lkml.org 
[lkml]   [2006]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateTue, 20 Jun 2006 11:46:50 -0400 (EDT)
FromJustin Piszcz <>
SubjectRe: LibPATA/ATA Errors Continue - Will there be a fix for this?
Dave, what is the make/model of the drives you get errors with by the way?

On Tue, 20 Jun 2006, David Greaves wrote:

> [Some email archaeology later]
>
> Back in March I was running 2.6.16 (with the opcode patch) and I sent an
> email with the following info:
>
> dmesg:
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/04 to SCSI
> SK/ASC/ASCQ 0xb/00/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
>
> Does that help with the diagnosis?
>
> Also see my emails: SMART on SATA reporting errors?
> http://marc.theaimsgroup.com/?l=linux-ide&m=113933732903205&w=2
>
> I did reply but got no response so I assumed I was just so far off base
> that I was being ignored :)
>
> David
>
> David Greaves wrote:
>> Mark Lord wrote:
>>
>>> MMm.. probably "barrier" commands that the drive doesn't like.
>>> Pity those messages don't also dump the failed opcode.
>>>
>> For me:
>> smartctl -data -o on /dev/sda
>> produces this on 2.6.17-rc5
>>
>> (I thought the opcode patch went into 2.6.17...)
>>
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>> ata1: PIO error
>> ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
>> ata1: status=0x51 { DriveReady SeekComplete Error }
>> ata1: error=0x04 { DriveStatusError }
>>
>> David
>>
>>
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
>>>> DriveStatusError }
>>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
>>>> DriveStatusError }
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense
>>>> translation for status: 0x51
>>>> Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 {
>>>> DriveReady SeekComplete Error }
>>>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
> --
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-20 17:49    [from the cache]
©2003-2010