unRAID 6.11.5

Platform: Asrock Z690 Extreme + 13500k

Parity: WD140EDGZ

Array: 2xWD140EDGZ, 3xWD80EFAX, 1xWD80EMAZ

 

Replatformed machine in April. Parity checks set for quarterly and started June 1. During the parity check, I noticed some ata errors popping up in the syslog.

Jun  2 13:28:14 wintermute kernel: ata8.00: exception Emask 0x10 SAct 0x20000 SErr 0x840000 action 0x6 frozen
Jun  2 13:28:14 wintermute kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Jun  2 13:28:14 wintermute kernel: ata8: SError: { CommWake LinkSeq }
Jun  2 13:28:14 wintermute kernel: ata8.00: failed command: READ FPDMA QUEUED
Jun  2 13:28:14 wintermute kernel: ata8.00: cmd 60/00:88:a8:24:04/01:00:10:06:00/40 tag 17 ncq dma 131072 in
Jun  2 13:28:14 wintermute kernel:         res 40/00:00:a8:23:04/00:00:10:06:00/40 Emask 0x10 (ATA bus error)
Jun  2 13:28:14 wintermute kernel: ata8.00: status: { DRDY }
Jun  2 13:28:14 wintermute kernel: ata8: hard resetting link
Jun  2 13:28:14 wintermute kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun  2 13:28:14 wintermute kernel: ata8.00: supports DRM functions and may not be fully accessible
Jun  2 13:28:14 wintermute kernel: ata8.00: supports DRM functions and may not be fully accessible
Jun  2 13:28:14 wintermute kernel: ata8.00: configured for UDMA/133
Jun  2 13:28:14 wintermute kernel: ata8: EH complete
Jun  2 15:05:31 wintermute kernel: ata8.00: exception Emask 0x10 SAct 0x8000 SErr 0x840000 action 0x6 frozen
Jun  2 15:05:31 wintermute kernel: ata8.00: irq_stat 0x08000000, interface fatal error
Jun  2 15:05:31 wintermute kernel: ata8: SError: { CommWake LinkSeq }
Jun  2 15:05:31 wintermute kernel: ata8.00: failed command: READ FPDMA QUEUED
Jun  2 15:05:31 wintermute kernel: ata8.00: cmd 60/00:78:e8:20:81/01:00:08:02:00/40 tag 15 ncq dma 131072 in
Jun  2 15:05:31 wintermute kernel:         res 40/00:00:e8:1f:81/00:00:08:02:00/40 Emask 0x10 (ATA bus error)
Jun  2 15:05:31 wintermute kernel: ata8.00: status: { DRDY }
Jun  2 15:05:31 wintermute kernel: ata8: hard resetting link
Jun  2 15:05:31 wintermute kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

 

Had a small number of corrections written to parity (~5). Based on the errors, though, I decided to shut down the server and double check the SATA and power cables to all of the drives, and started the parity check again. This afternoon the server locked up. After power cycling, the server booted back up, but the parity drive was unresponsive. I swapped the SATA cable and then the SATA port, to no avail.

 

Picked up a new WD140EDGZ, shucked, and the system came right up with the new drive recognized. I started a parity rebuild, and am seeing similar errors on the new drive, too.

Jun  6 18:26:26 wintermute kernel: ata7.00: exception Emask 0x10 SAct 0x800 SErr 0x840000 action 0x6 frozen
Jun  6 18:26:26 wintermute kernel: ata7.00: irq_stat 0x08000000, interface fatal error
Jun  6 18:26:26 wintermute kernel: ata7: SError: { CommWake LinkSeq }
Jun  6 18:26:26 wintermute kernel: ata7.00: failed command: WRITE FPDMA QUEUED
Jun  6 18:26:26 wintermute kernel: ata7.00: cmd 61/50:58:00:cb:84/04:00:e7:00:00/40 tag 11 ncq dma 565248 out
Jun  6 18:26:26 wintermute kernel:         res 40/00:00:a0:c9:84/00:00:e7:00:00/40 Emask 0x10 (ATA bus error)
Jun  6 18:26:26 wintermute kernel: ata7.00: status: { DRDY }
Jun  6 18:26:26 wintermute kernel: ata7: hard resetting link
Jun  6 18:26:26 wintermute kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun  6 18:26:26 wintermute kernel: ata7.00: supports DRM functions and may not be fully accessible
Jun  6 18:26:26 wintermute kernel: ata7.00: supports DRM functions and may not be fully accessible
Jun  6 18:26:26 wintermute kernel: ata7.00: configured for UDMA/133
Jun  6 18:26:26 wintermute kernel: ata7: EH complete

 

Any thoughts on next steps for isolating the issue would be appreciated.

 

wintermute-diagnostics-20230606-1748.zip

Edited June 7, 20233 yr by mrMTB
adding version

Curiouser and curiouser - I dropped the "failed" parity drive into another machine, and it came up and tested fine (rapid). Am I looking at a hardware problem on the motherboard?

Both of those look more like a power/connection issue, did you try different cables, both power and SATA?

I've ordered a new set of SATA cables and will change the power setup once they come in. Thanks for taking a look, and I'll report back tomorrow.

So far I've been unable to reproduce the issue. Thanks for the help, @JorgeB