mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eric Bickle <ebickle@healthspace.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others
Date: Thu, 11 Sep 2003 19:43:33 +0100	[thread overview]
Message-ID: <1063305812.3606.4.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <001601c37891$660cc5d0$5d74ad8e@hyperwolf>

On Iau, 2003-09-11 at 19:20, Eric Bickle wrote:
> > > kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > kernel: hdc: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=150637065,
> > > sector=150636992
> >
> > This is a physical failure from the hard disk *NOT* a Linux problem
> 
> That's exactially what I thought when I first saw the problem as well.
> 
> However, we had about 16-20 different drives show up with the problem, about
> 3 different brands too. I did some low-level tests on the drives that linux
> had an error on and none of my diagnostic tools could find any problems.
> 
> Any ideas?

Other than to tell you Linux is simply reporting back what the drive
itself reported - which is a physical failure to recover a sector of
data no.

A test that rewrites such a sector will generally clear the error, its
one of the problems of some diagnostic tools. A pure read test should
fine the error again unless its something like overheat causing the
problem. SMART data will tell you drive temperatures


  reply	other threads:[~2003-09-11 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 18:20 Eric Bickle
2003-09-11 18:43 ` Alan Cox [this message]
2003-09-12  8:14   ` Rogier Wolff
2003-09-12 10:44     ` Alan Cox
2003-09-13  4:48       ` Problem: IDE data corruption with VIA chipsets Resident Boxholder
2003-09-13 17:04         ` Alan Cox
2003-09-11 19:11 Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others Eric Bickle
2003-09-12 11:19 Roman Kagan
2003-09-12 11:45 John Bradford

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=1063305812.3606.4.camel@dhcp23.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ebickle@healthspace.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®