AnnHashaway Posted August 5, 2021 Share Posted August 5, 2021 The last two times I have run a parity check, there are no reads or writes on the parity drive and it ends with over a billion errors. Unraid still says the Parity is valid. Whats the best way to start diagnosing this? Quote Link to comment
trurl Posted August 6, 2021 Share Posted August 6, 2021 Are you sure you are running a correcting parity check? With that many sync errors, are you sure parity was ever valid, ever built, nothing was done to invalidate it completely such as New Config-Trust Parity when that wasn't appropriate? Post diagnostics, hopefully you haven't rebooted since parity check. Quote Link to comment
AnnHashaway Posted August 6, 2021 Author Share Posted August 6, 2021 13 hours ago, trurl said: Are you sure you are running a correcting parity check? With that many sync errors, are you sure parity was ever valid, ever built, nothing was done to invalidate it completely such as New Config-Trust Parity when that wasn't appropriate? Post diagnostics, hopefully you haven't rebooted since parity check. I ran a diagnostics immediately after, just in case. Attached. denali-diagnostics-20210805-1610.zip Quote Link to comment
trurl Posted August 6, 2021 Share Posted August 6, 2021 How did you add that parity disk? I don't think you ever built parity on that disk. Syslog seems to show parity being partitioned but no parity build and then later a parity check. Quote Link to comment
AnnHashaway Posted August 6, 2021 Author Share Posted August 6, 2021 I have been using this parity disk for a few years now. I have had a few power outage incidents with some data loss, but was able to use offsite backups to restore the data. I wonder if something happened at that point and I didn't notice. Is there a way to re-initiate it like a new parity drive and have it build the parity from scratch? Everything important is backed up locally and remotely, so I'm not worried about taking a swing. Thanks for you help. Quote Link to comment
trurl Posted August 6, 2021 Share Posted August 6, 2021 New Config, Preserve All will keep all disks just as they are and rebuild parity on any disk assigned to a parity slot. Quote Link to comment
AnnHashaway Posted August 6, 2021 Author Share Posted August 6, 2021 (edited) 2 hours ago, trurl said: New Config, Preserve All will keep all disks just as they are and rebuild parity on any disk assigned to a parity slot. I am almost 1% in the rebuild at the writes to the parity are zero. EDIT: Should I zero out the drive with unassigned devices and try again? Edited August 6, 2021 by AnnHashaway Quote Link to comment
trurl Posted August 7, 2021 Share Posted August 7, 2021 17 hours ago, AnnHashaway said: Should I zero out the drive with unassigned devices and try again? Can't see how that would make any difference at all since parity rebuild is going to overwrite the entire disk regardless of whether it is zeros or whatever. Something not working correctly 14 hours ago, trurl said: Post new diagnostics. Quote Link to comment
AnnHashaway Posted August 8, 2021 Author Share Posted August 8, 2021 23 hours ago, trurl said: Post new diagnostics. Attached denali-diagnostics-20210808-0831.zip Quote Link to comment
trurl Posted August 8, 2021 Share Posted August 8, 2021 Aug 6 15:30:53 Denali kernel: mdcmd (37): check correct Aug 6 15:30:53 Denali kernel: md: recovery thread: recon P ... ... Aug 7 09:35:13 Denali kernel: md: sync done. time=65060sec Aug 7 09:35:13 Denali kernel: md: recovery thread: exit status: 0 Seems to indicate it completed successfully after 18+ hours which is reasonable for 8TB parity. Post a screenshot of Main - Array Operation Quote Link to comment
AnnHashaway Posted August 9, 2021 Author Share Posted August 9, 2021 18 hours ago, trurl said: Aug 6 15:30:53 Denali kernel: mdcmd (37): check correct Aug 6 15:30:53 Denali kernel: md: recovery thread: recon P ... ... Aug 7 09:35:13 Denali kernel: md: sync done. time=65060sec Aug 7 09:35:13 Denali kernel: md: recovery thread: exit status: 0 Seems to indicate it completed successfully after 18+ hours which is reasonable for 8TB parity. Post a screenshot of Main - Array Operation Attached Quote Link to comment
trurl Posted August 9, 2021 Share Posted August 9, 2021 That first screenshot seems to agree parity successfully checked with no sync errors. Maybe something with your webUI not showing correct numbers for I/O on that disk for some reason. I don't know. 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.