One data disk and one parity disk have apparently the same errors:

 

[Tue Sep  5 15:51:34 2023] ata1: hard resetting link
[Tue Sep  5 15:51:39 2023] ata1: link is slow to respond, please be patient (ready=0)
[Tue Sep  5 15:51:44 2023] ata1: COMRESET failed (errno=-16)
[Tue Sep  5 15:51:44 2023] ata1: hard resetting link
[Tue Sep  5 15:51:46 2023] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[Tue Sep  5 15:51:46 2023] ata1.00: configured for UDMA/100
[Tue Sep  5 15:51:46 2023] ata1: EH complete
[Tue Sep  5 15:52:15 2023] ata1.00: exception Emask 0x50 SAct 0x80e00007 SErr 0x4890800 action 0xe frozen
[Tue Sep  5 15:52:15 2023] ata1.00: irq_stat 0x0d400040, interface fatal error, connection status changed
[Tue Sep  5 15:52:15 2023] ata1: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:00:40:29:b2/05:00:00:00:00/40 tag 0 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:08:80:2e:b2/05:00:00:00:00/40 tag 1 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:10:c0:33:b2/05:00:00:00:00/40 tag 2 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:a8:00:19:b2/05:00:00:00:00/40 tag 21 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:b0:40:1e:b2/05:00:00:00:00/40 tag 22 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/40:b8:80:23:b2/05:00:00:00:00/40 tag 23 ncq dma 688128 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1.00: failed command: READ FPDMA QUEUED
[Tue Sep  5 15:52:15 2023] ata1.00: cmd 60/80:f8:c0:28:b2/00:00:00:00:00/40 tag 31 ncq dma 65536 in
                                    res 40/00:08:80:2e:b2/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
[Tue Sep  5 15:52:15 2023] ata1.00: status: { DRDY }
[Tue Sep  5 15:52:15 2023] ata1: hard resetting link
[Tue Sep  5 15:52:21 2023] ata1: link is slow to respond, please be patient (ready=0)
[Tue Sep  5 15:52:25 2023] ata1: COMRESET failed (errno=-16)
[Tue Sep  5 15:52:25 2023] ata1: hard resetting link
[Tue Sep  5 15:52:28 2023] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[Tue Sep  5 15:52:28 2023] ata1.00: configured for UDMA/100
[Tue Sep  5 15:52:28 2023] ata1: EH complete

 

I've sent one disk for RMA however now the parity disk (ata1) is showing these errors. Quick smart reports no errors.

 

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      4691         -
# 2  Short offline       Completed without error       00%      3099         -
# 3  Short offline       Completed without error       00%       485         -
# 4  Short offline       Completed without error       00%        41         -
# 5  Short offline       Completed without error       00%        28         -

 

Now what I think happens is, and this is kinda weird. I _think_ Parity + Disk 1 + Disk 2 + Disk 3 + Disk 4 + Cache SSD are on the same sata cable. The PSU came with one cable I believe, or perhaps 2 - I can't remember.

 

The thing that troubles me is that this worked fine for the last 2 years I think and then suddenly these errors started happening. I added a brand new 8TB disk to rebuild from parity, and while it's working now - in the beginning, the first 1% or so was throwing these errors, now it works without issues.

 

Could it be that the PSU rail doesn't supply enough power - and if so - how do I check?

Should I do an extended SMART on the parity?

 

Right now unraid states there's going to take about 15h for the parity rebuild which is fine as I would like to keep the data on the disks

 

Please post the diagnostics.

Uploaded

flareon-diagnostics-20230905-1623.zip

ATA errors are about parity, looks more like a power/connection problem, check/replace cables.

 

Disk1 was already disabled, so we cannot see what happened, but SMART looks fine, most likely also a power/connection problem.

Can you clarify why this setup worked fine for the last 2 years and only now started happening? How do I check if its the PSU - can I check the voltage via bios to confirm somehow? Additionally - how would I go about having 6 drives connected, what PSU _should_ I use?

A cable or a PSU like anything else can go bad at any time, my TV worked fine for 5 years straight, then it didn't yesterday.

without swapping the cables - non stop errors like above. Swapped the cables, started the data-rebuild - the first 1% threw a lot of these, then I waited until the disks reach about 35-40'C (i.e. let them running for a while), since then no errors. Perhaps its the power cable - how do I check - connect a different drive and see if it throws the same errors?

38 minutes ago, Shagon said:

connect a different drive and see if it throws the same errors?

You can, the SATA cable would still be my main suspect, at least for disk1.

I'm 3 hours in, 20% done - no errors, I'm writing it down to sata cable issues for now.