Thread View: comp.sys.next.bugs
3 messages
3 total messages
Started by Zacharias J. Beckman
Thu, 07 Jan 1993 16:51
HELP: Crash in 3.0 results in failure to boot
Author: Zacharias J. Beckman
Date: Thu, 07 Jan 1993 16:51
Date: Thu, 07 Jan 1993 16:51
19 lines
1512 bytes
1512 bytes
Hello, 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. When the system started to boot Mach, it declared that it couldn't write to mtab because the file system was read only!!! The only way around this at present is to boot in single-user mode, then continue the multi-user startup. Has anyone run into this sort of problem before, or have any idea where I an look to cure it? It may not be a 3.0 bug, but on the other hand, perhaps it is... Thanks in advance. -- Zacharias J. Beckman - Dolphin Software Inc. - zac@dolphin.com - use NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Re: HELP: Crash in 3.0 results in failure to boot
Author: Richard Tilley
Date: Sat, 09 Jan 1993 09:14
Date: Sat, 09 Jan 1993 09:14
18 lines
1237 bytes
1237 bytes
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!
Re: HELP: Crash in 3.0 results in failure to boot
Author: Greg Johnson
Date: Sun, 10 Jan 1993 22:55
Date: Sun, 10 Jan 1993 22:55
8 lines
974 bytes
974 bytes
In article <1993Jan7.165156.9501@dolphin.com> Zacharias J. Beckman <zac@dolphin.com> writes: >When the system started to boot Mach, it declared that it couldn't write to >mtab because the file system was read only!!! I found a colleague with a read-only root not long after doing a 3.0 install. We finally discovered that he copied from the CD-ROM /NeXTCD or some such file where the extended version packages are. If a file with that name is on /, the new /etc/rc mounts the file-system read-only!
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads