61 Mill Parity Errors, No Drive Errors

[XanXic]

Sort of title, after my server ran a scheduled parity check it reported back over 61 million errors. This was a non-corrective check, I ran another one to be sure and same report 61+. But the drives themselves are showing zero errors and the parity is reported as valid.

The thing is these are the first parity checks after installing a new drive, I did the 'unraid swap' and replaced a bad 8TB drive with a 12TB one (All drives in the array were 8TB at this point), and added a second 12TB drive. So my parity moved to the new higher TB drive and the other was added to the array. Rebuilt parity over like...two days almost. And then I'm like 90% sure I ran a parity check after just to make sure it was all cool, which it was and has been fine since.

 

So my suspicion, because 61 million is a lot, these errors are related to a 'missing' drive? I'm not sure, I'm nervous to run a corrective check because idk what that'll do. Despite the error's it's still reporting the parity as valid. All drives have clean bills of health from SMART tests, and again show zero errors on them.

 

I tried searching around but couldn't find a similar issue and I can't find a way to actually read the parity report.

[JorgeB]

7 minutes ago, XanXic said:

I did the 'unraid swap'

Do you mean a parity swap? It's a known issue, sometimes the extra space of the new parity is not correctly zeroed.

[XanXic]

19 minutes ago, JorgeB said:

Do you mean a parity swap? It's a known issue, sometimes the extra space of the new parity is not correctly zeroed.

Yeah, that was the exact procedure I followed.

Is there something I should do or should I just expect the errors from now on?

Edited July 2, 2022 by XanXic

[JonathanM]

39 minutes ago, XanXic said:

Is there something I should do

 

50 minutes ago, XanXic said:

run a corrective check

Which should find and correct all the errors, then run a non-correcting check.

[XanXic]

Alright will do, I just wanted one other person to say it's okay before I went for it lol. I will know in...21 hours... lol

[XanXic]

So I ran a corrective parity check, 58 million errors. Then ran another check to see if it solved them and it's still 58 million errors. Parity is still valid but that didn't seem to fix the errors it's seeing.

Edited July 6, 2022 by XanXic

[JorgeB]

Are you sure they were both correct? If you didn't reboot yet post the diags.

[XanXic]

Yeah they were both corrective, I was going to post the diags but it had restarted since then. I have it setup to restart once a week in the dead of night. So I ran ANOTHER check lol and this time it found none. So I'd have to guess the corrective check plus a restart fixed the issue.