From owner-freebsd-questions  Thu Aug 29 16:26:31 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA15585
          for questions-outgoing; Thu, 29 Aug 1996 16:26:31 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA15579
          for <freebsd-questions@freebsd.org>; Thu, 29 Aug 1996 16:26:24 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id SAA00809; Thu, 29 Aug 1996 18:21:37 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199608292321.SAA00809@dyson.iquest.net>
Subject: Re: strange error with WD family disk
To: igor@cs.ibank.ru (Igor Vinokurov)
Date: Thu, 29 Aug 1996 18:21:37 -0500 (EST)
Cc: freebsd-questions@freebsd.org
In-Reply-To: <199608291358.RAA02171@escape.cs.ibank.ru> from "Igor Vinokurov" at Aug 29, 96 05:58:32 pm
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> re,
> 
>   Sometime FreeBSD report following:
> 
> wd0: interrupt timeout:
> wd0: status 58<seekdone,drq> error 0
> wd0: interrupt timeout:
> wd0: status 58<seekdone,drq> error 1<no_dam>
> wd0: wdunwedge failed:
> wd0: status 80<busy> error 1<no_dam>
> wd0a: wdstart: timeout waiting to give command writing fsbn 10672 of 10672-10751 (wd0 bn 10672; cn 5 tn 9 sn 25)wd0: status 80<busy> error 1<no_dam>
> wd0: wdunwedge failed:
> wd0: status d0<busy,seekdone> error 1<no_dam>
> 
>   Anyone can explain?
> 
This is not definitive, and should be considered to be a net
rumour :-):

Is your drive a relatively new WD (say purchased between 1yr and 6mos
ago?)  If it was, and you have an ASUS MB with an AWARD bios, there
is a compatibility problem.  The bios does not wait until the
drive is *really ready* (nor should it need to) before certain
I/O requests are made.  The problem is that the drive heads are
loaded before the drive is really ready (as I have inferred from
some USENET discussions.)  This slowly clobbers the disk surface
until it is bad.  WD has some recovery stuff on their FTP site,
ftp.wdc.com.  You would do well to call the WD support number
for further help.  (I have had two drives fail with the old
microcode.)  WD has some updated microcode that fixes the drive,
but if your surface is damaged too bad, then you need to return
the drive for replacement.

John