From owner-freebsd-questions  Thu Aug 29 19:52:45 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA27489
          for questions-outgoing; Thu, 29 Aug 1996 19:52:45 -0700 (PDT)
Received: from vegemite.Stanford.EDU (vegemite.Stanford.EDU [171.65.76.158])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA27484;
          Thu, 29 Aug 1996 19:52:39 -0700 (PDT)
Received: (hlew@localhost) by vegemite.Stanford.EDU (8.7.1/8.6.4) id TAA26552; Thu, 29 Aug 1996 19:52:38 -0700 (PDT)
Date: Thu, 29 Aug 1996 19:52:38 -0700 (PDT)
From: Howard Lew <hlew@sequence.Stanford.EDU>
To: dyson@freebsd.org
cc: Igor Vinokurov <igor@cs.ibank.ru>, freebsd-questions@freebsd.org
Subject: Re: strange error with WD family disk
In-Reply-To: <199608292321.SAA00809@dyson.iquest.net>
Message-ID: <Pine.SUN.3.91.960829195103.26496C-100000@vegemite.Stanford.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 29 Aug 1996, John S. Dyson wrote:

> > 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

Sort of dumb question, but you are kidding right?

If not then  how does someone get the updated microcode?  Or do we have 
to return the drive to Western Digital?