Hi all,

Is anybody getting this when you stop the array in V5.07

Every time I try to stop the array to shut down etc it just spit out this message and I am normally left with no option but to hold the power button to restart or type reboot in the putty session.

 

Stop SMB...Stop NFS...Stop AFP...Stop AVAHI...Spinning up all drives...Sync filesystems...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...

The disks cannot un-mount if they are "busy"

 

A disk is "busy" if any file on it is open, OR if it is the current directory of any process.

 

The unRAID server is waiting for YOU to terminate any process using the disks, or for them to finish with the file they have open and close it.

 

You must stop any add-ons you might have installed, (so they close their open files )

 

You can see all the open files and process that might be using a disk by typing on the command line:

lsof | grep mnt

 

Its output will look like this if there are open files or processes whose "cwd" (current working directory) are on a disk.  In this example case two processes have a current-working-directory on disk9, so it cannot be un-mounted.

lsof | grep mnt

unraid_ad  3588  root  cwd      DIR        9,9    128          2 /mnt/disk9

sleep    25529  root  cwd      DIR        9,9    128          2 /mnt/disk9

 

You can then list the details of a given process by typing

ps -fp 3588

(3588 is the process ID printed as the second field in the prior command. Use the process ID printed by your output.)

 

The output will then show more of the involved command:

ps -fp 3588

UID        PID  PPID  C STIME TTY          TIME CMD

root      3588    1  0 Jun25 ?        00:00:00 /bin/bash /boot/custom/bin/unraid_addon_control.sh -u

In my case, a script I wrote has changed directory to disk9.  For disk9 to be un-mounted, this script would have to terminate.

(fortunately, this specific script terminates itself when it detects an attempt to stop the array. I wrote it specifically to do just that.)

 

Most programs will NOT terminate themselves.  It is up to you to stop them first.  The offending process might even be your telnet session if you logged in and then changed directory to a disk to browse its contents.  Your login shell's "cwd" is than on that disk, and it cannot be un-mounted until you log off, or change directory off of it.

 

Joe L.