nearcatch Posted September 3, 2023 Share Posted September 3, 2023 (edited) Running a correcting parity check and the "sync errors corrected" numbers is increasing a lot, but the parity check is in the space *after* the data. My biggest data drive is 18TB and the parity drives are both 20TB. The check is currently at 18.3 TB. My understanding of parity is that if the parity is bigger than the array, all the *extra* parity should just be 0? No drives are reporting any SMART errors, syslog seems clean other than an odd cron error that has to be unrelated. deepervisor-diagnostics-20230903-1437.zip Edited September 3, 2023 by hasown Quote Link to comment
itimpi Posted September 3, 2023 Share Posted September 3, 2023 There have been previous reports of this space sometimes not being correctly zeroed when the parity is initially built, but I do not think anyone knows why. I would let it complete this time and not get worried unless it continues to happen in future checks. Quote Link to comment
JorgeB Posted September 3, 2023 Share Posted September 3, 2023 Did you do a parity swap in the recent past? Quote Link to comment
nearcatch Posted September 3, 2023 Author Share Posted September 3, 2023 1 hour ago, JorgeB said: Did you do a parity swap in the recent past? Yes, I've done a couple of parity swaps to get the 20TB drives in. My previous parity drives are data drives now. Quote Link to comment
JorgeB Posted September 4, 2023 Share Posted September 4, 2023 There's known issue where sometimes the new parity capacity after a parity swap does not get correctly zeroed, so the first check will find those errors, it should be fine once you correct them. Quote Link to comment
nearcatch Posted September 4, 2023 Author Share Posted September 4, 2023 I precleared the parity drives to stress test them before doing the swaps, so I thought they would've been zeroed anyway. But I'll run a second parity check and see how it goes. Quote Link to comment
Solution JorgeB Posted September 4, 2023 Solution Share Posted September 4, 2023 14 minutes ago, hasown said: so I thought they would've been zeroed anyway It won't matter, bug is that Unraid writes something else instead of zeros to the extra parity capacity during the swap procedure, instead of actually zeroing it. Quote Link to comment
nearcatch Posted September 7, 2023 Author Share Posted September 7, 2023 Just following up to finish this thread: the second parity check just finished and 0 errors corrected. Hopefully helps someone in the future who searches for this issue. 1 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.