From owner-freebsd-questions  Fri Aug 30 03:02:41 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA00732
          for questions-outgoing; Fri, 30 Aug 1996 03:02:41 -0700 (PDT)
Received: from bigpuppy.newell.arlington.va.us (mcnsisdn.newell.arlington.va.us [206.27.237.14])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA00717;
          Fri, 30 Aug 1996 03:02:34 -0700 (PDT)
Received: (from mnewell@localhost) by bigpuppy.newell.arlington.va.us (8.6.12/8.6.9) id FAA09919; Fri, 30 Aug 1996 05:59:09 -0400
Date: Fri, 30 Aug 1996 05:59:09 -0400 (EDT)
From: Mike Newell <mnewell@newell.arlington.va.us>
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.BSF.3.91.960830055149.7730D-100000@bigpuppy.newell.arlington.va.us>
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:

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

    ... snip ...

I see this same problem with my Pentium 166 boxes.  Both have ASUS 
motherboards (sorry, I don't have the model number but they are P166/512K 
cache/dual IDE controller boards).  The error seems to pop up under heavy 
loading.  I do _not_ have WD drives - they are Maxtors:

  wdc0: unit 0 (wd0): <Maxtor 72004 A>
  wd0: 1916MB (3924144 sectors), 3893 cyls, 16 heads, 63 S/T, 512 B/S
  wdc0: unit 1 (wd1): <Maxtor 72004 A>
  wd1: 1916MB (3924144 sectors), 3893 cyls, 16 heads, 63 S/T, 512 B/S

I saw the problem once after upgrading to 2.1.5 but it does not seem to 
have recurred.  The surfaces do not appear to have been damaged at all; 
at least I've not lost any files and the systems seem to recover fine.

Anyone else see this with Maxtor drives?

Much obliged,

Mike

+--------------------------------------+------------------------------------+
| Mike Newell                          | The opinions expressed herein      |
| Affiliation:                         | are mine.  You can take them or    |
| Address:                             | leave them.  Flames to /dev/null.  |
+--------------------------------------+------------------------------------+
| Mike@Newell.arlington.va.us          | http://www.newell.arlington.va.us  |
+--------------------------------------+------------------------------------+
| "Peace.  It's wonderful!"  Father Divine.                                 |
+---------------------------------------------------------------------------+