A few days ago I had to run a parity check due to an unclean shutdown. During this time unraid became unresponsive and I had to hard reset the box and restart the check from scratch. Subsequently it ran for a while pausing itself (drive temp warnings I may have set too conservatively) and resuming itself when they cooled down normally. It was not paused when at 3am my normal mover process ran and that paused the check for mover, from which it never auto resumed like it always does.

When I woke up I noticed and manually resumed, only for it to repause after a handful of minutes for no stated reason. Now every time I manually resume it, it will run for 0.2% - 0.3% which takes a few minutes before pausing itself again. It isn't pausing for temperature reasons as I've been watching it now and they aren't close anymore (turned ac on). There is no reason given in the notification it sends for the pause as is the case when it's due to temperature or mover, etc.

As of now I've got to watch it and hit resume every 5ish minutes (or 0.3%) and it's only at 34% so this is going to be an issue to get all the way to 100%. I'm not sure why this is happening or if there's a better way to deal with it than watching and resuming every few minutes. If anyone has ideas on why or suggestions for a different way to finish that doesn't involve that tedious, lengthy process I would greatly appreciate it.

Edited September 29, 2025Sep 29 by parabola90
readability

Remove the parity check plugin and retest, it may be settings related to that.

Rather than remove the parity check plugin you can simply set it to not pause parity checks.