Parity errors after unclean shutdown

[yyquest]

Hi all,

 

There was a power outage and my server was not cleanly shutdown. When the array was brought back online, the parity check showed 40 errors. I re-ran the checks and there were still 40 errors, option "write corrections to parity" checked. Any suggestions on how I can resolve these errors?

 

The server has not been rebooted after the initial parity check. Attached is the diagnostics report.

 

Thanks very much in advance!

tower-diagnostics-20220803-2323.zip

[JorgeB]

Auto pariyt check after an unclean shutdown is non correct, last one you ran was correct, so there should be no more errors on the next check.

[yyquest]

Sorry, forgot to add that my server is configured not to start array automatically after a shutdown. This means both the first and second parity checks were initiated manually. Both checks show identical number of errors (40).

 

Should I run parity-check a third time?

[JorgeB]

Yes, both checks were correct and found the same errors, this might suggest a problem with one of the disks, since there were several ATA errors with disk3 replace cables there and run another check.

[yyquest]

I see. Let me find a spare SATA cable first and try again. Thanks!

[yyquest]

On 8/3/2022 at 11:59 PM, JorgeB said:

Yes, both checks were correct and found the same errors, this might suggest a problem with one of the disks, since there were several ATA errors with disk3 replace cables there and run another check.

Hi,

 

Reporting back after I changed the SATA cable.

 

Actually just before I swapped out the SATA cable, the number of errors from (non-correcting) parity checks reached over 700 after a few more runs. The same number of errors remained after I changed the SATA cable, but (not sure if it was the change of cable or re-seating the cable that did the trick) after I ran correcting parity check once, my system has remained error free. I have run at least 5 non-correcting parity checks since swapping the cable.

 

Does this mean I can rest easy that there are no other faults in my array?

 

 

tower-diagnostics-20220814-1823.zip

[JorgeB]

Diags look clean, no more ATA errors, just keep doing the scheduled checks and any more sync errors grab diags before rebooting.

[yyquest]

Great, thanks for your helpful suggestions.

 

By the way, this is not related to my original question, but is it recommended to use something like the Dynamix File Integrity plugin so, in case of problems, I have some ideas of which file may have been corrupted?

[JorgeB]

29 minutes ago, yyquest said:

but is it recommended to use something like the Dynamix File Integrity plugin so, in case of problems, I have some ideas of which file may have been corrupted?

IMHO it's always good to have checksums for all files, using the plugin or any other tool, like corz for example.