Bit of background: I had to recently wipe my whole Unraid server (boot drive was messed up and I wanted a fresh start), it was working fine about 2 months ago but on Dec 1st, it started a parity sync as scheduled and had loads of read errors on 4 of my array drives and the parity drive itself. I have attached my diagnostics and syslog. Any ideas of what went wrong and what I could do to fix this?

 

I can provide more info, thanks in advance.

 

 

elux-diagnostics-20231206-2105.zip elux-syslog-20231206-2046.zip

Looks like a controller or power issue:

 

Dec  6 20:33:21 elux kernel: ata35: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:35 elux kernel: ata37: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:35 elux kernel: ata36: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:35 elux kernel: ata38: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:35 elux kernel: ata12: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:40 elux kernel: ata38: COMRESET failed (errno=-16)
Dec  6 20:33:40 elux kernel: ata36: COMRESET failed (errno=-16)
Dec  6 20:33:40 elux kernel: ata12: COMRESET failed (errno=-16)
Dec  6 20:33:40 elux kernel: ata37: COMRESET failed (errno=-16)
Dec  6 20:33:45 elux kernel: ata38: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:45 elux kernel: ata12: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:45 elux kernel: ata37: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:45 elux kernel: ata36: link is slow to respond, please be patient (ready=0)
Dec  6 20:33:50 elux kernel: ata38: COMRESET failed (errno=-16)
Dec  6 20:33:50 elux kernel: ata12: COMRESET failed (errno=-16)
Dec  6 20:33:50 elux kernel: ata36: COMRESET failed (errno=-16)
Dec  6 20:33:50 elux kernel: ata37: COMRESET failed (errno=-16)
Dec  6 20:33:50 elux kernel: ata35: COMRESET failed (errno=-16)

 

Since disk4 is on the same controller and it wasn't affected see if the other ones share a power cable/splitter.

I may have found what was causing these issues (i've had issues in the past before re-setting the server with drives being 'disabled' and 'contents emulated'). I made a little diagram of what the power structure was like before and what I changed it to now. I have removed the SATA extension cable (I believe I originally put it there for future expansion) but I have no idea what I was thinking before. Hopefully, now the power structure is much better and I don't have any issues in the future, I am currently running a parity sync and seems to be going well.

Thank you @JorgeBfor your help with this, I will mark it as the solution once the parity sync is complete.

Parity sync completed without any errors, thanks again for your help @JorgeB