Jump to content
We're Hiring! Full Stack Developer ×

[solved] Power failure now array won't start


Recommended Posts

Hi everyone,

 

Lost power the other day and powered the system back up. Array will not start. I've check the logs, but I'm a bit out of my depth as to why the drives won't start/mount. Hopefully someone here will be able to point me in the right direction.

 

System information:

 

- Full Slackware 13.37 installation

- Unraid v. 5b7

- Box has been running for perfectly fine for months.

 

CPU

- Intel Core i3 2100 Intel Core i3 2100 Dual Core Hyper-threading Processor LGA1155 3.1GHZ Sandy Bridge 3MB

 

Box

- Azza Helios 910 Black ATX Mid Tower Case 9X5.25 1X3.5 4X3.5INT 230MM Blue LED Fans & Window No PSU  

 

Power

- Corsair Builder Series CMPSU-430CXV2 430W ATX Power Supply Active PFC 120MM Fan  

 

Motherboard

- MSI H67MA-E35 (B3) H67 mATX LGA1155 DDR3 PCI-E16 2PCI-E HDMI DVI Audio GBLAN SATA3 Motherboard

 

Ram

- Kingston ValueRAM KVR1333D3N9K2/4G PC3-10666 4GB 2X2GB DDR3-1333 CL9 240PIN DIMM Memory Kit

 

Current drive set up

 

/dev/sda: 160.0 GB

- Contains the OS and other files relating to unraid.

 

WDC_WD20EARS-00MVWB0_WD-WMAZA3752360 (sdd) 1953514584

- Parity - 2 TB

 

WDC_WD20EARS-00MVWB0_WD-WMAZA4483050 (sdc) 1953514584

- Disk1 - 2 TB

 

ST3160023AS_5MT2FXQT (sdb) 156250000

- Cache - 500 GB

 

Here is what I found:

 

Opened the web GUI saw the following:

 

- Parity drive green dot

- Disk1 drive green dot

- Cache drive green dot

- Flash drive green dot

- Configuration valid.

- Array status - red ball - stopped.

 

Select the start button - page refresh nothing changes.

Login CLI via ssh no mount for disk1 nothing.

 

I've gone over the syslog, message log, rebooted from command line. I'm stuck. Anyone have any opinion as to what could be the issue here?  Attached is the syslog. I did not try a SMART report because I am not seeing any drive errors.

 

thank you for your time,

 

Cary.

 

 

 

 

 

 

syslog.txt

Link to comment

I've no idea either.

 

These lines look odd???

Oct  5 21:48:17 media udevd[1072]: bind failed: Address already in use

Oct  5 21:48:17 media udevd[1072]: error binding control socket, seems udevd is already running

Oct  5 21:48:20 media console-kit-daemon[1207]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

 

I would disable any add-ons.  It might be starting to use the disks before they are mounted.

Link to comment

I've no idea either.

 

These lines look odd???

Oct  5 21:48:17 media udevd[1072]: bind failed: Address already in use

Oct  5 21:48:17 media udevd[1072]: error binding control socket, seems udevd is already running

Oct  5 21:48:20 media console-kit-daemon[1207]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

 

I would disable any add-ons.  It might be starting to use the disks before they are mounted.

 

Good question on udev and consolekit. It may be my adventures in trying to turn this in to a media server a while back. I will disable consolekit loading in rc.local. I'll look in to why the error for udev is coming up as well.

 

I don't have any add ons that I know of, other than stock installation. 

 

c

 

Link to comment

Well, I still can't seem to find anything in the system that indicates as to why the array will not start.

 

I did notice this in the logs for the GUI : "Warning: Flash device not mounted!" I can't find any reference to this error in the forms. Not sure if this is the issue.

 

Oct  6 02:06:08 media emhttp: Device inventory:

Oct  6 02:06:08 media emhttp: ST3160023AS_5MT2FXQT (sdb) 156250000

Oct  6 02:06:08 media emhttp: ST3160023AS_5MT2FYMT (sda) 156250000

Oct  6 02:06:08 media emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA4483050 (sdc) 1953514584

Oct  6 02:06:08 media emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3752360 (sdd) 1953514584

Oct  6 02:06:08 media emhttp: shcmd (73): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger

Oct  6 02:06:08 media emhttp: Warning: Flash device not mounted!

Oct  6 02:06:08 media emhttp: shcmd (74): /usr/local/sbin/emhttp_event driver_loaded

 

 

Link to comment

Well, short of the obvious "your flash drive seems fubar'ed" I would check to see if the USB port it is plugged into works.  With the power outage something may have fried.

 

Yeah, i thought so too; pulled it, checked the file system. Everything seems to be working. tried different ports. It is mounting in the FS. 

 

regardless, I will try a new key when I get home. 

 

c

 

Link to comment

A small update.

 

I've tried a fresh USB stick with a new copy of 5b12a coupled with my existing configuration. System is on line, disk is checking parity, so it appears to be either a bad USB stick or my full Slackware install has corruption some where. I will probably stick with the original stick install going forward until 5.0 is release before heading back to a full Slackware install.

 

thank you for the suggestions.

 

regards,

 

Cary.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...