September 29, 20241 yr I had a hard lock a couple of days ago. Had to restart with the power button. Minor changes of the array can happen at night from Sonarr, otherwise everything stays on the cache. It came back up and it started a parity check. I cancelled it as the end of the month is near and I decided it was time to address my macvlan problems as reported by Fix Common Problems and upgrade at the same time. I think I was 6.12.8, now 6.12.13. 1 day later, power outage! I believe anyways as my desktop was restarted with no apps loaded. Unraid seemed okay since that hard lock, but of course it started another parity check with I guess automatic correction. How does one tell this? Noticed all of these P corrected errors in the logs by fluke. There are no notifications for these?!? Seems kind of important if you're running a correcting check, at least on the first one. I have this line in the Main tab parity area: "Sync errors corrected: 6000". Does the wording change based on the checked flag? Seems like there should be an easier way to know if you're correcting parity or not. Just found it is indicated in syslog if you know what to look for. Unraid has decided to stop logging these corrections all together. They ones reported appear to be sequential, but now I'm unsure if it's stopped reporting all corrections to save the logs or if it's smart enough to report the next non sequential error. In otherwords I can't assess how much damage is done, if any. Is there a drive issue or just power dropping before parity calculations. Since the parity check is now paused and the lack of log report, I can't tell if the corrections are ongoing or not. I have over 6000 corrections so far. Sounds terrible, but if it's 6000*512 byte sector size, then I guess that could be a single file mover was moving at the time? Due to the power outage the next day, my log is slim. I only see an error about some slow ata8. Which seems to be /sdi from poking around the logs. But not sure what to make of that. I guess I can assume this was a one off related to the hang and not a drive issue? And the correct course of action is to resume the check, and see if the monthly check in 1 day finds 0 errors? Thanks tera-diagnostics-20240929-1428.zip Edited September 29, 20241 yr by thespooler Add diags
September 30, 20241 yr Solution Some sync errors are expected after an unclean shutdown, just let the parity check finish.
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.