> hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: write_intr: error=0x04 { DriveStatusError }
> I have had this happen with recent kernels.. (I may have
> mentioned it before on here). These are very intermittent, and
> at least the recent ones haven't shown visible (to e2fsck)
> filesystem corruption.
> Is this a harmless error? Does it mean corruption? Is my drive
> creeping towards the ancient IDE burial ground?
> How do I tell if my MB has a CMD640 on it?
I had the same problem when I was using a Quantum 2.5G drive on a Pentium 100.
It went away after I changed PIO mode from 4 to 3 in BIOS Setup. From the
other hand, I also saw this message with an old 340M HD on a 486/33 for
several months before it died. So guess it can be both. I never saw e2fsck
errors caused by this message though.