swamiforlife Posted April 27, 2020 Share Posted April 27, 2020 Hello, I am running Unraid 6.8.0 and i havent done a parity check in a long time. I have dual parity drives. I ran a parity check and i got Sync Errors Corrected: 13624. I had 1 drive in my array with a few bad sectors. So does this mean that my parity will also be corrupt? Will my other data on other disks get corrupted? Or does this mean that parity fixed the data on the drive that was not readable due to bad sectors? Thanks for the help. Quote Link to comment
JorgeB Posted April 27, 2020 Share Posted April 27, 2020 Please post the diagnostics: Tools -> Diagnostics Quote Link to comment
swamiforlife Posted April 27, 2020 Author Share Posted April 27, 2020 Sorry I should have attached the diagnostics in the first place. I have attached them. Thanks for the help tower-diagnostics-20200427-1652.zip Quote Link to comment
JorgeB Posted April 27, 2020 Share Posted April 27, 2020 Apr 17 16:28:45 Tower emhttpd: unclean shutdown detected A few sync errors are normal, even expected, after an unclean shutdown. Quote Link to comment
swamiforlife Posted April 27, 2020 Author Share Posted April 27, 2020 Do you think that i should replace the disk with bad sectors? Also just for my understanding, when parity checking fixes errors is it changing data in the parity drives or the data drives? Also is it possible the parity checking with fixed errors can cause data to be corrupted? Quote Link to comment
JorgeB Posted April 27, 2020 Share Posted April 27, 2020 These sync errors are unrelated to a disk problem. Do you think that i should replace the disk with bad sectors? Which disk is it? You have too many for me to look at all SMART reports. Also just for my understanding, when parity checking fixes errors is it changing data in the parity drives or the data drives? Sync errors are always corrected on parity, never on data drives. Also is it possible the parity checking with fixed errors can cause data to be corrupted? No, it is possible is some rare cases to corrupt parity if there are read errors on a disk during a correcting check, hence why it's recommended that parity checks should always be non correct unless errors are expected, like after an unclean shutdown. Quote Link to comment
swamiforlife Posted April 27, 2020 Author Share Posted April 27, 2020 Disk number 14 Thanks for the help Quote Link to comment
JorgeB Posted April 27, 2020 Share Posted April 27, 2020 Looks mostly fine, there a single Reported_Uncorrect error, unless it keeps increasing it's fine, but you should run regular parity checks, once a month is usually the recommendation, it will catch any issues since it does a complete surface scan on all disks, basically same as an extended SMART test. Quote Link to comment
swamiforlife Posted April 27, 2020 Author Share Posted April 27, 2020 Ok, Thanks Quote Link to comment
eshchar Posted November 27, 2021 Share Posted November 27, 2021 I have SYNC ERRORS CORRECTED 1096 and i now it is corrupted data because sum of my files (db) are malformed is there a way to now which files are corrupted? tower-diagnostics-20211127-1151.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.