Parity Sync errors again?

[MrYoshii]

Hi, I got monthly Parity Syncs going and last time I was seeing the error.
I did ignore it because I was not sure if I got an unsafe shutdown.
But now there are two errors again. Maybe someone knows what's up with that?

 

homeserver01-diagnostics-20230602-2358.zip

[JorgeB]

Last check was non correct, so assuming the previous was the same it's normal it would find the same errors, run a correcting check.

[MrYoshii]

3 hours ago, JorgeB said:

run a correcting check.

oh damn I missed that setting in the scheduling tap.
I'm now doing the correcting check and I will keep you posted.

[itimpi]

3 hours ago, MrYoshii said:

oh damn I missed that setting in the scheduling tap

You WANT the regularly scheduled check to be non-correcting so that hardware issues do not inadvertently corrupt parity.   When you expect to have parity errors and you think the hardware is fine, that is when you run a correcting check manually to clear the errors.

[MrYoshii]

On 6/3/2023 at 5:13 PM, itimpi said:

You WANT the regularly scheduled check to be non-correcting so that hardware issues do not inadvertently corrupt parity.   When you expect to have parity errors and you think the hardware is fine, that is when you run a correcting check manually to clear the errors.

ah ok thanks.
 

[MrYoshii]

Ok so I did a rerun and I got this?
On the notification it says 2 errors and in the main tap it says 0 errors?

It also shows different Durations and speed?

Also this is the Notification on telegram:
HomeServer01: Notice [HOMESERVER01] - Parity-Check finished (2 errors)
Unraid Parity-Check
Notice [HOMESERVER01] - Parity-Check finished (2 errors)
Duration: 21 hours, 6 minutes, 42 seconds. Average speed: 105.3 MB/s

 

homeserver01-diagnostics-20230608-1529.zip

Edited June 8, 2023 by MrYoshii

[JorgeB]

Syslog confirms no sync errors were found, notifications are known to sometimes show the wrong data, not clear yet the cause, but you're fine.

[MrYoshii]

ok thanks

[MrYoshii]

I don't know why, but yesterday it did an auto check and showed again two sync errors.
Now I'm running a correction sync.

Should I be worried?

Edited August 3, 2023 by MrYoshii

[JorgeB]

50 minutes ago, MrYoshii said:

Should I be worried?

If there's no apparent reason, like an unclean shutdown, you should.

[itimpi]

53 minutes ago, MrYoshii said:

Now I'm running a correction sync.

Just worth pointing out that you would expect the error count for a correcting sync to be the same as the previous non-correcting one as Unraid does not distinguish between errors detected and those corrected.

[MrYoshii]

On 8/3/2023 at 12:01 PM, JorgeB said:

If there's no apparent reason, like an unclean shutdown, you should.

ok there were no unclean shutdowns. What could cause this issues?

 

On 8/3/2023 at 12:04 PM, itimpi said:

Just worth pointing out that you would expect the error count for a correcting sync to be the same as the previous non-correcting one as Unraid does not distinguish between errors detected and those corrected.

yes, but I got the errors the last time when I started this thread, and they were gone after I used a correcting check and now they are back again.

[JorgeB]

14 hours ago, MrYoshii said:

What could cause this issues?

RAM is the most common culprit, a disk or a controllers could also cause this.

[MrYoshii]

22 hours ago, JorgeB said:

RAM is the most common culprit, a disk or a controllers could also cause this.

okok if switched platform now i got ecc RAM.
After the correcting check, i did a another normal check. it finished without an error.

Hopefully it doesn't come back with the next check.