Re: Understanding my SMART errors

In <20090610143552.fd11cd1a.celejar@xxxxxxxxx>, Celejar wrote:
An excerpt of a current 'dmesg | grep hda' (these errors occurred upon
resuming from suspend to disk):

[34074.459505] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
} [34074.459685] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[34074.459886] hda: possibly failed opcode: 0x25
[34079.744751] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
} [34079.744931] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[34079.745135] hda: possibly failed opcode: 0x25
[34079.750086] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
} [34079.750263] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[34079.750466] hda: possibly failed opcode: 0x25
[34079.789002] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
} [34079.789192] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[34079.789411] hda: possibly failed opcode: 0x25
[34079.794851] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
} [34079.795043] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
[34079.795261] hda: possibly failed opcode: 0x25

Could be cabling or some other component between the kernel and the HD, but
most likely this is the sign of a failing drive.

Jun 9 15:12:29 lizzie smartd[3474]: Device: /dev/hda, ATA error count
increased from 12 to 17
Jun 10 14:09:30 lizzie smartd[3474]: Device: /dev/hda, ATA error count
increased from 28 to 34

Is this drive going?

Most likely, yes. Although, it might not completely fail for quite a while.
It may even be fixable through manufacturer-specific means.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/

Attachment: signature.asc
Description: This is a digitally signed message part.

Relevant Pages