From: "Dave Gilbert (Home)" <gilbertd@treblig.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: war <war@lucidpixels.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
apiszcz@solarrain.com
Subject: Re: WESTERN DIGITAL 200GB IDE DRIVES GO OFFLINE - HOW TO FIX
Date: Wed, 11 Jun 2003 17:59:28 +0100 [thread overview]
Message-ID: <3EE75FF0.3080702@treblig.org> (raw)
In-Reply-To: 1055346538.2420.3.camel@dhcp22.swansea.linux.org.uk
Alan Cox wrote:
> On Mer, 2003-06-11 at 16:36, war wrote:
>
>>I've searched the archives, google and so on, many questions relating to
>>why the Western Digital drives go offline exist but with no answers.
>>
>>PROBLEM: After extended periods of time, the HDD will simply go offline.
>>
>>EXAMPLE LOG ENTRY:
>>
>>Jun 2 02:07:26 l2 kernel: hdg: dma_intr: status=0x61 { DriveReady
>>DeviceFault Error }
>>Jun 2 02:07:26 l2 kernel: hdg: dma_intr: error=0x04 { DriveStatusError }
>>Jun 2 02:07:26 l2 kernel: hdg: DMA disabled
>
>
> "DeviceFault" and "Error"
>
> Those are return values I associate with device (ie hardware) faults
> oddly enough 8)
In many cases these drives with the older firmware don't even grace you
with the benefit of an IDE error; they just give random file system
corruption. I believe that this was the cause of the problems I was
reporting here:
http://www.cs.helsinki.fi/linux/linux-kernel/2003-14/0935.html
after updating the firmware both systems seem to be OK.
So even if you aren't actually seeing these errors, even if you aren't
using RAID I'd suggest getting this patch.
Dave
next prev parent reply other threads:[~2003-06-11 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 15:36 WESTERN DIGITAL 200GB IDE DRIVES GO OFFLINE - HOW TO FIX war
2003-06-11 15:48 ` Alan Cox
2003-06-11 16:59 ` Dave Gilbert (Home) [this message]
2003-06-11 17:27 ` Jeff Garzik
2003-06-11 17:46 ` war
2003-06-11 18:00 ` Nuno Monteiro
2003-06-11 23:08 ` Brian McGroarty
2003-06-14 4:10 ` Marc Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EE75FF0.3080702@treblig.org \
--to=gilbertd@treblig.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apiszcz@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=war@lucidpixels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox