[lkml]   [2003]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: how to interpret ide error messages (2.4)
On Wed, 2003-04-02 at 13:23, Kiniger, Karl (MED) wrote:
> kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> kernel: hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=20300322, sector=1263288
> kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }

The drive could not find the requested sector. That normally means bad
things but for some drivers can also mean the controller asked for a
totally bogon sector number

> kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=20803307, sector=1766272
> kernel: end_request: I/O error, dev 16:04 (hdc), sector 1766272

Unrecoverable data error.

> The affected sectors dont generate any error messages if I read them today...

On errors the next write to a bad sector will typically remap it
transparently to another spare block on the disk. Read obviously cannot
do the same. That would mean that if for example clearcase ignored the
I/O error and wrote back what it thought it saw but did not that it may
have recovered the sector with invalid data. Its also possible of course
clearcase actually handles I/O errors properly (which is hard).

Consult the clearcase support I guess, there should be tools to verify
your clearcase datasets. You might also want to force an fsck on your
file systems while the box is down for disk replacement to check
everything out.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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