DriveReady SeekComplete Error on hda

[Alan Cox]

On Sun, 04 Jan 2009 11:17:58 -0500
Robert L Cochran <cochranb at speakeasy.net> wrote:

> I'm getting these messages with reference to drive hda:
> 
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xb0
> 
> hda is this device:
> 
> Jan  4 10:52:51 dk kernel: hda: WDC WD2500JB-00REA0, ATA DISK drive
> Jan  4 10:52:51 dk kernel: hda: max request size: 512KiB
> Jan  4 10:52:51 dk kernel: hda: 488397168 sectors (250059 MB) w/8192KiB
> Cache, CHS=30401/255/63, UDMA(100)
> Jan  4 10:52:51 dk kernel: hda: cache flushes supported
> Jan  4 10:52:51 dk kernel:  hda: hda1 hda2
> Jan  4 10:52:52 dk kernel: EXT3 FS on hda1, internal journal
> Jan  4 10:53:00 dk kernel: hda: drive_cmd: status=0x51 { DriveReady
> SeekComplete Error }
> Jan  4 10:53:00 dk kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> Jan  4 10:53:00 dk smartd[3011]: Device: /dev/hda, opened
> Jan  4 10:53:00 dk smartd[3011]: Device: /dev/hda, found in smartd
> database.
> Jan  4 10:53:01 dk smartd[3011]: Device: /dev/hda, is SMART capable.
> Adding to "monitor" list.
> 
> My question is, should I replace hda? Are the drive_cmd messages a sign
> it is going dead?

0x51/0x04 (Drive Status Error) is 'unknown command'. Something is feeding
invalid requests to the drive - possibly the smart tools. From the dump
this looks like an ancient Fedora as Fedora uses libata and has done for
several releases now.