September 4, 20241 yr This system has been solid for 3+ years and I do my scheduled parity check every 120 days. Right now is in middle of a scheduled non-corrective parity check and I got many of those errors in the log. I am about 71% done. What should I do next? [1993536.265741] mdcmd (38): check nocorrect [1993536.265813] md: recovery thread: check P Q ... [1993767.284818] mdcmd (39): set md_write_method 1 [1993818.200655] eth0: renamed from vethc9b5ac8 [2011058.905716] md: recovery thread: PQ incorrect, sector=2565285656 [2011058.905763] md: recovery thread: PQ incorrect, sector=2565285664 [2011058.905801] md: recovery thread: PQ incorrect, sector=2565285672 [2011058.905837] md: recovery thread: PQ incorrect, sector=2565285680 [2011058.905873] md: recovery thread: PQ incorrect, sector=2565285688 [2011058.905909] md: recovery thread: PQ incorrect, sector=2565285696 THANKS in advance as always nas-unraid-1-diagnostics-20240903-1903.zip
September 4, 20241 yr Author 4 hours ago, JorgeB said: Any unclean shutdown since the last check? No unclean shutdowns as this unraid is on UPS and it has been up for several months. Last reboot was for the 6.12.11 upgrade. What is interesting is the Notifications -- Warnings reports no errors but in the main dashboard I see 699 errors. Here is the diagnostic after the parity check was completed. Should I reboot and do another parity-check with corrections? I just need to understand what I am dealing with before making it worse nas-unraid-1-diagnostics-20240904-0823.zip
September 4, 20241 yr Community Expert There's a known issue with the notifications, but history will be correct, if there weren't any known unclean shutdowns I would run a correcting check, and then a non correcting one to confirm no more errors, if there are, there's still a problem.
September 4, 20241 yr Author 3 minutes ago, JorgeB said: There's a known issue with the notifications, but history will be correct, if there weren't any known unclean shutdowns I would run a correcting check, and then a non correcting one to confirm no more errors, if there are, there's still a problem. Thanks you Sir. Will do and report back.
September 6, 20241 yr Author I got the same number of errors, 699. How can I tell if they were corrected? Is there a log? Attached find my diagnostic again. I am about to reboot and do another parity check. nas-unraid-1-diagnostics-20240906-0701.zip
September 6, 20241 yr Community Expert 11 minutes ago, DivideBy0 said: How can I tell if they were corrected? Is there a log? It is in the syslog. if you install the Parity Check Tuning plugin then even if you make no use of its facilities the entries for parity check entries in the History will be enhanced to say whether they were correcting or not.
September 6, 20241 yr Author Thanks and indeed it is in the syslog. I wish I knew exactly what was corrected but I guess as long is done right I shouldn't worry Sep 4 14:29:14 NAS-UNRAID-1 kernel: md: recovery thread: PQ corrected, sector=2565288568 Sep 4 14:29:14 NAS-UNRAID-1 kernel: md: recovery thread: PQ corrected, sector=2565288576 Sep 4 14:29:14 NAS-UNRAID-1 kernel: md: recovery thread: PQ corrected, sector=2565288584 Sep 4 14:29:14 NAS-UNRAID-1 kernel: md: recovery thread: stopped logging Edited September 6, 20241 yr by DivideBy0
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.