From owner-freebsd-stable  Mon Aug  3 11:36:20 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA13328
          for freebsd-stable-outgoing; Mon, 3 Aug 1998 11:36:20 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from pc-21490.bc.rogers.wave.ca (pc-21490.bc.rogers.wave.ca [24.113.51.240])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13278
          for <freebsd-stable@FreeBSD.ORG>; Mon, 3 Aug 1998 11:36:12 -0700 (PDT)
          (envelope-from jh@pc-21490.bc.rogers.wave.ca)
Received: (from jh@localhost)
	by pc-21490.bc.rogers.wave.ca (8.8.8/8.8.7) id LAA01901;
	Mon, 3 Aug 1998 11:35:20 -0700 (PDT)
Message-Id: <199808031835.LAA01901@pc-21490.bc.rogers.wave.ca>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199808031612.JAA14148@antipodes.cdrom.com>
Date: Mon, 03 Aug 1998 11:35:16 -0700 (PDT)
Reply-To: Jonathan Hanna <pangolin@rogers.wave.ca>
Organization: Pangolin Systems
From: Jonathan Hanna <pangolin@rogers.wave.ca>
To: Chris <chrisj@outcast.media-net.net>
Subject: Re: WD errors
Cc: freebsd-stable@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 03-Aug-98 Mike Smith wrote:
>> ...
>> follows. wd0s1f: wdstart: timeout waiting to give command reading fsbn
>> 3148892 of 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0:
>> status 80<busy> error 80<badblk>. after afew screens of that the message
>> will turn to  wd0: wdunwedge failed:
>> > wd0: status 80<busy> error 80<badblk>
>> > wd0s1f: wdstart: timeout waiting to give command reading fsbn 3148892 of
>> 3148892-3148893 (wd0s1 bn 3689468; cn 229 tn 167 sn 62)wd0: status
>> 80<busy> error 80<badblk>. the system will remain on-line (ie pingable)
>> ...
> 
> Your disk seems to be struggling with a bad block.  The best thing to do
> at this point is throw the disk out and get a new one, as with any
> modern IDE disk you will only get to this point once all of the
> available spare sectors have been used up.

When you give up on reading the block, you might try writing it and
then rereading. It may have been a bad write as opposed to a bad block.
I think I have caused this type of error with bad power connections but am 
not really sure.

Jonathan Hanna <pangolin@rogers.wave.ca>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message