I'm trying to add a drive, and stopped the array. It is a T440, which supports hot swap, but I understand the array has to stop to add/remove.

After 15 minutes the status at the bottom of the browser is still: Array Stopping - retry unmounting user shares.

However the dashboard says everything is stopped.

Array Stopped, Cache Stopped, Unassigned Stopped.

I've refreshed the Unraid browser and the note at the bottom status bar persists: Array Stopping - retry unmounting user shares.

Now 30 minutes in, and I don't have the option to just restart the array and try again another day. The Start button is gone. Array operation says "Stopping"

What is the proper way to handle this situation? Wait indefinitely? Shut Down? How can I debug?

Edit 15 minutes later: Yikes - I can't even restart Unraid cleanly -

Reboot - T440 Array Stopping Retry unmounting user share(s)... System is going down... 934

Edited October 4, 2025Oct 4 by timg11

That means there's some file(s) open, preventing the array from, stopping.

I had to use IDRAC to power down the server to recover. Now it is doing the 2-day parity check.

For future reference how can I discover open files and try to close them at the source, or if not possible, forcibly close them?

This is a NAS after all, and multiple computers are accessing files on the array.

I found the App Open Files v2. That might help on identifying.

The steps for stopping the array would be:

1) Stop VMs

2) Stop Docker containers

3) Check Open Files v2 to see if any other files are open and close them at their source

4) Stop Array

If 3) shows "phantom" files that appear to be open but have no real client, is there a way to force close them from an SSH terminal so the Stop Array will not hang?

Disable Docker and VM service and reboot in safe mode, start the array and see if it stops, if yes, retest again after booting in normal mode to rule out a plugin issue, leave the services still disabled, if still OK enable one of the services and retest, then the other, note that if the issue happens with the docker service enabled only, you may need to try enabling one or a few containers at a time to find the culprit.