February 8, 201214 yr I got this error this morning when waking from sleep: Feb 8 08:00:24 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 (Errors) Feb 8 08:00:24 Tower kernel: ata1.00: irq_stat 0x00020002, device error via D2H FIS (Errors) Feb 8 08:00:24 Tower kernel: ata1.00: failed command: WRITE DMA (Minor Issues) Feb 8 08:00:24 Tower kernel: ata1.00: cmd ca/00:38:17:c1:00/00:00:00:00:00/e0 tag 0 dma 28672 out (Drive related) Feb 8 08:00:24 Tower kernel: res 51/84:28:17:c1:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Feb 8 08:00:24 Tower kernel: ata1.00: status: { DRDY ERR } (Drive related) Feb 8 08:00:24 Tower kernel: ata1.00: error: { ICRC ABRT } (Errors) Feb 8 08:00:24 Tower kernel: ata1: hard resetting link (Minor Issues) Feb 8 08:00:26 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) Feb 8 08:00:26 Tower kernel: ata1.00: configured for UDMA/100 (Drive related) Feb 8 08:00:26 Tower kernel: ata1: EH complete (Drive related) Feb 8 08:00:26 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Feb 8 08:00:26 Tower kernel: ata1.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) Feb 8 08:00:26 Tower kernel: ata1.00: failed command: WRITE DMA (Minor Issues) Feb 8 08:00:26 Tower kernel: ata1.00: cmd ca/00:38:17:c1:00/00:00:00:00:00/e0 tag 0 dma 28672 out (Drive related) Feb 8 08:00:26 Tower kernel: res 5e/37:00:00:00:00/00:00:40:00:5e/00 Emask 0x12 (ATA bus error) (Errors) Feb 8 08:00:26 Tower kernel: ata1.00: status: { DRDY DRQ } (Drive related) Feb 8 08:00:26 Tower kernel: ata1.00: error: { IDNF ABRT } (Errors) Feb 8 08:00:26 Tower kernel: ata1: hard resetting link (Minor Issues) Feb 8 08:00:26 Tower kernel: ata1: controller in dubious state, performing PORT_RST (System) Syslog attached. 5b14, NCQ Enabled. I will swap the disk (Parity) to the Mobos controller and test for a week (unless someone has a good idea otherwise...) syslog-2012-02-08.txt
February 8, 201214 yr This indicates a SATA or power cable problem. See here: http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_Interface_Issues
February 8, 201214 yr Author That error happened 24 seconds after it woken up from S3 sleep, so I don't think the array was even running at that point. I've done three parity checks and copied over 300GB to the server and that error didn't crop up. I think its something to do with the initiation/drivers. Time will tell, I'm still using the same cable into the mobo port, so we'll see.
Archived
This topic is now archived and is closed to further replies.