home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.bugs
- Path: sparky!uunet!newsflash.concordia.ca!mizar.cc.umanitoba.ca!tilley
- From: tilley@ccu.umanitoba.ca (Richard Tilley)
- Subject: Re: HELP: Crash in 3.0 results in failure to boot
- Message-ID: <C0Kxow.98H@ccu.umanitoba.ca>
- Sender: news@ccu.umanitoba.ca
- Nntp-Posting-Host: ccu.umanitoba.ca
- Organization: University of Manitoba, Winnipeg, Canada
- References: <1993Jan7.165156.9501@dolphin.com>
- Date: Sat, 9 Jan 1993 09:14:56 GMT
- Lines: 18
-
- In <1993Jan7.165156.9501@dolphin.com> Zacharias J. Beckman <zac@dolphin.com> writes:
-
- >A few days ago, our server had a horrible crash. Everything on the network
- >locked up tight and needed to be restarted the hard way. When the server
- >came back up, it refused to boot in multi-user mode. The boot parameter of
- >"-nbu=128" was being ignored, and the default 16 buffers were used.
-
- Guess 1:
- You need a blank between the "-" and the "nbu=128".
-
- Guess 2:
- Use the "p" command in the ROM monitor to look at your settings.
- If they are all wrong, try using the "p" command to change one of them.
- Now use "p" to list them again.
- If the change was ignored, then cycle the power.
- Are the settings now all correct?
- --
- This space is not blank!
-