MrBeast

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

@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??) 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!!

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

Since this morning the flash backup message has just changed to "up-to-date" and I can also download the backup from the dashboard. 👍 rom my side nothing has been modified - so something seems to have been adjusted on the server side?

I have the same issue as well - But will also wait for an update from the admins Thanks in advance!