From owner-freebsd-questions Fri Aug 30 07:09:16 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21919 for questions-outgoing; Fri, 30 Aug 1996 07:09:16 -0700 (PDT) Received: from zeus.xtalwind.net (h-admissible.x31.infi.net [206.27.115.35]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21913; Fri, 30 Aug 1996 07:09:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zeus.xtalwind.net (8.7.5/8.7.3) with SMTP id KAA01049; Fri, 30 Aug 1996 10:09:12 -0400 (EDT) Date: Fri, 30 Aug 1996 10:09:11 -0400 (EDT) From: jack To: Mike Newell cc: dyson@FreeBSD.org, Igor Vinokurov , freebsd-questions@FreeBSD.org Subject: Re: strange error with WD family disk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 Aug 1996, Mike Newell wrote: > On Thu, 29 Aug 1996, John S. Dyson wrote: > > > > wd0: interrupt timeout: > > > wd0: status 58 error 0 > > > wd0: interrupt timeout: > > > wd0: status 58 error 1 > > > wd0: wdunwedge failed: > > > wd0: status 80 error 1 > > > 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 error 1 > > > wd0: wdunwedge failed: > > > wd0: status d0 error 1 > > > > > > 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): > wd0: 1916MB (3924144 sectors), 3893 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): > 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? I have the same thing with WD drives but it isn't the drives. It started when I updated my motherboard. The damned "Energy saver" BIOS is powering down the drives. I've diabled power management, enabled it and disabled powering down the drives, and it still insists on spinning them down. :( -------------------------------------------------------------------------- Jack O'Neill Finger jacko@onyx.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD --------------------------------------------------------------------------