My monthly parity check resulted in (3) errors. Guessing I had an unclean shutdown. My assumption is to rerun parity with "write corrections" checked, but wanted to check since I have not seen this in previous checks and it takes nearly 3 days

Also, I feel like monthly parity checks may be too frequent and plan to change unless there is a good reason not to.

Thanks

media-server-diagnostics-20260604-0728.zip

5 minutes ago, wdpaynter said:

Also, I feel like monthly parity checks may be too frequent and plan to change unless there is a good reason not to.

Monthly is what most people go for, although others do go for longer periods.

If you keep it monthly then it is probably worth using the Parity Check Tuning plugin to ensure it only runs when it tends to be idle.

Thanks. I do use the plugin and have it stop while mover is running (or perhaps that is default). The parity check doesn't seem to interrupt or affect server usage during the 2-3 days it runs.

Should I re-run parity check with corrections checked? I don't beleive my drives are an issue.

Edited June 4Jun 4 by wdpaynter

15 minutes ago, wdpaynter said:

Should I re-run parity check with corrections checked? I don't beleive my drives are an issue.

That would be the normal corrective action if you are reasonably confident there is no hardware error that needs fixing first.

Do you have any idea why you got the errors in the first place? Perhaps an unexpected shutdown?

Just now, itimpi said:

That would be the normal corrective action if you are reasonably confident there is no hardware error that needs fixing first.

Do you have any idea why you got the errors in the first place? Perhaps an unexpected shutdown?

I beleive it was shutdown related. I cannot remember if these same errors were present last month(s). Is there anyway to identify alternative issues in the log? I can comb through it, but am inexperienced in this regard

Can be quite hard to find anything in the logs unless you know exactly when it happened. There is also the fact that the standard syslog is only held in RAM so resets on a reboot. You need the syslog server installed to get syslog that survive a reboot.

1 hour ago, itimpi said:

Can be quite hard to find anything in the logs unless you know exactly when it happened. There is also the fact that the standard syslog is only held in RAM so resets on a reboot. You need the syslog server installed to get syslog that survive a reboot.

My server hasn't been rebooted in 13 days. I have syslog installed and the log is attached. For some reason it hasn't logged anything in a few hours. I'll likely just run a corrections parity check if nobody thinks anything else is advisable. Thx

syslog-192.168.68.57.log syslog-192.168.68.57.log.1

I would run a correcting check, but if after that you get new errors without an apparent reason, it should be investigated