LOF_HWalker Posted May 31 Share Posted May 31 We are running Unraid 6.12.9. Every time a parity check is run, it has a high error count (anywhere from 20-100+). The parity checks are set to correct errors, so I think these are new errors every time. None of our drives are showing any errors. How can I narrow down the source of these errors? I've also attached the diagnostics file. Thanks all! lof1-nas-diagnostics-20240531-0808.zip Quote Link to comment
Solution JorgeB Posted May 31 Solution Share Posted May 31 Start by running memtest. Quote Link to comment
itimpi Posted May 31 Share Posted May 31 2 hours ago, LOF_HWalker said: The parity checks are set to correct errors, so I think these are new errors every time. Are these manual or scheduled checks? There is a bug where scheduled ones always run as none-correcting regardless of what you specify. having said that we always recommend that scheduled checks ARE set to be non-correcting so that you do not get hardware playing up and corrupting parity before you realise anything has gone wrong. Then only run correcting checks manually when you are reasonably certain you have no hardware problem. BTW: if you have the Parity Check Tuning plugin installed, even if you use none of its features you will find that for any new checks the history entries will be enhanced to tell you both how the check was started and whether it was actually correcting or not. Quote Link to comment
LOF_HWalker Posted May 31 Author Share Posted May 31 1 hour ago, JorgeB said: Start by running memtest. Embarrassed that I didn't think of this, it failed so I'll get some new RAM in there ASAP. 51 minutes ago, itimpi said: Are these manual or scheduled checks? There is a bug where scheduled ones always run as none-correcting regardless of what you specify. having said that we always recommend that scheduled checks ARE set to be non-correcting so that you do not get hardware playing up and corrupting parity before you realise anything has gone wrong. Then only run correcting checks manually when you are reasonably certain you have no hardware problem. BTW: if you have the Parity Check Tuning plugin installed, even if you use none of its features you will find that for any new checks the history entries will be enhanced to tell you both how the check was started and whether it was actually correcting or not. They are scheduled, but I was wrong, I did already have them set to non-correcting so I will leave them that way. Thanks for the help! 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.