sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[Mitchell Laks]

Hi,

I have a production server in place at a remote site. 
I have a single system drive that is an ide drive 
and two data drives that are on a via SATA controller in a raid1 
configuration.

I am monitoring the /var/log/messages and I get messages every few days

Mar 22 23:31:36 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
Mar 22 23:31:36 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }

Mar 23 23:20:12 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
Mar 23 23:20:12 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
Mar 23 23:32:03 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
Mar 23 23:32:04 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }

Mar 24 23:22:45 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
Mar 24 23:22:45 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }


Mar 27 23:16:57 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
Mar 27 23:16:57 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }

Mar 28 23:10:16 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
Mar 28 23:10:17 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
Mar 28 23:23:32 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
Mar 28 23:23:32 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }


Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }

Interestingly by the logs I see that they have occured 

March 1,2,3,8,14,17x3,20x4,21,22,23x2,24,27,28x2,29.

(x2 means two errors as in above example).

Also they occur during the activity of the cron job I do at 11pm to rsync 
backup the sata drive raid 1 to another server.

here is the output of dmesg:


ata5: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 
88:407f
ata5: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
ata5: dev 0 configured for UDMA/133
scsi4 : sata_via
ata6: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 
88:407f
ata6: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
ata6: dev 0 configured for UDMA/133
scsi5 : sata_via
  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
SCSI device sda: drive cache: write back
 /dev/scsi/host4/bus0/target0/lun0: p1
Attached scsi disk sda at scsi4, channel 0, id 0, lun 0
  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
SCSI device sdb: drive cache: write back
 /dev/scsi/host5/bus0/target0/lun0: p1
Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0


Am I correct in assuming that the sata drives are giving me these errors, 
and what shall I do? Could it possibly be a problem with the sata controller 
rather than the drives?

me@A1:~$ cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
      390708736 blocks [2/2] [UU]

unused devices: <none>

I have done some testing with different sata controllers and recently switched 
another server from the built in
sata controller on the A8v (via8237 controller) motherboard to  an add in pci 
promise sata II150 card.

I think I have seen conflicts between the sata_via and sata_promise and I 
already have a sata_promise card in the system for future expandability.

I am running the debian stock 2.6.12-1-386 kernel and debian sarge with mdadm 
ii  mdadm          1.9.0-4sarge1  Manage MD devices aka Linux Software Raid


1:/var/log# lsmod|grep sata
sata_via                8452  2
sata_promise            9988  0
libata                 44164  2 sata_via,sata_promise
scsi_mod              129096  4 sr_mod,sata_promise,libata,sd_mod

Thank you very much.

Mitchell

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[David Greaves]

Party line: It's a faulty cable (on both drives? triggered by rsync?
Doesn't show up under 'badblocks'? hah!)

Check out the linux-ide archive for my (and others) reports.

I've had lots of issues like this - spurious and IMHO incorrect error
messages. Only certain types of disk access cause them - xfs_repair and
rsync seem to tickle it.

With 2.6.15 I had lots of *very* scary moments with multiple disk
failures on a raid5 during xfs_repair.
I think it's down to the 'basic' error handling in the libata code and
certain disks/controllers being loose with the protocol. They then
identified problems in 'fua' (IIRC) handling which was pulled for 2.6.16.

2.6.16 seems to be much better (fewer 'odd' errors reported and md
doesn't mind)

David
PS Mitchell - you're still using Verizon and I still live off the edge
of their known world (in the UK) so I don't expect you'll get this reply
- hard luck my friend - get a better ISP!)


Mitchell Laks wrote:

>Hi,
>
>I have a production server in place at a remote site. 
>I have a single system drive that is an ide drive 
>and two data drives that are on a via SATA controller in a raid1 
>configuration.
>
>I am monitoring the /var/log/messages and I get messages every few days
>
>Mar 22 23:31:36 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 22 23:31:36 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>Mar 23 23:20:12 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 23 23:20:12 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>Mar 23 23:32:03 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 23 23:32:04 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>Mar 24 23:22:45 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 24 23:22:45 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>
>
>Mar 27 23:16:57 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 27 23:16:57 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>
>Mar 28 23:10:16 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 28 23:10:17 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>Mar 28 23:23:32 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 28 23:23:32 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>
>Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>Interestingly by the logs I see that they have occured 
>
>March 1,2,3,8,14,17x3,20x4,21,22,23x2,24,27,28x2,29.
>
>(x2 means two errors as in above example).
>
>Also they occur during the activity of the cron job I do at 11pm to rsync 
>backup the sata drive raid 1 to another server.
>
>here is the output of dmesg:
>
>
>ata5: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 
>88:407f
>ata5: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
>ata5: dev 0 configured for UDMA/133
>scsi4 : sata_via
>ata6: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 
>88:407f
>ata6: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
>ata6: dev 0 configured for UDMA/133
>scsi5 : sata_via
>  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
>  Type:   Direct-Access                      ANSI SCSI revision: 05
>SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
>SCSI device sda: drive cache: write back
>SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
>SCSI device sda: drive cache: write back
> /dev/scsi/host4/bus0/target0/lun0: p1
>Attached scsi disk sda at scsi4, channel 0, id 0, lun 0
>  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
>  Type:   Direct-Access                      ANSI SCSI revision: 05
>SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
>SCSI device sdb: drive cache: write back
>SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
>SCSI device sdb: drive cache: write back
> /dev/scsi/host5/bus0/target0/lun0: p1
>Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0
>
>
>Am I correct in assuming that the sata drives are giving me these errors, 
>and what shall I do? Could it possibly be a problem with the sata controller 
>rather than the drives?
>
>me@A1:~$ cat /proc/mdstat
>Personalities : [raid1]
>md0 : active raid1 sda1[0] sdb1[1]
>      390708736 blocks [2/2] [UU]
>
>unused devices: <none>
>
>I have done some testing with different sata controllers and recently switched 
>another server from the built in
>sata controller on the A8v (via8237 controller) motherboard to  an add in pci 
>promise sata II150 card.
>
>I think I have seen conflicts between the sata_via and sata_promise and I 
>already have a sata_promise card in the system for future expandability.
>
>I am running the debian stock 2.6.12-1-386 kernel and debian sarge with mdadm 
>ii  mdadm          1.9.0-4sarge1  Manage MD devices aka Linux Software Raid
>
>
>1:/var/log# lsmod|grep sata
>sata_via                8452  2
>sata_promise            9988  0
>libata                 44164  2 sata_via,sata_promise
>scsi_mod              129096  4 sr_mod,sata_promise,libata,sd_mod
>
>Thank you very much.
>
>Mitchell
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>


-- 

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[Technomage]

THANK YOU! :)

it appears this might be related to some of the errors a friend of mine got 
(ref: Re: recovering data on a failed raid-0 installation).

after a bit more research, it does appears that a kernel bug in combination 
with some "fast and loose" protocol usage on a laptop IDE interface may have 
been at fault.

more research on this forthcoming when a drive imager device arrives 
tomorrow....

******* error output
the error reported in his case was:

ata3 status = status 0x51 { DriveReady SeekComplete Error } 
0x40 {Unrecoverable Error } <repeated 5 times>

scsi error 2010 0x8000002 
return code = sdb current sense key medium error 
additional sense unrecovered read error 
auto realocate failed. 
end request i/o error /dev/sdb sector 22629482 
I/O error in filesystem  
md0 metadata device md0 block 0x29a1578 
xfs log mount recovery error failed error 5
xfs log mount failed mount i/o error .... kernel panic! .....

On Thursday 30 March 2006 10:26, you wrote:
> Party line: It's a faulty cable (on both drives? triggered by rsync?
> Doesn't show up under 'badblocks'? hah!)
>
> Check out the linux-ide archive for my (and others) reports.
>
> I've had lots of issues like this - spurious and IMHO incorrect error
> messages. Only certain types of disk access cause them - xfs_repair and
> rsync seem to tickle it.
>
> With 2.6.15 I had lots of *very* scary moments with multiple disk
> failures on a raid5 during xfs_repair.
> I think it's down to the 'basic' error handling in the libata code and
> certain disks/controllers being loose with the protocol. They then
> identified problems in 'fua' (IIRC) handling which was pulled for 2.6.16.
>
> 2.6.16 seems to be much better (fewer 'odd' errors reported and md
> doesn't mind)
>
> David
> PS Mitchell - you're still using Verizon and I still live off the edge
> of their known world (in the UK) so I don't expect you'll get this reply
> - hard luck my friend - get a better ISP!)
>
> Mitchell Laks wrote:
> >Hi,
> >
> >I have a production server in place at a remote site.
> >I have a single system drive that is an ide drive
> >and two data drives that are on a via SATA controller in a raid1
> >configuration.
> >
> >I am monitoring the /var/log/messages and I get messages every few days
> >
> >Mar 22 23:31:36 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete
> > Error } Mar 22 23:31:36 A1 kernel: ata6: error=0x84 { DriveStatusError
> > BadCRC }
> >
> >Mar 23 23:20:12 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete
> > Error } Mar 23 23:20:12 A1 kernel: ata5: error=0x84 { DriveStatusError
> > BadCRC } Mar 23 23:32:03 A1 kernel: ata6: status=0x51 { DriveReady
> > SeekComplete Error } Mar 23 23:32:04 A1 kernel: ata6: error=0x84 {
> > DriveStatusError BadCRC }
> >
> >Mar 24 23:22:45 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete
> > Error } Mar 24 23:22:45 A1 kernel: ata5: error=0x84 { DriveStatusError
> > BadCRC }
> >
> >
> >Mar 27 23:16:57 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete
> > Error } Mar 27 23:16:57 A1 kernel: ata5: error=0x84 { DriveStatusError
> > BadCRC }
> >
> >Mar 28 23:10:16 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete
> > Error } Mar 28 23:10:17 A1 kernel: ata5: error=0x84 { DriveStatusError
> > BadCRC } Mar 28 23:23:32 A1 kernel: ata6: status=0x51 { DriveReady
> > SeekComplete Error } Mar 28 23:23:32 A1 kernel: ata6: error=0x84 {
> > DriveStatusError BadCRC }
> >
> >
> >Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete
> > Error } Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError
> > BadCRC }
> >
> >Interestingly by the logs I see that they have occured
> >
> >March 1,2,3,8,14,17x3,20x4,21,22,23x2,24,27,28x2,29.
> >
> >(x2 means two errors as in above example).
> >
> >Also they occur during the activity of the cron job I do at 11pm to rsync
> >backup the sata drive raid 1 to another server.
> >
> >here is the output of dmesg:
> >
> >
> >ata5: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023
> >88:407f
> >ata5: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
> >ata5: dev 0 configured for UDMA/133
> >scsi4 : sata_via
> >ata6: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023
> >88:407f
> >ata6: dev 0 ATA, max UDMA/133, 781422768 sectors: lba48
> >ata6: dev 0 configured for UDMA/133
> >scsi5 : sata_via
> >  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
> >  Type:   Direct-Access                      ANSI SCSI revision: 05
> >SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
> >SCSI device sda: drive cache: write back
> >SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
> >SCSI device sda: drive cache: write back
> > /dev/scsi/host4/bus0/target0/lun0: p1
> >Attached scsi disk sda at scsi4, channel 0, id 0, lun 0
> >  Vendor: ATA       Model: WDC WD4000YR-01P  Rev: 01.0
> >  Type:   Direct-Access                      ANSI SCSI revision: 05
> >SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
> >SCSI device sdb: drive cache: write back
> >SCSI device sdb: 781422768 512-byte hdwr sectors (400088 MB)
> >SCSI device sdb: drive cache: write back
> > /dev/scsi/host5/bus0/target0/lun0: p1
> >Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0
> >
> >
> >Am I correct in assuming that the sata drives are giving me these errors,
> >and what shall I do? Could it possibly be a problem with the sata
> > controller rather than the drives?
> >
> >me@A1:~$ cat /proc/mdstat
> >Personalities : [raid1]
> >md0 : active raid1 sda1[0] sdb1[1]
> >      390708736 blocks [2/2] [UU]
> >
> >unused devices: <none>
> >
> >I have done some testing with different sata controllers and recently
> > switched another server from the built in
> >sata controller on the A8v (via8237 controller) motherboard to  an add in
> > pci promise sata II150 card.
> >
> >I think I have seen conflicts between the sata_via and sata_promise and I
> >already have a sata_promise card in the system for future expandability.
> >
> >I am running the debian stock 2.6.12-1-386 kernel and debian sarge with
> > mdadm ii  mdadm          1.9.0-4sarge1  Manage MD devices aka Linux
> > Software Raid
> >
> >
> >1:/var/log# lsmod|grep sata
> >sata_via                8452  2
> >sata_promise            9988  0
> >libata                 44164  2 sata_via,sata_promise
> >scsi_mod              129096  4 sr_mod,sata_promise,libata,sd_mod
> >
> >Thank you very much.
> >
> >Mitchell
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[mitchell laks]

David Greaves <david <at> dgreaves.com> writes:

> 
> Check out the linux-ide archive for my (and others) reports.

I just read them and weeped.

> 
> I've had lots of issues like this - spurious and IMHO incorrect error
> messages. Only certain types of disk access cause them - xfs_repair and
> rsync seem to tickle it.

Interesting. rsync for me.

> With 2.6.15 I had lots of *very* scary moments with multiple disk
> failures on a raid5 during xfs_repair.
> I think it's down to the 'basic' error handling in the libata code and
> certain disks/controllers being loose with the protocol. They then
> identified problems in 'fua' (IIRC) handling which was pulled for 2.6.16.
> 
> 2.6.16 seems to be much better (fewer 'odd' errors reported and md
> doesn't mind)

"Fewer" - oh oh. Can you quantify this for me? I seem to be getting around 
8-9 /10 days = or averaging about 1 per rsync. 

I should check to see if the distribution is Poisson like distribution :).

I have not lost my raid1 yet. lucky me.

I am now very worried.

I need to do some testing off line with the new kernel  before 
putting out the fix. 

Is your experience also with an Asus board with a via vt8237 powered
 sata  connector?

Would you suggest I try the promise sata connector instead, before 
I try to move
over to the newer kernel? Or both? 
Could you give me more of your experience?

Thanks,

Mitchell

Thanks

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[David Greaves]

mitchell laks wrote:

>David Greaves <david <at> dgreaves.com> writes:
>  
>
>>2.6.16 seems to be much better (fewer 'odd' errors reported and md
>>doesn't mind)
>>    
>>
>
>"Fewer" - oh oh. Can you quantify this for me? I seem to be getting around 
>8-9 /10 days = or averaging about 1 per rsync. 
>  
>
Not sure what triggers them - they're at the end of the message.

>I am now very worried.
>  
>
I didn't notice any data loss. I suspect I was lucky.

>I need to do some testing off line with the new kernel  before 
>putting out the fix. 
>
>Is your experience also with an Asus board with a via vt8237 powered
> sata  connector?
>  
>
Asus A7V600-X mainboard

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600
AGP] Host Bridge (rev 80)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA
RAID Controller (rev 80)
I also have a plug-in
0000:00:0a.0 Mass storage controller: Silicon Image, Inc. SiI 3112
[SATALink/SATARaid] Serial ATA Controller (rev 02)

>Would you suggest I try the promise sata connector instead, before 
>I try to move
>over to the newer kernel? Or both? 
>  
>
Yes. There is a *definite* chance that there is a hardware fault and you
need to try hard to confirm that it's not.
I ended up spending over $100 on a new (unneeded) PSU - just in case...

>Could you give me more of your experience?
>  
>
Honestly it's pretty well documented on linux-ide.

The only think I haven't always mentioned is when the array went down.
I always got it back through an assemble/force - although once I had 2
of 3 kicked so quickly that they had the same (lower) event count and I
used the 'faulty' devices to reconstruct the array.

David


grep ata messages.log:
Mar 26 15:46:47 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 26 15:46:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 26 15:47:33 haze kernel: ata2: status=0x59 { DriveReady SeekComplete
DataRequest Error }
Mar 26 15:47:33 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 26 15:47:33 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 26 16:20:22 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 26 16:20:22 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 26 19:50:12 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 26 19:50:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:08 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:17 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:29 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:33 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:33 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:38 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:38 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:45 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:45 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:52 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:56 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:56 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:25:59 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:25:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:26:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:26:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:26:14 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:26:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:26:20 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:47 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:47 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:48 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:48 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:49 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:49 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:51 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 08:38:51 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 08:38:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 09:13:45 haze kernel: ata1: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 09:13:45 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 09:29:36 haze kernel: ata1: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 09:29:36 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 10:06:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 10:06:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 10:19:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 10:19:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 12:00:53 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 12:00:53 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 12:50:08 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 12:50:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 17:22:47 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 17:22:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 27 17:57:13 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 27 17:57:13 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:26:06 haze kernel: ata2: status=0xd8 { Busy }
Mar 28 06:27:06 haze kernel: ata2: status=0xd8 { Busy }
Mar 28 06:27:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:14 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:16 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:16 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:19 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:19 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:21 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:21 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:22 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:22 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:52 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:27:54 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:27:54 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:28:26 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:28:26 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:28:39 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:28:39 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 06:29:05 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 06:29:05 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 09:01:55 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 09:01:55 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 09:39:02 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 09:39:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 11:31:54 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 11:31:54 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 12:07:52 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 12:07:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 12:12:41 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 12:12:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 12:39:34 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 12:39:34 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 12:49:41 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 12:49:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 13:45:54 haze kernel: MCE: The hardware reports a non fatal,
correctable incident occurred on CPU 0.
Mar 28 13:52:15 haze kernel: ata1: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 13:52:15 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 13:55:41 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 13:55:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 18:34:35 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 18:34:35 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 19:02:48 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 19:02:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 28 19:24:27 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 28 19:24:27 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:09 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:09 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:10 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:10 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:11 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:11 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:14 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:15 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:15 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:17 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:20 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:23 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:23 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:34 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:34 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:36 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:57 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:57 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:58 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:58 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:25:59 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:25:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:12 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:20 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 06:26:55 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 06:26:55 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 08:13:15 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 08:13:15 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 11:22:05 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 29 11:22:05 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 29 19:18:55 haze kernel: MCE: The hardware reports a non fatal,
correctable incident occurred on CPU 0.
Mar 30 06:25:02 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:09 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:09 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:12 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:24 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:24 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:36 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:37 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:37 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:40 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:40 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:41 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:53 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:53 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:25:58 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:00 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:00 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:06 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:29 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:38 haze kernel: ata1: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:38 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:44 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:44 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:26:59 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:26:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 06:27:11 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 06:27:11 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 10:13:30 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 10:13:30 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 12:25:31 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 12:25:31 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 16:18:52 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 16:18:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 30 16:34:59 haze kernel: ata1: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 30 16:34:59 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:03 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:04 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:10 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:10 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:16 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:16 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:17 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:20 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:21 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:21 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:26 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:26 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:02 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:08 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:14 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:20 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:29 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:30 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:30 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:46 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:46 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:47 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }
Mar 31 06:26:51 haze kernel: ata2: no sense translation for op=0x28
cmd=0x25 status: 0x51
Mar 31 06:26:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
Error }

-- 

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[Mitchell Laks]

On Friday 31 March 2006 03:57, David Greaves wrote:

> Yes. There is a *definite* chance that there is a hardware fault and you
> need to try hard to confirm that it's not.
> I ended up spending over $100 on a new (unneeded) PSU - just in case...
You mean that it may (possibly) simply be a hardware fault, not the kernel 
issue  possibly related to fua (whatever)? I think not as I have 4 servers, 
and have seen this on 2 separate servers while  using the via vt8237 
controller.

I would guess that your vt8237 is controlling ata2 and ata1 (if you have  no 
other pci card sata controllers on the machine...). Please can you check if 
that is true  (boot messages in dmesg - however these are probably already 
overwritten by those kernel errors). 

Secondly - I see errors through yesterday. Are you saying that you still have 
problems AFTER you take all the steps of updating to 2.6.16 etc? So what is 
the point of the update?

Does it happen on the silicon image controller too? Is it simply a problem 
with the via controller chipset and the drivers?

Is this definitely only a sata issue and not pata as well?

thanks
Mitchell

>
> >Could you give me more of your experience?
>
> Honestly it's pretty well documented on linux-ide.
>
> The only think I haven't always mentioned is when the array went down.
> I always got it back through an assemble/force - although once I had 2
> of 3 kicked so quickly that they had the same (lower) event count and I
> used the 'faulty' devices to reconstruct the array.
>
> David
>
>
> grep ata messages.log:
> Mar 26 15:46:47 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 26 15:46:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 26 15:47:33 haze kernel: ata2: status=0x59 { DriveReady SeekComplete
> DataRequest Error }
> Mar 26 15:47:33 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 26 15:47:33 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 26 16:20:22 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 26 16:20:22 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 26 19:50:12 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 26 19:50:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:08 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:17 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:29 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:33 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:33 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:38 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:38 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:45 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:45 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:52 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:56 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:56 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:25:59 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:25:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:26:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:26:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:26:14 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:26:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:26:20 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 06:27:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 06:27:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:47 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:47 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:48 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:48 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:49 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:49 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:51 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 08:38:51 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 08:38:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 09:13:45 haze kernel: ata1: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 09:13:45 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 09:29:36 haze kernel: ata1: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 09:29:36 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 10:06:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 10:06:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 10:19:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 10:19:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 12:00:53 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 12:00:53 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 12:50:08 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 12:50:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 17:22:47 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 17:22:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 27 17:57:13 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 27 17:57:13 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:26:06 haze kernel: ata2: status=0xd8 { Busy }
> Mar 28 06:27:06 haze kernel: ata2: status=0xd8 { Busy }
> Mar 28 06:27:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:14 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:16 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:16 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:19 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:19 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:21 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:21 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:22 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:22 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:36 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:52 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:27:54 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:27:54 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:28:26 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:28:26 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:28:39 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:28:39 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 06:29:05 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 06:29:05 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 09:01:55 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 09:01:55 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 09:39:02 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 09:39:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 11:31:54 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 11:31:54 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 12:07:52 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 12:07:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 12:12:41 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 12:12:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 12:39:34 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 12:39:34 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 12:49:41 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 12:49:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 13:45:54 haze kernel: MCE: The hardware reports a non fatal,
> correctable incident occurred on CPU 0.
> Mar 28 13:52:15 haze kernel: ata1: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 13:52:15 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 13:55:41 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 13:55:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 18:34:35 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 18:34:35 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 19:02:48 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 19:02:48 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 28 19:24:27 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 28 19:24:27 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:09 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:09 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:10 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:10 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:11 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:11 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:14 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:15 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:15 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:17 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:20 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:23 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:23 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:34 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:34 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:36 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:57 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:57 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:58 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:58 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:25:59 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:25:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:12 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:20 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 06:26:55 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 06:26:55 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 08:13:15 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 08:13:15 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 11:22:05 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 29 11:22:05 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 29 19:18:55 haze kernel: MCE: The hardware reports a non fatal,
> correctable incident occurred on CPU 0.
> Mar 30 06:25:02 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:09 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:09 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:12 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:12 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:24 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:24 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:36 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:36 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:37 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:37 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:40 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:40 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:41 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:41 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:53 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:53 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:25:58 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:25:58 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:00 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:00 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:06 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:06 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:29 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:38 haze kernel: ata1: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:38 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:44 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:44 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:26:59 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:26:59 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 06:27:11 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 06:27:11 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 10:13:30 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 10:13:30 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 12:25:31 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 12:25:31 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 16:18:52 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 16:18:52 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 30 16:34:59 haze kernel: ata1: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 30 16:34:59 haze kernel: ata1: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:03 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:03 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:04 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:04 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:10 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:10 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:16 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:16 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:17 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:17 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:20 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:21 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:21 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:26 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:26 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:25:28 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:25:28 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:02 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:02 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:08 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:08 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:14 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:14 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:20 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:20 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:29 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:29 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:30 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:30 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:46 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:46 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:47 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:47 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }
> Mar 31 06:26:51 haze kernel: ata2: no sense translation for op=0x28
> cmd=0x25 status: 0x51
> Mar 31 06:26:51 haze kernel: ata2: status=0x51 { DriveReady SeekComplete
> Error }

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[David Greaves]

Mitchell Laks wrote:

>Hi,
>
>I have a production server in place at a remote site. 
>I have a single system drive that is an ide drive 
>and two data drives that are on a via SATA controller in a raid1 
>configuration.
>
>I am monitoring the /var/log/messages and I get messages every few days
>
>Mar 22 23:31:36 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 22 23:31:36 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>Mar 23 23:20:12 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 23 23:20:12 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>Mar 23 23:32:03 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 23 23:32:04 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>Mar 24 23:22:45 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 24 23:22:45 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>
>
>Mar 27 23:16:57 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 27 23:16:57 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>
>Mar 28 23:10:16 A1 kernel: ata5: status=0x51 { DriveReady SeekComplete Error }
>Mar 28 23:10:17 A1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>Mar 28 23:23:32 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 28 23:23:32 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>
>
>Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
>Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
>  
>
Look here:

http://marc.theaimsgroup.com/?l=linux-kernel&m=114386015009790&w=2

I don't know he's right - you may want to get into it...

David

Re: sata controllers status=0x51 { DriveReady SeekComplete Error } error=0x84 { DriveStatusError BadCRC }

[Mark Hahn]

> >Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error }
> >Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }

BadCRC is unambiguous: the packet was corrupted.  that could happen several
ways, the most common of which is bogus cables (remember, PATA is 18",
not longer, with the ends plugged in.)  but things like flakey power,
overclocking, or controllers programmed with wrong timing could also 
cause such errors.