Mark Schoonover wrote:
> On 7/13/07, James G. Sack (jim) <[EMAIL PROTECTED]> wrote:
>>
>> Lan Barnes wrote:
>> > On Fri, July 13, 2007 7:02 pm, James G. Sack (jim) wrote:
>> >> Lan Barnes wrote:
>> >>> My MythTV box (FC6) is throwing these messages on boot and in dmesg:
>> >>>
>> >>> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>> >>> hda: drive_cmd: error=0x04 { DriveStatusError }
>> >>> ide: failed opcode was: 0xb0
>> >>> hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>> >>> hdb: drive_cmd: error=0x04 { DriveStatusError }
>> >>> ide: failed opcode was: 0xb0
>> >>> hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>> >>> hdd: drive_cmd: error=0x04 { DriveStatusError }
>> >>> ide: failed opcode was: 0xb0
>> >>>
>> >>> Both drives are less than a year old; one less than 6 months. What's
>> >>> going
>> >>> on?
>> >>>
>> >> I've seen these error messages for
>> >>  1) actual bad drives (but usu. not where 2+ fail at once)
>> >>     (confirmed by manufacturer's diagnostic utility)
>> >>     (preferably, testing on another box)
>> >>  2) bad cabling or loose connectors
>> >>  3) bad motherboard (I think) -- or maybe heat problem in chipset?
>> >>
>> >> In some cases I have regained stability by backing off the UDMA
>> settings
>> >> via hdparm -X until the  DriveReady SeekComplete Error stopped. Can't
>> >> say I felt good (or comfortable) about doing that, though.
>> >>
>> >> Regards,
>> >> ..jim
>> >>
>> >
>> > The box appears to be running beautifully. How afraid should I be?
>> >
>>
>> My experience is that this kind of error message seemed to get worse
>> over time (longer streams of messages, etc), and that eventually showed
>> up as sluggish behavior and ultimately, hard 'lockups'.
>>
>> Disclaimer: I'm speaking with no hardware credentials here -- just my
>> personal amateurish assessment.
>>
>> Perhaps someone more knowledgeable will comment on the particular error
>> messages you quoted?
>>
>> Regards,
>> ..jim
> 
> 
> 
> When I see these error messages in my server logs, the drive gets replaced.
> Drives are too cheap to risk data loss.
>

Note that he's logging errors for hda, hdb, and hdd (one of which is
probably a CD) -- do you see anything suspicious in that?

Regards,
..jim


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to