Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!think.com!mintaka.lcs.mit.edu!ai-lab!hal.gnu.ai.mit.edu!mycroft From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.questions Subject: Re: PC keeps rebooting after install Date: 9 Mar 1993 10:42:49 GMT Organization: /etc/organization Lines: 24 Message-ID: <1nhsb9INN63p@life.ai.mit.edu> References: <1n0nmqINNmro@crcnis1.unl.edu> <1993Mar3.011330.10035@unet.net.com> <6496@krafla.rhi.hi.is> NNTP-Posting-Host: hal.ai.mit.edu In article <6496@krafla.rhi.hi.is> adamd@rhi.hi.is (Adam David) writes: > > I installed 386bsd on the whole disk but every so often it crashes so > bad that it needs to be guided through over 20 reboots one after the > other before things normalise again. It seems to be minor > inconsistencies in the filesystem (not reported by fsck) that have > this effect once in a while. ~Oh, that." When fsck corrects an error on booting, a certain infamous bug in init will cause the boot sequence to continue even as it's trying to reboot. This will cause the root file system to be mounted read/write, and possibly some files modified. The machine ends up rebooting unsynced, and the root file system has errors in it. You can guess what happens next. I think patchkit 0.2.1 fixes this. -- \ / Charles Hannum, mycroft@ai.mit.edu /\ \ PGP public key available on request. MIME, AMS, NextMail accepted. Scheme White heterosexual atheist male (WHAM) pride!