unRAID unresponsive after monthly parity check (small syslog incuded)

[heredago]

Clean and first install of unRAID in June  (5.0 rc4) (VM of an ESXi server with MV8 HBA's)

 

This is the second time that this exact same thing has happened but except for this, everything has worked perfectly for the last 4-5 months (initial clean install)

 

I haven't changed a single thing since the initial install in June (except for a permission on a share) and the last (and only other) time that unRAID became unresponsive like this must have been 2 months ago. (I don't know if it was at the time of the Sept 2nd parity check or not)

 

So the monthly parity check of October 2nd finished fine without any problem. But the one of this month (Nov 2nd) made my unRAID unresponsive:

• I can still Telnet into the server
  
• cannot acccess the web menu
  
• cannot acccess the smb share
  

 

unraid_syslog_nas_2012-02-11_outage_.txt

[heredago]

I've tried different things to restart the webui to no success

 

1. For the menus not running, telnet into your system and run the following at the command line to restart the unRaid webGUI

 

killall emhttp

nohup /usr/local/sbin/emhttp &

 

2. For unMenu:

 

cd /boot/unmenu

uu

 

but I received:

 

root@Tower:~# killall emhttp

root@Tower:~# nohup /usr/local/sbin/emhttp &

[1] 24575

root@Tower:~# nohup: ignoring input and appending output to `nohup.out'

 

 

 

then, I tried the Powerdown script from cmd line but received:

 

root@Tower:~# powerdown

Capturing information to syslog. Please wait...

version[24665]: Linux version 3.0.33-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #1 SMP Mon Jun 4 14:12:24 MDT 2012

ls: cannot access /dev/hd[a-z]: No such file or directory

 

[heredago]

I just completed these steps:

 

System Recovery Steps:                    

1. Rename the /boot(flash)/config/plugins directory.

2. Rename boot(flash)/extra/.

3. Use the stock go file (boot(flash)/config/go).                    

Stock go file:

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

 

but I still cannot access the Webui, I can only access \\TOWER\ and only \\TOWER\flash shows up in there 

 

 

and here is attached the full system log

syslog_2012-02-11_17-46.txt

[Helmonder]

The webgui on unraid 5 CANNOT be restarted, your only option is a reboot. If the webgui has died due to a memory issue then you can make some settings to avoid that happening again (search for OOM_ADJ in the forum)

[heredago]

I rebooted but I still cannot access the webui, the array doesn't seem started because the shares aren't showing in \\TOWER\ 

 

I can only see the USB Flash key at \\TOWER\flash and even with disabling the plugins & extras & using a stock go file, and rebooting, it still doesn't work.

 

I guess I will have to try a fresh "install" on the USB key when I get back.

 

From my understanding, I think that I shouldn't really be too worried about my data. 

 

 

[dgaschk]

I rebooted but I still cannot access the webui, the array doesn't seem started because the shares aren't showing in \\TOWER\ 

 

I can only see the USB Flash key at \\TOWER\flash and even with disabling the plugins & extras & using a stock go file, and rebooting, it still doesn't work.

 

I guess I will have to try a fresh "install" on the USB key when I get back.

 

From my understanding, I think that I shouldn't really be too worried about my data. 

 

Give at least 30 min. The journal can take over 15 minutes to replay after a crash. This will delay the availability of the server.