OK. I think I screwed something up.  As per my other post, I have been trying to upgrade a couple small IDE disks with one larger SATA disk.  I had just finished copying the contents of the last IDE drive over to the SATA disk via MC and went in to the unraid GUI to stop the array and unassign the IDE Drive.  I hit stop and the screen refreshed and showed all my disks but one as unformatted, but the array still running.  I think the problem stems from the fact that I forgot I had a putty telnet session connected to the unraid server when I tried to stop the array from the GUI.  How can I recover from this?  Here is a screenshot:

 

 

 

 

easy... terminate the telnet session, or "cd" to where you are not on one of the disks.

 

Stop any extra running processes you've added.  They're keeping the disks busy.

 

Then the array will stop.

 

You can type

lsof /mnt/disk1

lsof /mnt/disk2

etc...

 

To see which disks/processes/files are open.

 

Joe L.

I tried running lsof /mnt/disk1 and it returns:

 

-bash: lsof: command not found

I have the powerdown script installed.  Is it safe to use to shutdown any running processes? 

I have the shutdown script installed.  Is it safe to use to shutdown any running processes? 

It is safe only if you stop the array first.

 

What version of unRAID are you running?   lsof is standard these days. (I think since 4.5beta3)

 

Basically, if you have running processes YOU added, stop them.

 

Tom added his own script with the same "powerdown" name...it has been reported it just powers down.It does not stop the array first.

 

So it you do invoke powerdown, use the full path to it

 

/sbin/powerdown

 

 

If you are running cache_dirs, stop it by running

cache_dirs -q

 

 

Oh yes... it is disk8 that has the running process.  The others could all be un-mounted, and that is why in your version of unRAID they are showing as un-formatted.  DO NOT press the button labeled "Format" or you will be very unhappy as you realize you asked it to reformat your disks.

 

 

Try

fuser -cu /mnt/disk8

You probably have the fuser command on your unRAID version.

Joe L.

I am running 4.4.2 Pro.  What's the command to stop a process?  I have installed unmenu & apcupsd.  The powerdown script I installed stops the array first, but I assume it won't right now since I can;t manually stop it.

I am running 4.4.2 Pro.  What's the command to stop a process?  I have installed unmenu & apcupsd.  The powerdown script I installed stops the array first, but I assume it won't right now since I can;t manually stop it.

The command to kill a process is:

kill pid

where pid = process ID number

Here's what I get:

 

root@Tower1:/# fuser -cu /mnt/disk8

/mnt/disk8:          2120c(root)  2122c(root)

 

Array still can't be stopped and I still show the same unformatted drives.

 

How do I find the pid of a given process?

I ran ps and it returns:

 

root@Tower1:/# ps

  PID TTY          TIME CMD

12555 pts/2    00:00:00 bash

12974 pts/2    00:00:00 ps

 

 

In unmenu, under "System Info", you have a button labeled "Fuser Info"  It should show you the process holding disk8 busy.

 

The "/sbin/powerdown" script will kill processes for you ( if any can be killed ) then un-mount the drives, and then power down.   If you need, it might be used.

 

But make sure you type its full path /sbin/powerdown and not just "powerdown"

 

There are two processes 2120 and 2122 on disk 8 that have it as their current working directory. 

 

Type

ps -fp2122

ps -fp2120

 

To see them.

 

The fuser command does not kill the processes, it just lists them.  So using it will not let you stop the array, you still need to stop the two processes using the "kill" pid" command.

 

Joe L.

 

Joe L

Thanks so much!

 

I ran kill 2120 and was returned to a prompt.  I then ran kill 2122, but it errored saying there was no such process.  I guess killing 2120 killed both of them.  Either way, I was then able to stop the array and all disks showed fine.  I restarted the array and everything is as I would expect.  Thanks so much for all your help!

 

I'll make sure to close my telnet session next time before trying to stop the array.

I ran ps and it returns:

 

root@Tower1:/# ps

  PID TTY          TIME CMD

12555 pts/2    00:00:00 bash

12974 pts/2    00:00:00 ps

 

 

Next time, try

ps -ef