Unraid 6.90-beta33 or beta35 Parity-Check bug？

Then during the shutdown, the system forced a processes that was tying up the system to close.

See this post for the various shutdown timeouts that need to be synchronized: 

 

16 hours ago, ljm42 said:

See this post for the various shutdown timeouts that need to be synchronized: 

 

I have very few docker and vms, which are openwrt, plex and dsm. I need to shut them down before shutting down or restarting unraid, otherwise the waiting time will be long. So I think it is a system bug.

These are configurable settings. If the defaults don't work for you, then you need to set them up for your particular system:

 

• "Settings->VM Manager->VM Shutdown time-out": must be long enough to allow your VMs to shutdown
• "Settings->Disk Settings->Shutdown time-out": must be long enough for the array to stop *after* VMs have shutdown. So 60 to 120 seconds longer than the VM timeout.

 

If a parity check starts after shutting down, then you Disk Settings->Shutdown time-out setting is too short for your particular system.

 

If you would like more of an explanation, see this post (which is embedded in the post I linked to above):

 

12 hours ago, ljm42 said:

These are configurable settings. If the defaults don't work for you, then you need to set them up for your particular system:

 

• "Settings->VM Manager->VM Shutdown time-out": must be long enough to allow your VMs to shutdown
• "Settings->Disk Settings->Shutdown time-out": must be long enough for the array to stop *after* VMs have shutdown. So 60 to 120 seconds longer than the VM timeout.

 

If a parity check starts after shutting down, then you Disk Settings->Shutdown time-out setting is too short for your particular system.

 

If you would like more of an explanation, see this post (which is embedded in the post I linked to above):

 

thank you. I will try.