I am a bit of a newbie so please be patient. I have read many threads about this issue but have not found a solution. I set up my Unraid server the first time late last year and I have never managed to cleanly shut this down, the issue has been the same from the start.

I have tried killing all processes, no ssh or terminal is open when trying to shut down etc. My diagnostics file is attached, if someone is willing to have a look. let me know what next diagnostics steps I should do, this is all still new to me and I will probably only learn by guidance.

Thanks

koti-diagnostics-20260427-1609.zip

Reboot and post new diagnostics with the array started in normal (not maintenance) mode.

You can alos 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.

8 minutes ago, trurl said:

Reboot and post new diagnostics with the array started in normal (not maintenance) mode.

Here is my diagnostics file from after reboot

koti-diagnostics-20260427-1631.zip

Unrelated, but you have a share configured to be on cache pool only, another configured to be on plex pool only. But they have files on the array or other pool. And another share not configured to use cache, but has files on cache. Mover won't move these because there is no Mover action, because there is no Secondary.

d-------s                         shareUseCache="only"    # Share exists on cache, disk1
m---a                             shareUseCache="no"      # Share exists on disk1, disk2, disk3, cache
p-------e                         shareUseCache="only"    # Share exists on plex, disk1, cache

You should remove this deprecated plugin

compose.manager.plg - 2025.11.01  (Deprecated)  (Up to date)

14 minutes ago, JorgeB said:

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

Also, what about your user scripts?

2 hours ago, JorgeB said:

You can alos 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.

Thanks for the tip. I will try this as the next step, sounds like it will take quite a long time. What do you mean by "start the array and see if it stops"?

2 hours ago, trurl said:

Unrelated, but you have a share configured to be on cache pool only, another configured to be on plex pool only. But they have files on the array or other pool. And another share not configured to use cache, but has files on cache. Mover won't move these because there is no Mover action, because there is no Secondary.

d-------s                         shareUseCache="only"    # Share exists on cache, disk1
m---a                             shareUseCache="no"      # Share exists on disk1, disk2, disk3, cache
p-------e                         shareUseCache="only"    # Share exists on plex, disk1, cache

Thanks. I am not using movers since I prefer to just move the files around myself. My plex and cache pools are separated but also sometimes I might want to use either for whatever else I am doing since these are my only SSDs. Can there be problems because of this?

2 hours ago, trurl said:

You should remove this deprecated plugin

compose.manager.plg - 2025.11.01  (Deprecated)  (Up to date)

Also, what about your user scripts?

I have now removed that.

What about my user scripts do you want to know?

10 minutes ago, draakko said:

What do you mean by "start the array and see if it stops"?

Just that: start the array and see if it can stop in safe mode with the services disabled, that is to confirm if one of those is the problem.

1 hour ago, JorgeB said:

Just that: start the array and see if it can stop in safe mode with the services disabled, that is to confirm if one of those is the problem.

Ah ok, thanks.

Is there anything in my diagnostics file which helps find the issue or are they not useful here?

Regarding compose manager, Immich official installation steps use it, is it really not recommended?

4 hours ago, JorgeB said:

start the array and see if it can stop in safe mode with the services disabled

Waiting for the result of this test.

24 minutes ago, trurl said:

Waiting for the result of this test.

I rebooted into safe mode, started the array, stopped it and it did stop without issues

11 hours ago, JorgeB said:

disable Docker and VM service and reboot in safe mode

3 hours ago, draakko said:

rebooted into safe mode

Did you also disable Docker and VM Manager in Settings?

On 4/28/2026 at 3:53 AM, trurl said:

Did you also disable Docker and VM Manager in Settings?

I disabled Docker and VM Manger

Tried stopping the array. Did not work.

Rebooted into safe mode.

Started the array.

Stopped the array. Succesfully.

Started the array.

Enabled Docker and VM manager.

Stopped the array. Succesfully.

6 minutes ago, draakko said:

I disabled Docker and VM Manger

Tried stopping the array. Did not work.

Rebooted into safe mode.

Started the array.

Stopped the array. Succesfully.

Started the array.

Enabled Docker and VM manager.

Stopped the array. Succesfully.

Tried stopping the array immediately after rebooting into normal mode and disabling VMs and Docker. Did not work.

If it works in SAFE mode but not otherwise then a plugin is the likely cause. You can disable individual plugins by booting in SAFE mode and deleting any .plg files in config/plugins, or just rename them so they aren't .plg files.

What happens if you disable the user scripts plugin using that method then boot in normal mode?

9 hours ago, trurl said:

If it works in SAFE mode but not otherwise then a plugin is the likely cause. You can disable individual plugins by booting in SAFE mode and deleting any .plg files in config/plugins, or just rename them so they aren't .plg files.

What happens if you disable the user scripts plugin using that method then boot in normal mode?

So first I boot into safe mode, remove a plugin, boot back to normal mode, and then try again?

Will I be able to restore the plugin with my settings by renaming it back to .plg?

Just making sure I dont mess up anything

19 minutes ago, draakko said:

Will I be able to restore the plugin with my settings by renaming it back to .plg?

Yes (and then rebooting)