My unraid server has had to be shut down a couple times in a few months.  Each time I stop the array it is stuck in the unmounting phase.  I had to physically power off the box to get the machine to rest.  Any ideas?  Attached is the syslog.

 

Thanks!

 

Neil

syslog-2011-06-10.txt

My unraid server has had to be shut down a couple times in a few months.  Each time I stop the array it is stuck in the unmounting phase.  I had to physically power off the box to get the machine to rest.  Any ideas?  Attached is the syslog.

 

Thanks!

 

Neil

 

 

There is something holding one of the disks busy

 

See this thread for some more information.

Below is the output but I am not really sure what it means?

 

 

root@Storage:~# /usr/bin/fuser -mv /mnt/disk* /mnt/user/*

 

                    USER        PID ACCESS COMMAND

/mnt/user/Backups:  root      2233 ..c.. bash

 

/mnt/user/Gallery:  root      2233 ..c.. bash

 

/mnt/user/MovieOrigs:

                    root      2233 ..c.. bash

 

/mnt/user/Movies:    root      2233 ..c.. bash

 

/mnt/user/Music:    root      2233 ..c.. bash

 

/mnt/user/Recordings:

                    root      2233 ..c.. bash

My Disk4 isn't blinking like it is spun down.  This disk replaced a "bad" one.

 

disk4 ST2000DL003-9VT1_5YD1BCQH 24°C 1,953,514,552 Unmounting 15,661,100 480,994 0

 

It has a ton of write compared to most other disks as well.

Below is the output but I am not really sure what it means?

 

 

root@Storage:~# /usr/bin/fuser -mv /mnt/disk* /mnt/user/*

 

                     USER        PID ACCESS COMMAND

/mnt/user/Backups:   root       2233 ..c.. bash

 

/mnt/user/Gallery:   root       2233 ..c.. bash

 

/mnt/user/MovieOrigs:

                     root       2233 ..c.. bash

 

/mnt/user/Movies:    root       2233 ..c.. bash

 

/mnt/user/Music:     root       2233 ..c.. bash

 

/mnt/user/Recordings:

                     root       2233 ..c.. bash

it indicates that process ID 2233 has threads open with those directories as their "current" directory.  You cannot un-mount the drives until the process 2233 is terminated.

 

Joe L.

Yes but 2233 is just bash?  I am the only person logged in so something isn't right?

I had the drive mounted on my Windows 2003 server and when I disconnected it and then ran that command I received no results.  I think that might have fixed it! Thanks! Is that normal?

 

That wasn't the problem after all.  I did kill 2233 and it unmounted but i don't know what 2233 / bash was that was holding it all up.

One possible answer was if you had a terminal open and were on that disk, it would keep it from unmounting. That is to say, if you were sitting in /mnt/user/[sharename] that can stop the disk from unmounting.

 

Bruce

have you downloaded the clean powerdown script? (on unmenu packages)

 

that will kill those processes automatically to allow a clean powerdown.

 

have you downloaded the clean powerdown script? (on unmenu packages)

 

that will kill those processes automatically to allow a clean powerdown.

 

next time, type

ps -fp 2233

to see what it is.

have you downloaded the clean powerdown script? (on unmenu packages)

 

that will kill those processes automatically to allow a clean powerdown.

 

next time, type

ps -fp 2233

to see what it is.

 

Thanks Joe.  Like that alternative than ps -ef | grep 2233 (or whatever the offending pid is)

 

I did kill the process and the machine went down cleanly.  Now if only I had an older machine to firmware update my stupid drives

 

Thanks!

 

Neil

 

I've used an unRIAD server to update firmware. Just connect a USB CD/DVD drive and startup from the update CD.