Merry0815

Parity Sync was succesful tonight, so seems it was the power connector. Thank you!

I checked that now and they were both connected to one power cable indeed which is then connected to my PicoPSU. I now unplugged everything and plugged it back together used a new 4pin to SATA splitter for the parity drive. I don´t have any other power cables left on my PSU. I´ll let it run another Parity check for the night and see what happens and update here. Thanks for the help already!

Hello, Lately my Unraid NAS reported a disabled parity drive. I assumed some cable came loose so I shut it down and made sure everything was secure. After doing that I started the Array again and Unraid started a ParityCheck. This parity Check ended with read Errors (see the diagnostics attached). Since then I tried to find out what is the problem, because I am doubting both my drives are failing, since they are rather new (6 months). I have been pulling SMART Reports of each drive (attached) and even did a extended SMART on the parity drive (disk0), which also failed without errors. So I am still suspecting some cable issue, because I see some SATA link log entries in the syslog, but I am not sure. Also when I run the array without the parity drive everything works fine and I can run a full ReadCheck of the drives (so no read Errors on disk1 there) Could someone help me find the issue here? sdc-nas-smart-20240709-0658.zipsdd-nas-smart-20240709-0709.zip I attached the diagnostic logs: nas-diagnostics-20240709-0651_ParityRead.zip

Did you ever find a solution to this? trying to make Hardware transcoding work on my binhex-jellyfin container and I think I am stuck at the same issue