riff.79 Posted August 13, 2020 Share Posted August 13, 2020 Hi team! I am having an issue that I can put my finger on. I have am seeings about 2562 errors during a parity check. The error I am seeing is: Tower kernel: md: recovery thread: P corrected, sector=xxxx I have taken a look at the logs but I'm not sure where to look - I don't see any obvious disk errors. It always happens in the middle of a parity check. I have checked the cables too. All firmly in place. Any help would be greatly appreciated. tower-diagnostics-20200813-1440.zip Quote Link to comment
JorgeB Posted August 13, 2020 Share Posted August 13, 2020 Any unclean shutdown before this check? If not run another check and post new diags if more errors. Quote Link to comment
riff.79 Posted August 13, 2020 Author Share Posted August 13, 2020 (edited) 49 minutes ago, johnnie.black said: Any unclean shutdown before this check? If not run another check and post new diags if more errors. No, that's the strange bit. Ill run a few more and see how it goes. The parity check I ran before this one found the exact same number of errors. Edited August 13, 2020 by riff.79 Quote Link to comment
JorgeB Posted August 13, 2020 Share Posted August 13, 2020 37 minutes ago, riff.79 said: The parity check I ran before this one found the exact same number of errors. I assume that was a non correcting check? Quote Link to comment
riff.79 Posted August 13, 2020 Author Share Posted August 13, 2020 9 minutes ago, johnnie.black said: I assume that was a non correcting check? Nope was a correcting check. This is my backup unit btw, primary data is on another Unraid. Quote Link to comment
JorgeB Posted August 13, 2020 Share Posted August 13, 2020 Not a good sign, still run another one so we can compare the affected blocks. Quote Link to comment
riff.79 Posted August 13, 2020 Author Share Posted August 13, 2020 (edited) 11 minutes ago, johnnie.black said: Not a good sign, still run another one so we can compare the affected blocks. Will do! Thanks for your help so far. First issue since 2012 with parity, not a bad run! This machine is about 2 years old. Edited August 13, 2020 by riff.79 Quote Link to comment
riff.79 Posted August 14, 2020 Author Share Posted August 14, 2020 17 hours ago, johnnie.black said: Not a good sign, still run another one so we can compare the affected blocks. No errors this time. Ill run a third just to be sure. Hope I have not wasted your time. 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.