lkml.org 
[lkml]   [1998]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Drive error
Date
>> From: Mark Shapiro <mark@award.bios.net>
>> Date: Sun, 12 Apr 1998 23:39:04 -0400 (EDT)
>
>> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=1988685, sector=17036
>> end_request: I/O error, dev 03:03, sector 17036
>
>> Is this a problem with the hard drive or the controller? Should I replace the
>> bad copmonent, or is it fixable? It looks like a hardware error rather than a
>> filesystem error, sooo....
>
> These are low-level errors from the disk driver, reporting errors from
> the disk controller. What they mean is that you have hardware errors
> developing on your drive. When this happens, *immediately* perform a
> backup!! If you have a spare (empty) disk handy, do the backup by using
> dd to copy the raw disk image.

While I agree that IDE errors are typically a sign of a near future death,
but in this case, I note that it is a "dma_intr". If you are running a
2.0.x kernel, there might be another reason. Here is a quote from Mark
Lord taken from a previous linux-kernel message:

------
[UltraDMA "reused" a status bit that used to mean "bad block",
but now means "CRC error, retry transfer". Linux 2.0.xx just
gives up when it sees "bad block", since it "knows" that it
cannot do anything about a bad block.. very painful. ]
------

I think Mark was going to (or has) sent Alan a patch for the 2.0.34-preX
that Alan is currently putting together, but I'd have to check.

Paul.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.462 / U:1.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site