Maintenance Mode Boot / Start

Currently, when array / container / VM autostarts are enabled, booting the server will of course start all these services.

If we are rebooting to do maintenance (ie. add or remove hardware, etc.) we might not want the array to start so we can adjust settings that need the array stopped. At present, this means remembering to disable array autostart before shutting down. Forgetting means waiting for the array to start just to stop it again (can be quite long, depending on filesystem and how many disks you have). Additionally, one could forget to turn array autostart back on, and then an unexpected reboot never brings the server back up.

Other maintenance tasks involving disk configuration might require starting the array, but we don't want containers or VMs to start. Similarly, we must disable the Docker and VM engines before starting the array, or wait for them all to start just to stop them again.

We may also need to edit container or VM settings and want to do that before they start (perhaps we've changed disk configuration and need to change path mappings). Array must be started and Docker engine must be enabled to edit containers, but they will autostart when we do that and we can't stop it.

Proposed Solution

A checkbox next to the reboot/shutdown buttons (like the "Reboot in Safe Mode" one) that will disable array autostart for the next boot only.

When array autostarts, continue to autostart containers and VMs, but when the array is manually started offer a dialog asking if containers, VMs, both, or neither should start with it. Once we've completed our task(s), a button like "Start All" for containers/VMs that respects if they are set to autostart could be clicked. (Perhaps we could just always have such a button?)

This could save users a lot of time over the course of an Unraid machine's lifetime.