Hi fellow unraiders,

I've been chasing down some errors on my 8tb parity disk for some weeks now without any resolve and was hoping I could get some advice from the brains trust.

The errors I'm seeing on the parity drive are below (where the * lines repeat 6 more times):

Nov 27 23:08:05 nas kernel: ata7.00: exception Emask 0x10 SAct 0x7f00 SErr 0x4050000 action 0xe frozen
Nov 27 23:08:05 nas kernel: ata7.00: irq_stat 0x08000040, interface fatal error, connection status changed
Nov 27 23:08:05 nas kernel: ata7: SError: { PHYRdyChg CommWake DevExch }
* Nov 27 23:08:05 nas kernel: ata7.00: failed command: WRITE FPDMA QUEUED
* Nov 27 23:08:05 nas kernel: ata7.00: cmd 61/90:40:18:d8:52/00:00:30:01:00/40 tag 8 ncq dma 73728 out
* Nov 27 23:08:05 nas kernel: ata7.00: status: { DRDY }
Nov 27 23:08:05 nas kernel: ata7: hard resetting link
Nov 27 23:08:06 nas kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Nov 27 23:08:06 nas kernel: ata7.00: configured for UDMA/133
Nov 27 23:08:06 nas kernel: ata7: EH complete

Following advice from other peoples posts, I've:

• Replaced the SATA cable to the disk 3 times, including buying some cable matters ones which feel notably higher quality and really click in but unfortunately haven't made any difference.

• Swapped which SATA port it plugs into on the motherboard

• Set libata.force=3.0Gbps

• Swapped which string of SATA power cables it was connected to

• Installed an ASM1061 controller and connected the parity drive to it

I did all the above one by one until the error returned, and then i tried the next thing. Some other observations:

• Parity checks never return any errors

• No SMART alerts

• I'll see a handful of these errors and then it'll be clean for the next few days (or weeks?)

• No errors on any other drives

• Very rare to see the errors while performing a parity check (for example - last FPDMA error was from 23:08 last night, kicked off a parity check this morning - currently at 91% of 8TB - and no further errors)

Just wondering if these are errors to worry about or not? If i should try swap this disk into another slot (perhaps one that's mostly idle and only occasionally spins up)? Or any other advice that can be thrown my way..

Thanks!

nas-diagnostics-20251128-2221.zip

Edited November 28, 2025Nov 28 by ideasman

If you already did all that and the issue persists, I would just ignore it for now; it should not cause any issues other than a slight delay accessinbg the disk when those errors happen.