Array Stopping - Retry unmounting user share(s)...

[j44rs4]

This is my first post in this forum, so please bare over with me.

 

I try to stop the Array, but It will not shut down, only leaving me the message "Array Stopping•Retry unmounting user share(s)..." 

 

I installed this, to see what files are active: https://lime-technology.com/forums/topic/41196-open-files-plugin-can-help-with-troubleshooting-why-server-wont-shut-down/

 

The files that shows up is from udev:

/lib/modules/4.14.49-unRAID/modules.builtin.bin /lib/modules/4.14.49-unRAID/modules.symbols.bin /lib/modules/4.14.49-unRAID/modules.alias.bin /lib/modules/4.14.49-unRAID/modules.dep.bin    There is no help in killing the actual PID either.   And the Syslog says: Jun 28 09:09:54 Tower root: rmdir: failed to remove '/mnt/user': Device or resource busy Jun 28 09:09:54 Tower emhttpd: shcmd (31097): exit status: 1 Jun 28 09:09:54 Tower emhttpd: shcmd (31099): /usr/local/sbin/update_cron Jun 28 09:09:54 Tower emhttpd: Retry unmounting user share(s)... Jun 28 09:09:59 Tower emhttpd: shcmd (31100): umount /mnt/user Jun 28 09:09:59 Tower root: umount: /mnt/user: target is busy. Jun 28 09:09:59 Tower emhttpd: shcmd (31100): exit status: 32 Jun 28 09:09:59 Tower emhttpd: shcmd (31101): rmdir /mnt/user Jun 28 09:09:59 Tower root: rmdir: failed to remove '/mnt/user': Device or resource busy Jun 28 09:09:59 Tower emhttpd: shcmd (31101): exit status: 1 Jun 28 09:09:59 Tower emhttpd: shcmd (31103): /usr/local/sbin/update_cron Jun 28 09:09:59 Tower emhttpd: Retry unmounting user share(s)... Jun 28 09:10:04 Tower emhttpd: shcmd (31104): umount /mnt/user Jun 28 09:10:04 Tower root: umount: /mnt/user: target is busy. Jun 28 09:10:04 Tower emhttpd: shcmd (31104): exit status: 32 Jun 28 09:10:04 Tower emhttpd: shcmd (31105): rmdir /mnt/user Jun 28 09:10:04 Tower root: rmdir: failed to remove '/mnt/user': Device or resource busy Jun 28 09:10:04 Tower emhttpd: shcmd (31105): exit status: 1 Jun 28 09:10:04 Tower emhttpd: shcmd (31107): /usr/local/sbin/update_cron Jun 28 09:10:05 Tower emhttpd: Retry unmounting user share(s)...

 

 

Can someone help me out?

[tjb_altf4]

I have it happen more often than I'd like.

I tend to be able to reduce it by doing a few tasks ahead of time:

•  running mover (and finishing)
• shutdown all dockers
• shutdown all vms

then I usually run fuser -km /mnt/user as the hail mary if it still happens.

[j44rs4]

Hi, and thx for quick reply.

 

I don't run any dockers or vms, and always make sure that mover finished, but still no luck

 

I also tried your command in hope of any progress, but I can still see the same files are active.

Does anyone know what these files do, and why they are noe killed in the process?

 

Even after killing the process, nothing happens.....still the same error message.

[CHBMB]

First thing I'd check is you don't have a client machine with a file or folder open.  This tends to happen when something is accessing the share.

[JorgeB]

Or an active SSH session to /mnt/something

[j44rs4]

Hi, and thx for all suggestions.

Problem is now solved.

 

I ssh'ed in, to see if there where any shares/mounts that did not shut down poperly. And yep, there it was. A share that I manually mount in the GO-file, to use for ProFTPd

 

Once that share was unmounted, the array shut down.

[cinereus]

On 6/28/2018 at 2:20 PM, tjb_altf4 said:

then I usually run fuser -km /mnt/user as the hail mary if it still happens.

This is the only thing that worked for me. What does it do?

[tjb_altf4]

9 hours ago, cinereus said:

This is the only thing that worked for me. What does it do?

Simple answer is you are killing any running process still accessing files in your user shares.

[cinereus]

15 hours ago, tjb_altf4 said:

Simple answer is you are killing any running process still accessing files in your user shares.

Why does the stop array script not include this after a certain delay?

[Alcapone001]

On 1/10/2023 at 6:35 PM, cinereus said:

Why does the stop array script not include this after a certain delay?

 

This is what i also dont understand why it cant do this by default. I mean you initiated the Shutdown, so it is not like you have any active processes running. 

 

For me I get this error and it can be a tad frustrating. I have no VMs setup and No one accessing shares. 

[tjb_altf4]

I get this on occasion still, and for some reason if I open the web cli and run top, it will finish stopping immediately.

[ryry]

This issue occurs for me as well.  I don't really have a way of shutting down cleanly as it is.