Sorry if this problem already solved somewhere. I used search button FYI.

So why - Automatic Correcting Parity-Check - is starting automatically and randomly?

In attachments: history, and settings for scheduler. I tried two Ai bots. Perplexity helped somehow, bcs gave good info, but my option was already off/no.

It said, change "Write corrections to parity" to "no".

tower-diagnostics-20250911-1552.zip

Edited September 11, 2025Sep 11 by lakimakromedia
Upload diagnostic zip

1. Parity Check Tuning plugin is likely the culprit, you can try removing that plugin.

2. Parity checks happen when there is an unclean shutdown. Have you had any issues with shutting down or sudden restarts?
   

   Also please attach your diagnostics.zip

Edited September 11, 2025Sep 11 by MowMdown

I was restarting server due to this parity check.. Usually it happened when I was not home, and wife said every time that plex is not working already few days, I was checking and yes, it was not avaliable via tailscale. During my presence after reset I saw this parity check. We can see in history, that process takes around 18 hours. I had this similar problem on 6.9, after update to 7.x this happened.

9 hours ago, MowMdown said:

Parity Check Tuning plugin is likely the culprit, you can try removing that plugin.

This is unlikely as the plugin does not start the Automatic checks - that is being done by Unraid itself. The plugin is never responsible for initiating checks - just for providing the possibility of running them in increments.

9 hours ago, lakimakromedia said:

I was restarting server due to this parity check.. Usually it happened when I was not home, and wife said every time that plex is not working already few days, I was checking and yes, it was not avaliable via tailscale. During my presence after reset I saw this parity check. We can see in history, that process takes around 18 hours. I had this similar problem on 6.9, after update to 7.x this happened.

Are the parity checks happening after a reboot? Are they just randomly happening?

If these are happening after you are rebooting your server it's not shutting down cleanly and something is preventing a proper shutdown.

If they're just randomly happening your server may be rebooting itself which is indicative of faulty hardware. Next time it happens and it wasn't after you manually cause a reboot, check the server uptime in the upper right corner of the webgui.

You need to enable the remote syslog server and also please post your diagnostics zip (still need this)

Edited September 11, 2025Sep 11 by MowMdown

37 minutes ago, MowMdown said:

Are the parity checks happening after a reboot? Are they just randomly happening?

If these are happening after you are rebooting your server it's not shutting down cleanly and something is preventing a proper shutdown.

If they're just randomly happening your server may be rebooting itself which is indicative of faulty hardware. Next time it happens and it wasn't after you manually cause a reboot, check the server uptime in the upper right corner of the webgui.

You need to enable the remote syslog server and also please post your diagnostics zip (still need this)

I was rebooting/hard reseting due to automatic parity checks were freezing server ror long time, like days, not hours (web ui not avaliable, no access to any docker, server was like offline, physically pc was working) . After this parity was not present, until it shows up in next random day (around month like in history).

Here is prev syslog, before last automatic parity check which was succefull I think. (wife didn't infermed me abauot any problems).

tower-syslog-previous-20250911-1356.zip

tower-syslog-20250911-1359.zip

Edited September 11, 2025Sep 11 by lakimakromedia
Present syslog uploaded