Hello, new unraid user here on a 6.11.5 trial, running 3 x 18tb drives, one of which is a parity drive, plus one 1tb M.2 cache drive. Relatively tech savvy, but not IT professional / sysadmin levels of experience. I'm having trouble with my brand new unraid install restarting my parity check after every shutdown or restart, presumably due to an unclean shutdown. It also doesn't manually start my array, even though I have it set to do so.
I've found the following advice here and tried it all, to no avail:
Changed my shutdown timer from 90 to 420 seconds.
Disabled all docker plugins and uninstalled all apps (except Community and Tips and Tweaks).
Manually stopped my array and cancelled the parity check before restarting. I'm not running any VMs, this is just a data storage and Plex server.
Plugged the USB stick into a USB 2 port, instead of a USB 3 port.
I already have ssh,bash in the "Processes to kill before Array is Stopped" field in Tips and Tweaks plugin - it seems to be there by default now.
Other notes:
One comment said to manually stop your array, time how long it takes, then set a shutdown timer based on that with a buffer for safety. I timed my array stop time at around 25 seconds, so 420 seconds should presumably be plenty of buffer for this.
Based again on me manually timing itself, Shutdown / restart itself appears to take less than 420 seconds (~240 seconds for the login screen to show up again), so it doesn't appear to be the shutdown timer that's causing the problem.
The pinned topic on unclean shutdowns says "If an unclean shutdown does occur because the overall "Shutdown time-out" was exceeded, Unraid will attempt to write diagnostics to the /log/ folder on the flash drive. When you ask for help with an unclean shutdown, post the /log/diagnostics.zip file.". I've checked this folder and I can't find an auto generated log, although I can see a couple of manual logs I exported.
tma-1-diagnostics-20221211-1149.zip
tma-1-diagnostics-20221211-1212.zip