[  477.971022] ata1.00: exception Emask 0x50 SAct 0xc00 SErr 0x290b02 action 
0xe frozen
[  477.971107] ata1.00: irq_stat 0x01400000, PHY RDY changed
[  477.971166] ata1: SError: { RecovComm UnrecovData Persist HostInt PHYRdyChg 
10B8B BadCRC }
[  477.971243] ata1.00: failed command: READ FPDMA QUEUED
[  477.971305] ata1.00: cmd 60/a8:50:00:13:ed/00:00:05:00:00/40 tag 10 ncq 
86016 in
[  477.971308]          res 40/00:58:a8:13:ed/00:00:05:00:00/40 Emask 0x50 
(ATA bus error)
[  477.971449] ata1.00: status: { DRDY }
[  477.971501] ata1.00: failed command: READ FPDMA QUEUED

I was using dd to copy /dev/sda3 to /dev/sdb3 on a system that is usually 
running Windows but doesn't appear to have hardware problems.  Then I saw the 
above message about a READ error on ata1.00 in the kernel log followed 
immediately by the below message about a WRITE error on ata2.00.  Any ideas 
about what might be happening here?  I've attached the entire kernel message 
log.

[  477.971763] ata1: hard resetting link
[  477.971796] ata2.00: exception Emask 0x50 SAct 0x3fffe000 SErr 0x480800 
action 0x6 frozen
[  477.971877] ata2.00: irq_stat 0x08000000, interface fatal error
[  477.971937] ata2: SError: { HostInt 10B8B Handshk }
[  477.971994] ata2.00: failed command: WRITE FPDMA QUEUED
[  477.972082] ata2.00: cmd 61/00:68:00:2c:e7/04:00:05:00:00/40 tag 13 ncq 
524288 out
[  477.972087]          res 40/00:68:00:2c:e7/00:00:05:00:00/40 Emask 0x50 
(ATA bus error)
[  477.972233] ata2.00: status: { DRDY }
[  477.972287] ata2.00: failed command: WRITE FPDMA QUEUED

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

Attachment: dmesg.txt.gz
Description: GNU Zip compressed data

_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main

Reply via email to