What is bocking unraid from unmounting my disk?

[xamindar]

I rarely shut down my unraid but it always bugs me that it will not unmount all the drives so I end up having to shut it down unsafe. This time I can not figure out what is causing it. What else can I use besides lsof?

root@Chiroru:/# lsof /mnt/disk2
COMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
unraid_ad 1365 root  cwd    DIR    9,2  144    2 /mnt/disk2
sleep     6013 root  cwd    DIR    9,2  144    2 /mnt/disk2
root@Chiroru:/# lsof /dev/md
md1  md2
root@Chiroru:/# lsof /dev/md2
COMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
unraid_ad 1365 root  cwd    DIR    9,2  144    2 /mnt/disk2
sleep     6028 root  cwd    DIR    9,2  144    2 /mnt/disk2
root@Chiroru:/#

Isn't unraid_ad the management its self?

[Ford Prefect]

I rarely shut down my unraid but it always bugs me that it will not unmount all the drives so I end up having to shut it down unsafe. This time I can not figure out what is causing it. What else can I use besides lsof?

root@Chiroru:/# lsof /mnt/disk2
COMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
unraid_ad 1365 root  cwd    DIR    9,2  144    2 /mnt/disk2
sleep     6013 root  cwd    DIR    9,2  144    2 /mnt/disk2
root@Chiroru:/# lsof /dev/md
md1  md2
root@Chiroru:/# lsof /dev/md2
COMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
unraid_ad 1365 root  cwd    DIR    9,2  144    2 /mnt/disk2
sleep     6028 root  cwd    DIR    9,2  144    2 /mnt/disk2
root@Chiroru:/#

Isn't unraid_ad the management its self?

 

hmm, might be a silly question to ask...

...but are you happen to have a shell/terminal session active

to your unRAID box, with i'ts PWD pointing to one of the disks/shares?

 

[xamindar]

Nope. Just had one but it was at /

[Joe L.]

you have unraid_addon_control.sh running.

 

It specifically makes one of your disks busy so it can perform any shutdown tasks of add-ons you've added.

It, once those processes are completed, would "cd" off of disk2.

 

I've got no idea how old the version of unraid_addon_control.sh you are running (if it is one that has all the changes I've made to it over time) or how you invoked it, you'll need to tell me what you've added to your system that you are having it start and stop. 

 

Worst case, just terminate it with the kill command

kill 1365

(1365 is the process ID of unraid_addon_control.sh as reported by the lsof command)