Hi

something is wrong with my Unraid Server. I cant stop the array anymore. I get the following error message:
 

May 17 12:20:07 blackbox root: rmdir: failed to remove '/mnt/user': Device or resource busy
May 17 12:20:07 blackbox emhttpd: shcmd (3913): exit status: 1
May 17 12:20:07 blackbox emhttpd: shcmd (3916): /usr/local/sbin/update_cron
May 17 12:20:07 blackbox emhttpd: Retry unmounting user share(s)...
May 17 12:20:12 blackbox emhttpd: shcmd (3917): /usr/sbin/zfs unmount -a
May 17 12:20:12 blackbox emhttpd: shcmd (3918): umount /mnt/user
May 17 12:20:12 blackbox root: umount: /mnt/user: target is busy.
May 17 12:20:12 blackbox emhttpd: shcmd (3918): exit status: 32
May 17 12:20:12 blackbox emhttpd: shcmd (3919): rmdir /mnt/user
May 17 12:20:12 blackbox root: rmdir: failed to remove '/mnt/user': Device or resource busy

 

What confuses me on top of this is that I'm not using zfs at all. All my drives are formated with xfs or btrfs.

blackbox-diagnostics-20250517-1234.zip

 

How can I fix this?

Thank you very much for your help and suggestions!

 

Edited May 17, 20251 yr by Tom082
added diagnostics

50 minutes ago, Tom082 said:

hat confuses me on top of this is that I'm not using zfs at all.

That's a general zfs unmount, it's always done, without checking if zfs is being used or not.

 

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.

 

 

Docker and VM Services were disabled when it happened. I was adding a redundant Cache Pool and therefore first moved off /appdata, /system and /domains from my NVMe to the Array following SpaceInvader's guide.

The issue above happened after using mover. It could not move /system completely and stopped moving files at some point. So I stopped mover via CLI and restarted. It still did not move the remaining files. Hence I tried to stop/start the array and the above happened.

I then rebooted via CLI. The server came up and started parity check due to an unclean shutdown. Then I manually copied /system to my backup folder, stopped the array and then renamed the NVMe from Cache to Work, added 2 SSD in a BTRFS RAID-1 Pool named Cache and invoked mover again to transfer all data back to Cache or Work depending where I want it. This time mover had no issues..

When all was moved I tried to stop the array once more out of curiosity, and again the same issue as above. To me this seems to be a mover related issue.

I rebooted again, canceled parity check and tested stopping/starting the array with Docker and VM services still disabled. It worked flawlessly multiple times.

I have now started parity check...