The day before yesterday, I was unable to Stop or Reboot the Array and as a last resort, I pressed the power button to shut it down.

After rebooting, the Parity-check started automatically and found 896 errors.

I have never had a parity-check error in all the times I have used Unraid (even when I was forced to power down).

The Array has two 12TB disks loaded as parity disks, one 10TB, and several 8TB and 6TB disks.

I think the error started to appear when the parity-check reached the 10TB drive, but I am not sure.

What is the next action I should take, I left the write-correction checkmark off in Parity-Check, so I don't think the error is corrected. Should I turn on this option and run Parity-Check again?

Thank you in advance.
 

 

unraid-diagnostics-20240920-1759.zip

Some parity errors after a forced shutdown is quite normal.   According to the diagnostics the check that was run was a correcting check so running a non-correcting check should now return 0 errors.

 

When did you add the 12TB parity drive?   The reason I am asking is that there appears to be a bug that has been difficult to fix where when you add a new parity drive larger than any other drive in the array the extra space beyond the size of the largest drive does not get zeroed as it should, and this gets picked up on the next arity check.   The fix is to run a correcting check from the Main tab (which should then report the same number of errors as it fixes them..   Leave any scheduled checks as non-correcting'

Thanks, that's a relief to hear. As a matter of fact, before I added the 12TB disk, I was using 10TB and 8TB as parity disks and then replaced them. So this is exactly the same situation. I'm going to try the parity check again and see if there are any errors.

On 9/20/2024 at 6:46 PM, itimpi said:

Some parity errors after a forced shutdown is quite normal.   According to the diagnostics the check that was run was a correcting check so running a non-correcting check should now return 0 errors.

 

When did you add the 12TB parity drive?   The reason I am asking is that there appears to be a bug that has been difficult to fix where when you add a new parity drive larger than any other drive in the array the extra space beyond the size of the largest drive does not get zeroed as it should, and this gets picked up on the next arity check.   The fix is to run a correcting check from the Main tab (which should then report the same number of errors as it fixes them..   Leave any scheduled checks as non-correcting'

Thank you so much！ I finished parity check with finding zero error.