DigitalMaestro

Thank you for the clarification. I understand the issue better now. DM

I recently experienced an issue where Unraid would hang when executing a shutdown because the Unassigned Devices plugin could not unmount a remote SMB mount where the target server was offline. Many thanks to @dlandon for identifying and fixing the issue quickly. However, this brought up a larger question in my mind. Should a plugin (or VM or Docker container or any other process) be allowed to cause a potential hang on shutdown? I did see a "forcing shutdown" message in the syslog during the hang but the shutdown still never completed. To this end I'd like to request that a feature be added to the shutdown script such that, after some reasonable (perhaps user defined) period of time, the script forces the shutdown no matter what (even if potential data corruption could be the result). This could be presented as an option in Disk Settings (or whichever settings section is appropriate) so that users could choose not to activate this feature. For those interested, here's an example of how this affected me in a real scenario. I was away from home when a power loss occurred. Normally, the UPS would trigger a shutdown and then Unraid would turn off the UPS once the shutdown was completed. However in this case the shutdown experienced the hang and never sent the turn off command to the UPS. Power was restored before the UPS was exhausted and so the UPS never cycled power (it always cycles power if it gets the turn off command even if power is restored). Thus my Unraid server remained offline until I was able to return home meaning that all the hosted services I run were also offline. Thanks DM

Thank you! Much appreciated. DM

Hi, Were you able to get any further insight into the issue with Unraid hanging on shutdown from the diagnostics I posted? Thanks DM

I physically unmounted and removed all UD mounted disks (including the ZFS disk) and mounted the remote SMB that points to the VM. I then started the shutdown of the array and it never completes. I have attached the diagnostics I captured while it was stuck (started at 21:37:51 and it is still hung at 21:55:00, diagnostics captured at 21:47). It does appear that UD is having trouble with the SMB mount from my read of the syslog but I'll defer to your expertise to determine the true root cause. Thanks DM diagnostics-20250209-2147.zip

I actually use that disk to do weekly backups of my ZFS cache drive pool where I host my VMs. I mount it with UD and use a syncoid script to do the backup. I then remove it and store it offline (but sometimes it happens to stay mounted for a couple of days until I remember to remove it) So are you indicating that the SMB issue is a red herring and the real issue is UD failing to unmount the drive? It does unmount when I do it manually. I swear that I have the same hanging shutdown issue whether the ZFS drive is mounted or not. However I will run a test where only the SMB is mounted and the ZFS drive is not present and report back. DM

Apologies, should have done that. Attached. Note that the SMB mount is currently not mounted. Let me know if you need the diagnostics with the SMB mounted. Thanks DMdiagnostics-20250208-2037.zip

I am experiencing an issue where the Unassigned Devices plugin appears to be preventing a clean array stop (the array stop operation never completes) I have a VM that exposes an SMB share. I use UD to mount this share. The share is subsequently used by one of my Docker containers. When I stop the array, the VMs and Dockers shutdown normally. The next action seems to be the UD plugin unmounting all mounted disks and shares. When UD tries to unmount the remote SMB share, it gets an error because the VM exposing the share is already shutdown. I see a timeout error to that effect in the syslog. The next entry in the syslog appears to be a reconnection attempt to the VM's SMB share. After that, there are no other entries in the syslog. It appears that this SMB error either causes UD to hang waiting on the reconnection attempt or the UD shutdown script somehow does not return the correct response to the Unraid master shutdown script. Either way, the shutdown process is halted at this point and requires a hard reboot. Has anyone seen this behaviour? If so, any pointers on how to correct it? Thanks DM

Thank you for all the feedback and help. I think removing those lines may have done the trick! Now the "Starting go script" is immediately followed by "Starting emhttpd" Also the web GUI is now active much faster. I was accustomed to waiting 30 seconds to a minute after the login prompt appeared on the monitor after bootup before I could load the web GUI in the browser from another computer. Now the browser can navigate to the web GUI almost immediately after the login prompt appears. System auto started as expected. Since the failure was intermittent, I'll need to see a few shutdown cycles before I am 100% certain that the problem is resolved but I'm pretty sure it is. Thanks once again! DM

My old system had Marvell controllers. New system does not. I simply built the new system then moved the disks and flash drive over. Was there something I needed to do the clean up the go file? Any other file cleanup required? Thanks DM

Yes, the BIOS is configured to automatically (re)start the computer when power is applied. DM

I do have auto-start enabled in Disk Settings. Scenario: I am testing the UPS shutdown settings. Unraid successfully initiates shutdown once the UPS hits the defined runtime. When I plug the UPS back into the mains, the computer restarts. Unraid loads successfully but does not start the array (array status is 'Array Stopped'). However the array configuration is shown as valid in the "Main" section. Interestingly, if I then click the Reboot button, Unraid reboots and subsequently auto-starts the array as expected. Is there an additional configuration step needed to enable auto-start after UPS shutdown? Diags attached (created after first reboot from UPS shutdown when array did not auto-start). Any insight appreciated. Edit: I went ahead and tested three scenarios after this auto-start failure to see if I could glean anymore insight Reboot - Unraid auto starts properly Shudown - After manually powering up the computer Unraid auto starts properly UPS shutdown - In this case Unraid did auto start correctly. So it appears that the issue may not be UPS related after all. The core question is thus: Why would Unraid intermittently not auto start even though it reports the array configuration as valid? Thanks DM diagnostics-20220415-1431.zip