Date: Mon, 25 May 1998 23:56:54 -0700 From: Mike Smith <mike@smith.net.au> To: Michael Robinson <robinson@public.bta.net.cn> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver Message-ID: <199805260656.XAA00687@antipodes.cdrom.com> In-Reply-To: Your message of "Tue, 26 May 1998 11:42:26 %2B0800." <199805260342.LAA02975@public.bta.net.cn>
next in thread | previous in thread | raw e-mail | index | archive | help
> I wrote a message related to this problem to freebsd-questions > yesterday, but upon further investigation, I have decided this is > a bug, not a feature. Actually, it's almost certainly a hardware fault. > I have a Tecra 510CDT (running 2.2.6-RELEASE) that suffered a > corrupted disk when the battery power failed as it was trying to > halt. I have identified seven contiguous sectors on the disk that > cause the following problem: > > 1. Any I/O access to the affected sectors will cause the following > message: > > wd0: interrupt timeout > wd0: status 58<rdy,seekdone,drq> error 0 The disk has failed to respond to the access request. You may be able to recover by dd'ing zeroes over the whole partition (forcing a block reallocation), however the disk may be damaged beyond repair. > 4. Hard reset is the only way to recover. > > I tried to work around this problem with bad144, but rapidly discovered > that bad144 is something of a bad joke in FreeBSD. Does anyone have > any recommendations for how to fix the wd driver or otherwise recover > from this fault? You could use 'badsect' to isolate the sectors. This is more effective than bad144 (which was a joke long ago). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805260656.XAA00687>