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: 16 Aug 93 12:30:35 PDT Message-ID: <1993Aug16.123035.22380@crash> References: <1993Aug15.214815.3942@limbic.ssdl.com> Lines: 13 Gil Kloepfer Jr. (gil@limbic.ssdl.com) wrote: : : I suspect that the problem is that the wd.c driver is not handling the : bad144 table correctly -- one of the patches causes the bad sector table : check to be made ONLY if the transfer is a single-block transfer (DKFL_SINGLE). I'm having a similar problem. My NetBSD machine gives an error message saying it's getting a hard error reading a block. It gives the block number, then crashes the machine. I've figured out how to use bad144 to mark the offending block of the disk but the same hard error message keeps coming up!!! Should I use bad144 or is it broken? I haven't figured out how to use badsect yet but my machine is really unreliable now! This is frustrating!