Help, new to Unraid - Parity drive has been disabled with 11484 errors, before I do anything please help with what I should do? Logs and Diagnostic attached please help

kaha-syslog-20210907-0523.zip kaha-diagnostics-20210907-1523.zip

Just to check - it looks like you have parity2 but not parity1?

 

A drive gets disabled when a write to it fails.   The diagnostics show lots of resets occurring on the parity2 drive, although the smart information looks OK.    This is typically an issue with the power and/or SATA cabling to the drive so that should be carefully checked.

 

To re-enable the parity drive you may need to rebuild it from all the data drives.   I did not check them but are they all fine as far as you know as that is necessary to be able to rebuild parity.  If going this route you could also consider switching the drive to be parity1 if you are going to run with single  parity going forward.
 

FYI:

• the diagnostics include the syslog so no need to provide it separately
• you have mover logging enabled, You do not want to leave that enabled unless you are investigating a mover related issue as it both clutters the syslog and also the file names are not anonymised which has privacy implications.

So I think I followed all of the above advice, all new sata cables, and change the power cables over, reset the Parity drive to parity1, and re-enable, ran SMART test and everything looked ok. But it has happened again. (Logs and Diagnostics attached.) Your thoughts or advice would be much appreciated.

 

kaha-diagnostics-20210915-1243.zip kaha-syslog-20210915-0237.zip

10 minutes ago, Kiwiconcord said:

Logs and Diagnostics attached

On 9/7/2021 at 2:08 AM, itimpi said:

the diagnostics include the syslog so no need to provide it separately

 

Connection problems with parity. Check all connections, both ends, power and SATA, including splitters.

 

I replaced all cables last time and plug directly into power supply removing splitter, I am new to Unraid but not to IT, surely the connection issue is the fact that it is not seeing the drive as sdj anymore, as the same drive is in Unassigned Devices and mount point is sdk?   

 

If I reboot as I did last time this happened, it will remount to sdj then I will be able to reassign back to the array and run parity check and it will be fine until next time. Am I missing something but why is it assigning it a different mount point, and what is causing that?

6 hours ago, Kiwiconcord said:

the connection issue is the fact that it is not seeing the drive as sdj anymore

This is a symptom of the connection issue, not the reason for it.