exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen

[d_mcknight]

I recently noticed this repeating error in my system log (repeating every 10 seconds or so) after my system became non-responsive to the point VM's, local/remote WebGUI, and SSH would not respond.

Mar 2 11:39:37 MCKNIGHT-UNRAID kernel: ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Mar 2 11:39:37 MCKNIGHT-UNRAID kernel: ata10: irq_stat 0x00000040, connection status changed
Mar 2 11:39:37 MCKNIGHT-UNRAID kernel: ata10: SError: { CommWake DevExch }
Mar 2 11:39:37 MCKNIGHT-UNRAID kernel: ata10: limiting SATA link speed to 1.5 Gbps
Mar 2 11:39:37 MCKNIGHT-UNRAID kernel: ata10: hard resetting link
Mar 2 11:39:39 MCKNIGHT-UNRAID kernel: ata10: COMRESET failed (errno=-32)
Mar 2 11:39:39 MCKNIGHT-UNRAID kernel: ata10: reset failed (errno=-32), retrying in 8 secs
Mar 2 11:39:48 MCKNIGHT-UNRAID kernel: ata10: hard resetting link
Mar 2 11:39:49 MCKNIGHT-UNRAID kernel: ata10: SATA link down (SStatus 0 SControl 310)
Mar 2 11:39:49 MCKNIGHT-UNRAID kernel: ata10: EH complete

 

All of my storage devices appear fully functional (Boot drive, 2 Cache, 3 Array, 1 Optical Drive passed through to a VM, and one Unassigned device assigned to a non-running VM).

 

Any help diagnosing this issue would be much appreciated.

unraid-diagnostics-20180302-1123.zip

[JorgeB]

Is there any device connected to the onboard SATA port #6?

[d_mcknight]

11 hours ago, johnnie.black said:

Is there any device connected to the onboard SATA port #6?

 

No, I have ports 1,2,3,4,7 currently occupied according to my motherboard manual (MSI X99 Gaming Pro Carbon)

Edited March 3, 2018 by d_mcknight

[JorgeB]

Then it's likely a board problem, ATA10 is port #6 and is initially detected as not used, but then it thinks something is there, though it never succeeds in initializing the port.

[JorgeB]

There's one thing you can try, move one of your devices to port #6, maybe it works correctly if in use.

[d_mcknight]

1 minute ago, johnnie.black said:

Then it's likely a board problem, ATA10 is port #6 and is initially detected as not used, but then it thinks something is there, though it never succeeds in initializing the port.

 

Interesting.. I'll try connecting a drive and see what happens. How did you figure out ATA10 corresponds to port #6?

[JorgeB]

By looking at the syslog, ATA1 to 4 correspond to ports #7 to #10 and ATA5 to 10 ports #1 to #6.