Alan Cox wrote: > Ar Maw, 2006-07-11 am 09:28 -0400, ysgrifennodd Justin Piszcz: >> Alan/Jeff/Mark, >> >> Is there anything else I can do to further troubleshoot this problem now >> that we have the failed opcode(s)? Again, there is never any corruption >> on these drives, so it is more of an annoyance than anything else. > > Nothing strikes me so far other than the data not making sense. Possibly > it will become clearer later if/when we see other examples. For me it's SMART related. smartctl -data -o on /dev/sda reliably gets a similar message. Justin - does this smartctl command trigger a message for you? I've been mailing on and off since January-ish. (http://marc.theaimsgroup.com/?l=linux-ide&w=2&r=7&s=libpata&q=b) Back in March I was running 2.6.16 (with a different version of Mark's 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 - : send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
