Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!agate!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: kernel corruption on 330Mb hd???
Message-ID: <12811@polya.Stanford.EDU>
Date: 11 Nov 89 20:00:47 GMT
References: <17504@kuhub.cc.ukans.edu> <5604@umd5.umd.edu>
Reply-To: ali@Polya.Stanford.EDU (Ali T. Ozer)
Organization: .
Lines: 21

In article <5604@umd5.umd.edu> feldman@umd5.umd.edu (Mark Feldman) writes:
>In article <17504@kuhub.cc.ukans.edu> 2FHGKINGLY@kuhub.cc.ukans.edu writes:
>>What happens is the machine locks up during the boot process.
>>You fix the problem by booting off optical and copying the sdmach
>>file from optical to the hd. 
>I've had three systems corrupted the same way.  It's a bug.  Many others
>have suffered the same bug.  As of yet, no one knows what is causing the
>boot file to become corrupted, let alone how to prevent it.

Yes, this is a bug.  NeXT is working on it.

If your system freezes up during the boot process, after announcing the
amount of memory and possibly the number of buffers used, then you might
be bitten by this bug.  You will need to boot from a 1.0 optical to fix
things; please diff your /sdmach file against the good one from the OD;
if they are different copy the one from the OD oveer the corrupted one.

If you can duplicate the problem, please send me mail and I'll get it to
the OS engineers.

Ali