From owner-freebsd-stable Tue May 26 01:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11955 for freebsd-stable-outgoing; Tue, 26 May 1998 01:02:13 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11815 for ; Tue, 26 May 1998 01:01:04 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00687; Mon, 25 May 1998 23:56:55 -0700 (PDT) Message-Id: <199805260656.XAA00687@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Robinson cc: freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-reply-to: Your message of "Tue, 26 May 1998 11:42:26 +0800." <199805260342.LAA02975@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 23:56:54 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > 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 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