Hello,

 

I ran into this weird situation where notifications say that my parity check came out clean yet the parity history says I had 1 error.

Notifications:

Parity history:

 

I wonder what should I believe... Notification seems to be reporting last parity check instead of the current one (speed and time difference)?

 

I run non correcting parity checks monthly. Had no issues for ~1 year. But now since 1 error came up I wonder how should I correctly handle it or identify which drive it came from? There are no smart errors logged from any of my drives...

 

Or should I just run a correcting parity check and forget about it?

 

Edited October 1, 20232 yr by Laov

7 minutes ago, Laov said:

I wonder what should I believe...

Check the main GUI page, next to the parity check button, that will be correct, the notifications sometimes give old results, looks like a bug but unable to reproduce to far.

1 minute ago, JorgeB said:

Check the main GUI page, next to the parity check button, that will be correct, the notifications sometimes give old results, looks like a bug but unable to reproduce to far.

Yes. I checked. It says I have 1 error.

 

What should my next steps be as it was a non correcting parity check that found it? I'd like to identify the cause. Attached diagnostics.

dataserver-diagnostics-20231001-1517.zip

First step is to run a correcting check, you can then run another one to confirm all is well.

4 hours ago, JorgeB said:

First step is to run a correcting check, you can then run another one to confirm all is well.

 

I ran a correcting check but it came back with 0 errors...

 

Notification also consistently shows the previous parity checks result

 

I really have to wonder where this 1 error came from...

9 minutes ago, Laov said:

I ran a correcting check but it came back with 0 errors...

That would suggest to me a possible RAM bit flip during the previous run, keep monitoring next runs.