Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!crash!warelock From: warelock@crash.cts.com (Tom Zacharoff) Subject: Re: bad144 problem? Organization: CTS Network Services (crash, ctsnet), El Cajon, CA Date: 23 Aug 93 17:42:52 PDT Message-ID: <1993Aug23.174252.27909@crash> References: <25asop$6h6@wzv.win.tue.nl> Lines: 31 Guido van Rooij (guido@gvr.win.tue.nl) wrote: : warelock@crash.cts.com (Tom Zacharoff) writes: : : >Peter da Silva (peter@NeoSoft.com) wrote: : >: : >: I seem to remember that there are patches out that let you put the bad sector : >: table at other offsets, but I don't now if they're NetBSD-only or not. The : >: ideal solution would be to make it a bad-sector partition like in System V, : >: but I've been told (and I quite believe) that that would require WAY too much : >: hacking to make it worthwhile in the near term. And long-term everyone's : >: going to logically-perfect drives using SCSI or IDE (though that begs the : >: question of what you do when you get NEW bad sectors... if the drive : >: automatically remaps them you get invisible file-system corruption, and if : >: it doesn't you still need bad sector handling). : : >I have an IDE drive. Does that mean I don't need to mess around with this : >bad sector forwarding? Should my drive be doing all this automatically? : Yes. You DON'T need the sf flag for IDE drives in the disktab. Well if that's true then how do I fix these disk errors? My unix box crashes and locks up after giving me the message "Hard error reading fsbn 6913". Badsect won't allow me to create any bad files to mask the disk errors. It says that the filesystem is busy. I'm trying to follow the steps in the man page for badsect to the letter. Do I need some kind of fix-it floppy? I also get an error like this: "Error: C:1 H:6 S:26" about 100-200 times and maybe (just maybe) then it boots up. I hope this new release of NetBSD will handle these things better.