I was transfering some files to unRaid when power was momentarily interrupted. The server did not shut down because it was on battery backup. When I brought up the web management page I saw that all the disks were listed as unformated, except for the parity disk and the one to which I was copying files. Parity is still valid.

 

I cannot do a graceful power shut down because when I hit the stop button, nothing seems to happen. The power off button does not appear. My question is where do I go from here? I don't want to loose the data.

 

Thanks

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Can you log in via telnet?

 

Thanks for the quick response. I am looged in from a remote computer and in the root directory.

The unformatted in the web GUI is usually a symptom of a process that is accessing he array causing a known bug in uNRAID to show it as unformatted. Normally this is only seen when you try to stop the array. I am assuming you didint try to stop the array? Could you have clicked stop by mistake in your haste? Do you run the ls -R or anything else?

 

Do you have a proper UPS with modern battery i.e. is your UPS broke cause if not your unRAID server shouldnt have seen the power outage

 

Thanks for the quick response. I am looged in from a remote computer and in the root directory.

First DO NOT PRESS THE FORMAT BUTTON to format the drives that are showing as un-formatted.

 

Next, if a drive is "busy" it cannot be un-mounted, if it cannot be un-mounted it will show up in the management interface as OK when all the others that not busy and were un-mounted show as un-formatted.

 

A file-system is busy if any file on it is open, or if any process has it (or a folder in it) as its current directory.

 

From the command line type:

fuser -mvk /dev/md*

 

To kill all the processes that have files open.  Then you should be able to use the "Stop" button to stop the array, and then "Start" to re-start it (or Reboot to reboot it)

 

Joe L.

 

I am assuming you didint try to stop the array? Could you have clicked stop by mistake in your haste?

 

I did try to stop the array, but it did no good, AFAIK. I expected the power off button to appear after I clicked on the stop button, but it did not. I then hit the stop button again, it greyed out, as before, but then returned, indicating to me the server had not stopped.

 

 

Do you run the ls -R or anything else?

 

I don't know what this is, so I guess not. I am running the lattest version.

 

 

Do you have a proper UPS with modern battery i.e. is your UPS broke cause if not your unRAID server shouldnt have seen the power outage

 

Good point!. The UPS is about 5 mos., and I will check it out after I get the problem solved

 

At this point, I need direction as how to proceed with doing a graceful shutdown and correcting the formatting error.

 

 

Do what Joe just said.

 

Also post which version of unRAID you have if it is not fixed.

Thanks, Joe! Here is what I typed and the results when I telneted in:

 

 

Tower login: root

Linux 2.6.28.4-unRAID.

root@Tower:~# ^Vfuser -mk/dev/md*

-bash: fuser: command not found

root@Tower:~# fuser -mvk /dv/md*

Cannot stat /dv/md*: No such file or directory

Cannot stat /dv/md*: No such file or directory

Cannot stat /dv/md*: No such file or directory

root@Tower:~#

You have a typo... type it EXACTLY as shown:

 

fuser -mvk /dev/md*

Sorry about that. Here is the results I got:

 

root@Tower:~# fuser -mvk /dev/md*

root@Tower:~#

 

 

I have lost the network connection to the sever so I am thinking of going down into the basement and typing stop at the server, itself

STOP

 

STOP STOP

 

 

!!!!!

 

do not do random things with your fingers crossed. evaluate, plan execute

Joe L, BubbaQ, and NAS, thanks for the help. All is well.

 

After following Joe's instructions, and reading NAS' warning, I was able to re-establish my network connection and stop the aray. I then powered down, re-booted and the drives appear normal.

 

You guys are so intelligent. 

 

 

 

 

I should have told you after running fuser, your telnet session may die.  You can then go to the web page and stop/shutdown normally.