Hi all,

after my bi-monthly scheduled (correcting) parity check finished two days ago, i just noticed that it has found 2 errors during the check.
As the scheduled check is a correcting one, I started a second, non-correcting, parity check . Unfortunately with the same result...again two errors. 😥

Furthermore I noticed that the displayed party size in the "Parity Operation History" is quite strange: 52,7 MB...

 

Does anyone have an idea what the problem could be or a suggestion on how to proceed?
I have also attached the diagnostics with the two parity checks included.
 

Thanks in advance for any help!

ironman-diagnostics-20230202-2040.zip

The strange size being displayed when you call up the history will almost certainly be because you have the Parity Check Tuning plugin installed.   There was a change in the 6.11.x series to the format of the history file and the way showing history is invoked and this is not being accounted for.   I am in the final stages of testing an update to the plugin that will correctly handle this (and also show the extended history information the plugin records).   When the update is available (hopefully in the next few days) and installed then that field will have the expected value (even for the existing entries). 

@itimpi Thanks for the quick response and for pointing out the reason for the strange parity size! I will check, once the new plugin version has been released, if the issues goes away. 👍

I just checked the syslog again and noticed that the scheduled parity check was executed as "non-correcting" checks, although it was set in the settings to be executed as "corrected"... (Possibly a bug??)


 

Quote

Jan 29 23:59:21 IronMan kernel: md: recovery thread: P incorrect, sector=2743151176
Jan 29 23:59:21 IronMan kernel: md: recovery thread: P incorrect, sector=2743151208
Jan 30 12:34:12 IronMan Parity Check Tuning:  Non-Correcting Parity Check finished (2 errors)
Jan 30 12:34:12 IronMan Parity Check Tuning: Elapsed Time 14 hr, 17 min, 24 sec, Runtime 14 hr, 17 min, 24 sec, Increments 1, Average Speed 155.5MB/s

 

[...]

 

Jan 31 15:55:34 IronMan kernel: md: recovery thread: P incorrect, sector=2743151176
Jan 31 15:55:34 IronMan kernel: md: recovery thread: P incorrect, sector=2743151208
Feb  1 04:18:13 IronMan Parity Check Tuning:  Non-Correcting Parity Check finished (2 errors)
Feb  1 04:18:13 IronMan Parity Check Tuning: Elapsed Time 14 hr, 17 min, 29 sec, Runtime 14 hr, 17 min, 29 sec, Increments 1, Average Speed 155.5MB/s

Then it makes sense why the second check still shows the errors. 😅

I will perfom again a "correcting" parity check and than a "non-correcting" one to see if the errors goes away... I will give an update once finished.

Thanks again!!
 

After i performed again a correcting and then a non-correcting check, no more problems appeared with the parity check...all good!!