Article View: comp.sys.next.bugs
Article #31HELP: Crash in 3.0 results in failure to boot
From: 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
Technical Details
Message-ID:
<1993Jan7.165156.9501@dolphin.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!wupost!csus.edu!netcom.com!netcomsv!dolphin!zacShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.bugs Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!wupost!csus.edu!netcom.com!netcomsv!dolphin!zac From: Zacharias J. Beckman <zac@dolphin.com> Subject: HELP: Crash in 3.0 results in failure to boot Message-ID: <1993Jan7.165156.9501@dolphin.com> Sender: zac@dolphin.com Reply-To: zac@dolphin.com Organization: Dolphin Software Distribution: usa Date: Thu, 7 Jan 1993 16:51:56 GMT Lines: 19