sata_sil or libata?

sata_sil or libata?

[Wesley Lim]

Jeff,

I have encountered a problem with my SATA controller and would like to
report the bug - I'm not sure if you are the person to contact but
here goes:

2.6.16.1 from kernel.org
Syba SD-SATA150R PCI (Silicon Image 3112A flashed to 4.2.76)
Maxtor 6L250M0 Rev:BACE

I have it running as part of a degraded RAID 5 (I was planning to
transition to a full RAID 5 but I guess not with the errors I'm
getting =(
When I was copying from a regular device (hdc3) to the degraded array
md2 (composed of hda3 and sda3) ata1 would start to report errors. I
keep getting errors reporting the same sectors.

I was wondering if this could possibly be firmware related?

Let me know if I can provide any additional information to help solve this bug.

Thanks for the help!
Wesley

dmesg:
libata version 1.20 loaded.
sata_sil 0000:00:09.0: version 0.9
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 16
ata1: SATA max UDMA/100 cmd 0xCC802E80 ctl 0xCC802E8A bmdma 0xCC802E00 irq 16
ata2: SATA max UDMA/100 cmd 0xCC802EC0 ctl 0xCC802ECA bmdma 0xCC802E08 irq 16
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e01 87:4663 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 490234752 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: SATA link down (SStatus 0)
scsi1 : sata_sil
  Vendor: ATA       Model: Maxtor 6L250M0    Rev: BACE
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda

ERROR WHILE rsync -avx / /mnt/:
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 63268998
raid5: read error not correctable.
raid5: Disk failure on sda3, disabling device. Operation continuing on 1 devices
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 63269006
raid5: read error not correctable.
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 63269014
raid5: read error not correctable.
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for status: 0x51
ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 63269022
raid5: read error not correctable.
I/O error in filesystem ("md2") meta-data dev md2 block 0x1cfaa598    
  ("xlog_iodone") error 5 buf count 4096
xfs_force_shutdown(md2,0x2) called from line 959 of file
fs/xfs/xfs_log.c.  Return address = 0xc0207a0c
Filesystem "md2": Log I/O Error Detected.  Shutting down filesystem: md2
Please umount the filesystem, and rectify the problem(s)
RAID5 conf printout:
 --- rd:3 wd:1 fd:2
 disk 0, o:0, dev:sda3
 disk 1, o:1, dev:hda3
I/O error in filesystem ("md2") meta-data dev md2 block 0x1cfaa580    
  ("xlog_iodone") error 5 buf count 12288
xfs_force_shutdown(md2,0x2) called from line 959 of file
fs/xfs/xfs_log.c.  Return address = 0xc0207a0c
printk: 2552 messages suppressed.
Buffer I/O error on device md2, logical block 14766033
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766034
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766035
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766036
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766037
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766038
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766039
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766040
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766041
lost page write due to I/O error on md2
Buffer I/O error on device md2, logical block 14766042
lost page write due to I/O error on md2
RAID5 conf printout:
 --- rd:3 wd:1 fd:2
 disk 1, o:1, dev:hda3
xfs_force_shutdown(md2,0x1) called from line 338 of file
fs/xfs/xfs_rw.c.  Return address = 0xc0207a0c

Re: sata_sil or libata?

[David Greaves]

Wesley Lim wrote:

>Jeff,
>
>I have encountered a problem with my SATA controller and would like to
>report the bug - I'm not sure if you are the person to contact but
>here goes:
>
>2.6.16.1 from kernel.org
>Syba SD-SATA150R PCI (Silicon Image 3112A flashed to 4.2.76)
>Maxtor 6L250M0 Rev:BACE
>
>ata1: no sense translation for status: 0x51
>ata1: translated ATA stat/err 0x51/00 to SCSI SK/ASC/ASCQ 0x3/11/04
>ata1: status=0x51 { DriveReady SeekComplete Error }
>sd 0:0:0:0: SCSI error: return code = 0x8000002
>sda: Current: sense key: Medium Error
>    Additional sense: Unrecovered read error - auto reallocate failed
>end_request: I/O error, dev sda, sector 63268998
>raid5: read error not correctable.
>raid5: Disk failure on sda3, disabling device. Operation continuing on 1 devices
>  
>
Hi Wesley; I'm glad you've come along :) I have almost identical problems.

I take it badblocks shows the drives as OK? (mine does)

I suggest a scan of the linux-ide archives from early february ago.
Subject: LibPATA code issues / 2.6.15.4

Mark published *two* patches to provide scsi op/cmd info which you may
want to apply. (25/2/06 and 14/2/06)
(They don't quite apply cleanly - IIRC Mark has a DPRINTK macro that
needs changing to a printk call)

Your results will then look like this (vanilla 2.6.16 with cmdpatch):

ata2: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata2: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: command 0x25 timeout, stat 0x51 host_stat 0x0
ata2: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata2: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata2: status=0x51 { DriveReady SeekComplete Error }
sd 1:0:0:0: SCSI error: return code = 0x8000002
sdb: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sdb, sector 393692817
raid1: sdb2: rescheduling sector 2975952
raid1: sdd2: redirecting sector 2975952 to another mirror
ata2: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata2: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata2: status=0x51 { DriveReady SeekComplete Error }

By the way, 2.6.16 is not kicking the drives from the array for me.
Did you mean 2.6.15.1? (just checking)

David
PS I added the people from the last thread to this one as I assume
you'll be interested - hope that's OK.

Re: sata_sil or libata?

[Wesley Lim]

On 4/1/06, Mark Hahn <hahn@physics.mcmaster.ca> wrote:
> >     Additional sense: Unrecovered read error - auto reallocate failed
> > end_request: I/O error, dev sdb, sector 393692817
>
> this sort of thing would make me want to sanity-check the drives,
> since it certainly sounds like a media/heat/vibration/power problem.
>
> have you run a SMART selftest on these drives?

I've done badblocks on the drive and it's fine. I haven't tried
smartctl as I read -d ata can cause problems because of some SCSI
queuing thing? Can I safely use smartd yet?

Re: sata_sil or libata?

[Mark Hahn]

> > >     Additional sense: Unrecovered read error - auto reallocate failed
> > > end_request: I/O error, dev sdb, sector 393692817
> >
> > this sort of thing would make me want to sanity-check the drives,
> > since it certainly sounds like a media/heat/vibration/power problem.
> >
> > have you run a SMART selftest on these drives?
> 
> I've done badblocks on the drive and it's fine. I haven't tried
> smartctl as I read -d ata can cause problems because of some SCSI
> queuing thing? Can I safely use smartd yet?

afaikt, the smart thing had to do with incomplete locking of 
the scsi passthrough stuff.  it was never an issue in a testing
situation (without other IO), and I'd guess it's been fixed since.

Re: sata_sil or libata?

[Wesley Lim]

On 4/1/06, David Greaves <david@dgreaves.com> wrote:
> I take it badblocks shows the drives as OK? (mine does)

smartctl says that SMART overall-health self-assessment is passed.

I've tinkered around with badblocks and the results are surprising. I
really hope this is not a case of bad hard disk that intermittently
decides to act up.

badblocks gives the same errors as when copying files into the drive.
*However* badblocks reports 0 bad sectors and no libata error if I
test the exact same sectors it reported were bad *immediately after
the previous (errored) run* (no cooldown/reboot/etc) It might have to
do with length of SATA bus activity? I get both libata and badblocks
errors around the 60000000 sector range after badblocks has been
running ~1 hour into a test. if I just run badblocks over those
reported blocks, it always shows up fine, no libata or badblocks error
(including badblocks -w)

I experience the errors only on the reading phase of badblocks, not
the writing phase. Also, as said above, I get zero errors when I
repeat badblocks -w over any specific "problem" areas. This cycle
repeats itself. (if I run a full drive scan, similar errors occur. if
I check just those "bad" blocks, they disappear)

I'm going to try starting a long block scan from a different address n
and see if the reported "bad" blocks show up around the n+60000000
sector range.

> Mark published *two* patches to provide scsi op/cmd info which you may
> want to apply. (25/2/06 and 14/2/06)
> (They don't quite apply cleanly - IIRC Mark has a DPRINTK macro that
> needs changing to a printk call)

I just patched my kernel. The new error messages are below.

> By the way, 2.6.16 is not kicking the drives from the array for me.
> Did you mean 2.6.15.1? (just checking)

Yup, 2.6.16.1


Here's the new dmesg (running badblocks)

ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 61590952
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Medium Error
    Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 61590960

Re: sata_sil or libata?

[Wesley Lim]

The more I think about it, the more it sounds like a faulty hard disk.
I'll just RMA it. Sorry for the trouble.

Wesley

On 4/1/06, Wesley Lim <wesleylim@gmail.com> wrote:
> On 4/1/06, David Greaves <david@dgreaves.com> wrote:
> > I take it badblocks shows the drives as OK? (mine does)
>
> smartctl says that SMART overall-health self-assessment is passed.
>
> I've tinkered around with badblocks and the results are surprising. I
> really hope this is not a case of bad hard disk that intermittently
> decides to act up.
>
> badblocks gives the same errors as when copying files into the drive.
> *However* badblocks reports 0 bad sectors and no libata error if I
> test the exact same sectors it reported were bad *immediately after
> the previous (errored) run* (no cooldown/reboot/etc) It might have to
> do with length of SATA bus activity? I get both libata and badblocks
> errors around the 60000000 sector range after badblocks has been
> running ~1 hour into a test. if I just run badblocks over those
> reported blocks, it always shows up fine, no libata or badblocks error
> (including badblocks -w)
>
> I experience the errors only on the reading phase of badblocks, not
> the writing phase. Also, as said above, I get zero errors when I
> repeat badblocks -w over any specific "problem" areas. This cycle
> repeats itself. (if I run a full drive scan, similar errors occur. if
> I check just those "bad" blocks, they disappear)
>
> I'm going to try starting a long block scan from a different address n
> and see if the reported "bad" blocks show up around the n+60000000
> sector range.
>
> > Mark published *two* patches to provide scsi op/cmd info which you may
> > want to apply. (25/2/06 and 14/2/06)
> > (They don't quite apply cleanly - IIRC Mark has a DPRINTK macro that
> > needs changing to a printk call)
>
> I just patched my kernel. The new error messages are below.
>
> > By the way, 2.6.16 is not kicking the drives from the array for me.
> > Did you mean 2.6.15.1? (just checking)
>
> Yup, 2.6.16.1
>
>
> Here's the new dmesg (running badblocks)
>
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> sd 0:0:0:0: SCSI error: return code = 0x8000002
> sda: Current: sense key: Medium Error
>     Additional sense: Unrecovered read error - auto reallocate failed
> end_request: I/O error, dev sda, sector 61590952
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: no sense translation for op=0x28 cmd=0x25 status: 0x51
> ata1: translated op=0x28 cmd=0x25 ATA stat/err 0x51/00 to SCSI
> SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> sd 0:0:0:0: SCSI error: return code = 0x8000002
> sda: Current: sense key: Medium Error
>     Additional sense: Unrecovered read error - auto reallocate failed
> end_request: I/O error, dev sda, sector 61590960
>