Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!dog.ee.lbl.gov!network.ucsd.edu!news.cerf.net!crash!warelock From: warelock@crash.cts.com (Tom Zacharoff) Subject: Re: bad144 problem? Organization: CTS Network Services (crash, ctsnet), El Cajon, CA Date: 30 Aug 93 12:11:56 PDT Message-ID: <1993Aug30.121156.21094@crash> References: <256js2INN1jk@kralizec.zeta.org.au> Lines: 24 I posted a message earlier about having problems with my "old" ide drive. I've just recently installed Netbsd 0.9 and figured out how to get the install program to start up bad sector forwarding. I used to specify my drive as an ide to the install program. It ended up as an st506 drive in the disklabel. After reading the install program's script I figured out that only if you specify an esdi or st506 drive you could get the install program to turn the bad sector forwarding on. I also discovered that when it is turned on, the install program partitions the disk slightly differently. It actually leaves one cylinder free for use as the bad sector table and it properly initializes the table using a form of bad144 not explained in the man page (or at least to my knowledge: bad144 wd0 0). It looks like everything is working fine now. I was getting that hard error reading fsbn message that crashes my system but after adding the entry (the absolute entry, not the one in relation to the partition; i.e. /dev/wd0a) to the table and rebooting the error never came up again. Now all I get are soft errors reading certain sectors. That does nothing to crash my system. I'm going to look into the use of the -f formatting option of bad144 for any new bad areas that show up. This is the first time I've seen any real response to a concern I've had about anything I cared to post on the Net. I'd also like to say thanks to the guy that posted about the need for examples and how sometimes they are totally missing. I feel the same way.