Parity Check - 1.2 Billion Errors vs 0 Errors

[danimal86]

I run a quarterly parity check.  I had it set to only do the parity check for a chunk of about 6 hours at a time, but decided i'd rather just get it over with in a little over a day (i resumed the parity check manually and changed the setting mid way through the check, but at idle)

I noticed that errors were stacking up like crazy as the check was going:

 

But then i look at my notifications and it says 0 errrors

Even my email confirmation said 0 errors. 

 

Are all the errors because of the incremental parity check?   Should i start another (non-incrimental) pairty check?

Attached diagnostics. 

tower-diagnostics-20230509-0641.zip

[JorgeB]

There is a known issue with the notifications sometimes, but the log shows sync errors, so run a correcting check.

[danimal86]

18 minutes ago, JorgeB said:

There is a known issue with the notifications sometimes, but the log shows sync errors, so run a correcting check.

How many errors?

I normally have it so that it doesn't write corrections (at least on scheduled parity checks). 

 

Just use this one?

[JorgeB]

34 minutes ago, danimal86 said:

How many errors?

It stops logging after a few.

 

34 minutes ago, danimal86 said:

Just use this one?

Yes.

[danimal86]

17 minutes ago, JorgeB said:

It stops logging after a few.

 

Yes.

running now.  Lots of sync errors corrected and climbing.  Something to be concerned with?

[JorgeB]

Obviously those are not normal, did you do any recent array changes, like new config or similar?

[danimal86]

51 minutes ago, JorgeB said:

Obviously those are not normal, did you do any recent array changes, like new config or similar?

The only thing i can think of that i can think of was a hardware change.  I was messing around with a Google Coral M.2 and had to remove and reinstall my LSI HBA card to get to the m.2 slot, but i ended up removing it. 

No software changes that i can think of.  Messed around with a couple different dockers (frigate/xteve/firefox/recyclarr), but nothing that i can think of that would need a New Config. 

Edited May 9, 2023 by danimal86

[danimal86]

@JorgeB

2nd Parity check finished, had 1.3Billion errors.  

 

I've attached an updated diagnostics.  Any idea what would cause this?  Everything on the system seems to be working like normal.  

tower-diagnostics-20230511-0637.zip

Edited May 11, 2023 by danimal86

[JorgeB]

Run another check to confirm all is well.

[danimal86]

5 hours ago, JorgeB said:

Run another check to confirm all is well.

Got the 3rd one running

[danimal86]

@JorgeB

Finished the 3rd parity check and all the errors appear to have been corrected.  

 

I attached an updated diagnostic.  

 

What could have caused 1.3B correctable errors?  

tower-diagnostics-20230513.zip

[JorgeB]

This suggests the issue if fixed now, but no idea how so many errors could exist without any major array changes, just keep checking next scheduled checks don't find more errors.

[danimal86]

4 hours ago, JorgeB said:

This suggests the issue if fixed now, but no idea how so many errors could exist without any major array changes, just keep checking next scheduled checks don't find more errors.

Everything seems to be working just fine....no missing drives or any warning notifications.  My only thing is that every once in a while, i'll see a movie or half a show missing and think "i could have sworn i had this".  Now, take that with a grain of salt...could totally have been something that i didn't have or stopped monitoring mid way through a show.  

 

I've been on the quarterly parity check maybe i should go back to monthly?

[JorgeB]

28 minutes ago, danimal86 said:

i should go back to monthly?

At least for now I think it would be better.