Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HELP, PLEASE! Server does not completely boot :(

0 views
Skip to first unread message

ashot...@rbcmail.ru

unread,
Aug 27, 2001, 2:05:20 AM8/27/01
to
Hello all!
Please help me to solve the problem with our NW
5.1 server.
When I start the server, it loads some nlms etc.
about 3 minutes, and then I see in System Console
the message:
"Couldn't allocate main stack"
and then:
"Cache memory allocator is out of avaiable memory"
and then:
"A schedule "Work to do" took over 1 minutes to
be run"
and then:
"Start term memory allocator is out of memory"
and then: 15 attempts to get more memory failed"
and then it repeats three last messages,
increasing the number of attempts (1214, 2890
etc.) in last message. And so on.
And nothing else starts... It doesn't even answer
on Ctrl+Esc (maybe because of System Console
being the only one task - nothing loads before
this task completely loads)
Thanks in advance for Your help (or for words of
sorrow :()

Christian Zimny

unread,
Aug 27, 2001, 4:37:43 AM8/27/01
to

Hi,

have you checked, how many memory do the server show (on the server
console: memory)?

Chris

czimny.vcf

ashot...@rbcmail.ru

unread,
Aug 27, 2001, 4:39:18 AM8/27/01
to
I must add: if I stert the server with -NA key
(don't load autoexec.ncf) the messages appears
only one time after loadind DSLOADER. Then after
loading of hardware autodetecting module, system
seems to be hanged... So, on logo screen the
sign "N" is still blinking, but on the System
Console screen the cursor is also blinking and
nothing happens (I waited about 15 minutes). So,
as I understand, the NDS was crashed. Is there a
way to boot in something like Safe-Mode to satart
DSREPAIR? Thanks again in advance.

ashot...@rbcmail.ru

unread,
Aug 27, 2001, 4:45:10 AM8/27/01
to
I cannot type anything in system console - it
doesn't give me a possibility to type - always
writing a message and not appearing the command
line. But memory seems to be ok - 512 Mb. We have
some hardware problems with it, we repaired it,
but it seems to crash NDS. So, I cannot start
DSREPAIR - I cannot access command line :((

> begin:vcard
> n:Zimny;Christian
> tel;fax:02234/1822-155
> tel;work:02234/1822-312
> x-mozilla-html:FALSE
> url:www.kdvz-frechen.de
> org:kdvz Rhein-Erft-Rur;Benutzer-Service
> adr:;;Bonnstr. 16-18;Frechen;NRW;50226;Germany
> version:2.1
> email;internet:czi...@kdvz-frechen.de
> title:Dipl.-Ing.
> fn:Christian Zimny
> end:vcard
>
>


Christian Zimny

unread,
Aug 27, 2001, 4:56:38 AM8/27/01
to

Can you try to load server with -NS (without startup.ncf) -NA and then
manually load the startup.ncf lines?

Can you see your Netware volumes (nwconfig)?

Can you mount it manually ?

Chris

czimny.vcf

Massimo Rosen

unread,
Aug 27, 2001, 4:59:05 AM8/27/01
to
Hi,

ashot...@rbcmail.ru wrote:
>
> So,
> as I understand, the NDS was crashed. Is there a
> way to boot in something like Safe-Mode to satart
> DSREPAIR? Thanks again in advance.

Server -ndb starts the server without opening NDS. You should probably
use that in conjunction with -na to avoid products strating in autoexec
trying to access NDS and crash.

CU,
--
Massimo Rosen
Novell Support Connection Sysop
No emails please!
http://www.cfc-it.de

ashot...@rbcmail.ru

unread,
Aug 27, 2001, 5:27:08 AM8/27/01
to
Ok. I made it. The second time I tryed to reboot
server with -NA key it booted. I saw the message
(very quick dissapeared, but I had a tome to read
it) about swap file - it was corrupted or
something like it. How to repair the swap-file
(if needed)? And how long works the DSREPAIR
utility if I've choose "Rebuild Schema"?
Thanks again =)

Christian Zimny

unread,
Aug 27, 2001, 5:55:32 AM8/27/01
to

Perhaps vrepair can repair it (with write all changes to disk).

Dsrepair run very fast (maximal a few minutes).

Chris

czimny.vcf

ashot...@rbcmail.ru

unread,
Aug 27, 2001, 7:26:03 AM8/27/01
to
Thanks all =))) The server booted successfully. I
just rebooted with -NA key and started DSREPAIR.
I've choosen the first - "Automatically
repair..." or something and the just rebooted the
system. And all became ok =))) I hope that all
will be ok for a long years =))))
Thanks again for Your patronage =)))))
0 new messages