Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!mcsun!Germany.EU.net!news From: bs@Germany.EU.net (Bernard Steiner) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD EPSILON -> Bogus Super Block Date: 6 Oct 1993 14:19:11 +0100 Organization: EUnet Deutschland GmbH, Dortmund, Germany Lines: 19 Distribution: world Message-ID: <28ugkf$rue@Germany.EU.net> References: <1993Oct6.120915.5678@mksol.dseg.ti.com> NNTP-Posting-Host: qwerty.germany.eu.net In article <1993Oct6.120915.5678@mksol.dseg.ti.com>, bmyers@asd470.dseg.ti.com (Bob Myers) writes: |> When the system starts checking, it finds a problem with block 16 in the /usr |> structure...fsck panics, then prints that it's going to do an automatic reboot... |> this *DOESN'T* happen; instead, an endless loop starts up and I see the same |> messages occuring --- about the bad/corrupted block 16. You should be able to stop the rc script on startup before the fsck by hitting control-c. Use bad144 wd0 0 <sector numbers> to add them to the bad144 table. Of course, this requires that you tell the system that your disk does not automatically replace bad sectors by itself. (Turn the badsect flag on in disklabel.) Alternatively, if your controller supports this, re-format the drive with automatic sector re-mapping. Cheers, Bernard