From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: David Greaves <david@dgreaves.com>
Cc: Mark Lord <liml@rtr.ca>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jgarzik@pobox.com
Subject: Re: LibPATA/ATA Errors Continue - Will there be a fix for this?
Date: Tue, 20 Jun 2006 11:46:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606201146430.2601@p34.internal.lan> (raw)
In-Reply-To: <44981800.2000807@dgreaves.com>
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
>>
>>
>
>
> --
>
next prev parent reply other threads:[~2006-06-20 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 12:17 Justin Piszcz
2006-06-20 13:01 ` Mark Lord
2006-06-20 13:03 ` Justin Piszcz
2006-06-20 14:23 ` David Greaves
2006-06-20 15:45 ` David Greaves
2006-06-20 15:46 ` Justin Piszcz [this message]
2006-06-20 22:20 ` David Greaves
2006-06-20 22:22 ` Justin Piszcz
2006-06-21 11:39 ` Justin Piszcz
2006-06-20 15:15 Al Boldi
2006-06-20 15:48 ` Justin Piszcz
2006-06-20 16:25 ` Mark Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0606201146430.2601@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=david@dgreaves.com \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®