Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!pipex!uknet!mcsun!sun4nl!philapd!apdnews!wilko From: wilko@idca.tds.philips.nl (Wilko Bulte) Newsgroups: comp.os.386bsd.questions Subject: [FreeBSD] system reports 'invalid bad block table' on boot: why? Message-ID: <663@apdnews.idca.tds.philips.nl> Date: 11 Oct 93 15:48:34 GMT Sender: news@idca.tds.philips.nl Organization: Digital Equipment Corporation, Apeldoorn, The Netherlands. Lines: 23 Last weekend I've done an experimental install of FreeBSD Gamma (haven't got epsilon yet) on ST506 disk based system. During install I answered the question about automatic bad sector remapping with 'no', the install procedure subsequently ran bad144. Strangely enough, it didn't make a bad sector table (well it did make it, but it was empty). When I ran bad144 manually, the bad sector table was still empty. I added the badsectors that were reported during the bad144 run by hand, and now the table indeed reflected those bad blocks. So far so good (??). When the system is rebooted however, the kernel always reports something like 'invalid bad sector table'. This makes me suspect that it will not take bad spots into account, so I/O errors will probably a matter of time. Summary: what is wrong here? Wilko (who is happy that he has SCSI disks on his own system ;-) -- | / o / / _ Wilko Bulte mail: wilko@idca.tds.philips.nl |/|/ / / /( (_) |d|i|g|i|t|a|l| Equipment Corporation voice: +3155-432062 fax: +3155-432103 DTN: 829 2062 PO Box 245 - 7300 AE Apeldoorn - The Netherlands