IG82 Posted April 3, 2015 Share Posted April 3, 2015 This has occurred before but I have grown impatient and forced it to shut-down by holding the power button. I am running 5.0.6 on a Microserver, no plugins or anything special with the exception of Unmenu. After trying to stop the array it gets stuck at 'Retry unmounting user share(s)'. Attached is my syslog. I have searched for similar problems and although found the same error the resolutions did not work. Running lsof | grep mnt returns nothing. Any suggestions on how to diagnose what is causing this so I can stop it happening on every shutdown would be appreciated. Thanks Ian syslog-2015-04-03.zip Quote Link to comment
itimpi Posted April 3, 2015 Share Posted April 3, 2015 Have you tried logging in via telnet and following the suggestions in the syslog? It is saying that something is still using /mnt/user and if you have a look you might be able to work out what it is. Quote Link to comment
trurl Posted April 3, 2015 Share Posted April 3, 2015 Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Quote Link to comment
itimpi Posted April 3, 2015 Share Posted April 3, 2015 Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Also a screen session can cause this - easy to forget they might still be hanging around 1 1 Quote Link to comment
IG82 Posted April 3, 2015 Author Share Posted April 3, 2015 Have you tried logging in via telnet and following the suggestions in the syslog? It is saying that something is still using /mnt/user and if you have a look you might be able to work out what it is. Yeah, as above nothing returned by lsof, assuming fuser /mnt is the correct way to run that returns nothing either. Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. I have nothing open I am aware of, and wouldn't that report as something being open via lsof or fuser? Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Also a screen session can cause this - easy to forget they might still be hanging around Yup, have done this many times before so first thing I do is exit any screen sessions before trying to shutdown now Quote Link to comment
IG82 Posted April 7, 2015 Author Share Posted April 7, 2015 I gave up in the end and pulled the power. I had tried the provided powerdown script. After this the webgui could not be accessed although telnet was still available. Next boot it did not require a parity check so can only assume that the script did most of the job cleanly Would be great to have some more ideas here, not being able to shutdown the server cleanly and at will is an issue. Quote Link to comment
Golfonauta Posted July 21, 2015 Share Posted July 21, 2015 I have same issues in 6.0.1, it keeps retrying to unmount... Quote Link to comment
dchamb Posted November 9, 2015 Share Posted November 9, 2015 Same here and running 6.0.1. No answers? Quote Link to comment
itimpi Posted November 9, 2015 Share Posted November 9, 2015 Same here and running 6.0.1. No answers? Any reason why you are not on the current release (6.1.3)? The Open Files plugin can help with troubleshooting this sort of problems. Also it can be worth installing the Powerdown plugin as this is more likely to succeed in successfully shutting down the array than the standard built-in version. Quote Link to comment
Gragorg Posted November 22, 2015 Share Posted November 22, 2015 I occasionally get this error. Once you power down your server pull the unraid usb stick and put it in a windows PC. Windows will detect errors and ask you to scan it. Let windows scan the usb and fix the errors. Eject the usb and put it back in your server. This has always fixed it for me. Quote Link to comment
morbidpete Posted October 6, 2016 Share Posted October 6, 2016 Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Also a screen session can cause this - easy to forget they might still be hanging around waited an hour until googling this. Found this post. Damn screen sessions thanks for the tip Quote Link to comment
ChrisMChristian Posted February 1, 2017 Share Posted February 1, 2017 Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Also a screen session can cause this - easy to forget they might still be hanging around IF you are sure nothing important has a share mounted (which could be anything, stuck session that is no longer, etc). I just ssh to my unRAID server and execute: ps -ef | grep /mnt/user I then take the PID and perform a graceful kill (I've only had to do kill -9 once) kill <PID> as soon as all mounts in the process go away, your array stopping will be successful. 6 Quote Link to comment
Ulvan Posted February 17, 2018 Share Posted February 17, 2018 On 4/3/2015 at 2:46 PM, itimpi said: Also a screen session can cause this - easy to forget they might still be hanging around Apologies for necro, but big thanks for this, it has happened to me several times and only now I realized that I have one of those sessions running! Quote Link to comment
AlexT Posted August 31, 2019 Share Posted August 31, 2019 Got exactly same issue trying to stop the array, and the cause was vsftpd server, that was using /mnt/users/... so killall vsftpd immediatelly solved the issue and array got stopped. Hope that will help someone Quote Link to comment
jazzy192 Posted January 14, 2020 Share Posted January 14, 2020 On 4/3/2015 at 1:46 PM, itimpi said: Also a screen session can cause this - easy to forget they might still be hanging around Exactly what causing the same problem with me! I had a screen of Rclone or running! Quote Link to comment
bitcore Posted December 19, 2020 Share Posted December 19, 2020 On 4/3/2015 at 8:46 AM, itimpi said: Also a screen session can cause this - easy to forget they might still be hanging around This got me. Thanks!!!! Quote Link to comment
elco1965 Posted February 16, 2021 Share Posted February 16, 2021 This just started happening to me. I have looked at the syslog and the diagnostics. Something is preventing Unraid from umounting disk 13 and the cache. The cache is a pool of 4 disks configured in RAID10. I can shutdown and reboot the array but when I try to stop the array it gets stuck posting "Retry Unmounting disk share(s)" at the bottom. This forces me to refresh the web gui so the reboot button will light up. There is an issue with the libvirt img. Sometimes when I restart the array "starting services Libvirtwol..." appears and doesn't go away. I am only running one Win10 VM. Same machine with no changes for a while now. I think something with the VM is holding up the shutdown process. But with services stopped, how? I've been using Unraid long enough to know that I am not sophisticated enough to figurine out what it is. Thank you in advance. pisa-diagnostics-20210216-1218.zip pisa-syslog-20210216-2018.zip Quote Link to comment
Squid Posted February 16, 2021 Share Posted February 16, 2021 Since the VM is still running, that would be the prime candidate Windows isn't great because half the time it decides to pop up a window telling you it can't shut down for such and such reason. Best to set the VM in Settings - VM Settings to hibernate and install the virtio guest tool on the VM (its on the virtio ISO disk) Quote Link to comment
elco1965 Posted February 16, 2021 Share Posted February 16, 2021 Squid thanks for the reply. I have just reinstalled virtio guest tool on the VM. I am certain this was done in the past. I have also reconfirmed all the settings in the wiki here. I rebooted the VM and then tried to stop the array with the same result as before. Quote Link to comment
WexfordStyle Posted July 2, 2021 Share Posted July 2, 2021 On 2/1/2017 at 9:47 AM, ChrisMChristian said: IF you are sure nothing important has a share mounted (which could be anything, stuck session that is no longer, etc). I just ssh to my unRAID server and execute: ps -ef | grep /mnt/user I then take the PID and perform a graceful kill (I've only had to do kill -9 once) kill <PID> as soon as all mounts in the process go away, your array stopping will be successful. This solved it for me. Thank you! Quote Link to comment
oldirtdog Posted October 20, 2021 Share Posted October 20, 2021 On 4/3/2015 at 8:41 AM, trurl said: Also, if you do have a telnet or console session with the current directory on the array, it won't be able to unmount either. Yep... this was it for me... sometimes it's the most obvious things Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.