Hello,

I've read a lot of threads about this error:

kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: drive_cmd: error=0x04 { DriveStatusError }

Well I've never gotten this before, all of a sudden today, I check my server information page in WHM and this error shows up under the hard drive information. My server was acting a little weird before that, for a period of about 30 minutes the load would just spike to about 30 and then go back down to the average of about .2 .

After never seeing this error before I just rebooted and now the error does not come back up. Server seems to be running just fine now.

Anyone know if I should worry about this seeing as how its not showing anymore that I rebooted?

Thanks,
Dan

This is a somewhat random error that occurs on many machines I own with IDE harddrives. I would not worry about it unless you start seeing this message very frequently. Next time if your load spikes to 30, you should examine what is going on with disk I/O. More than likely, it was just a coincidence.

Well these are samsung drives which I know are incompatible with smart check, so that may be the cause.

Originally posted by DynamoHost
Hello,

I've read a lot of threads about this error:

kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: drive_cmd: error=0x04 { DriveStatusError }

Well I've never gotten this before, all of a sudden today, I check my server information page in WHM and this error shows up under the hard drive information. My server was acting a little weird before that, for a period of about 30 minutes the load would just spike to about 30 and then go back down to the average of about .2 .

After never seeing this error before I just rebooted and now the error does not come back up. Server seems to be running just fine now.

Anyone know if I should worry about this seeing as how its not showing anymore that I rebooted?

Thanks,
Dan

Aslong as those errors aren't followed by I/O errors, you will be fine.

You can always run a badblocks scan on it during your off-peak hours to double check.

I had the same problem. Finally, I found the HDD had some bad sectors. Now I'm waiting the HDD to be replaced :(