[SOLVED] Post move and Unraid won't start...

[talmania]

Hey all--

 

I just moved and my unraid server will boot up without problems but it will not start unraid or the unraid menu.  I've reseated all the drives and ensured the array was offline before powering down previously.

 

I've followed the instructions to post my syslog here--can someone please help?  Thanks!

 

 

jason

syslog.txt

[talmania]

So in an attempt to take the next step and possibly solve this for myself I looked at my go script and it looks like this:

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp #

/boot/unmenu/uu

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

cp --preserve=timestamps /boot/custom/etc/ssh/ssh*key* /etc/ssh

chmod 600 /etc/ssh/ssh*key*

/etc/rc.d/rc.sshd start

# install crashplan

#tar -C / -xvf /boot/packages/crashplan.tar

#/usr/local/crashplan/bin/CrashPlanEngine start

 

I noticed the last thing it's reporting on in the syslog is the emhttp is the unmenu or something else after potentially causing it to hang?  should I try commenting those out?

[itimpi]

Looking at the syslog it says appears that everything is OK, but that the array has not been started as it is not set to auto-start.

 

How are you accessing the server?    I wonder if your problem is simply that the network address has changed?

[talmania]

Thank you itimpi for the response--I sincerely appreciate it!

 

I'm accessing it via KVM over IP.  I can ping the IP address.  Interestingly enough I happened to check an infrequently used email this morning and noticed the following unraid notification:

 

WARNING - unRAID Array NOT STARTED

 

 

Server Name: Deed

Server IP: 172.23.1.31

 

Date: Wed Jun 25 22:47:13 PDT 2014

 

WARNING - unRAID Array NOT STARTED

 

 

Server Name: Deed

Server IP: 172.23.1.31

 

Date: Wed Jun 25 22:47:13 PDT 2014

 

 

Output of /proc/mdcmd:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

sbName=/boot/config/super.dat

sbVersion=2.2.0

sbCreated=1315969296

sbUpdated=1402893513

sbEvents=81

sbState=1

sbNumDisks=20

sbSynced=1401800612

sbSyncErrs=2198

mdVersion=2.2.0

mdState=STOPPED

mdNumProtected=20

mdNumDisabled=0

mdDisabledDisk=0

mdNumInvalid=0

mdInvalidDisk=0

mdNumMissing=0

mdMissingDisk=0

mdNumNew=0

mdResync=0

mdResyncCorr=0

mdResyncPos=0

mdResyncDt=0

mdResyncDb=0

diskNumber.0=0

diskName.0=

diskSize.0=3907018532

diskState.0=7

diskId.0=HGST_HDN724040ALE640_PK2334PBHBZ60R

rdevNumber.0=0

rdevStatus.0=DISK_OK

rdevName.0=sdb

rdevSize.0=3907018532

rdevId.0=HGST_HDN724040ALE640_PK2334PBHBZ60R

rdevNumErrors.0=0

rdevLastIO.0=1403759786

 

rdevSpinupGroup.0=0

diskNumber.1=1

diskName.1=md1

diskSize.1=1465138552

diskState.1=7

diskId.1=ST31500341AS_9VS09K8D

rdevNumber.1=1

rdevStatus.1=DISK_OK

rdevName.1=sdc

rdevSize.1=1465138552

rdevId.1=ST31500341AS_9VS09K8D

rdevNumErrors.1=0

 

rdevLastIO.1=1403759786

 

rdevSpinupGroup.1=0

diskNumber.2=2

diskName.2=md2

diskSize.2=1465138552

diskState.2=7

diskId.2=ST31500341AS_9VS1ELPJ

rdevNumber.2=2

rdevStatus.2=DISK_OK

rdevName.2=sdd

rdevSize.2=1465138552

rdevId.2=ST31500341AS_9VS1ELPJ

rdevNumErrors.2=0

 

rdevLastIO.2=1403759786

 

rdevSpinupGroup.2=0

diskNumber.3=3

diskName.3=md3

diskSize.3=1465138552

diskState.3=7

diskId.3=ST31500341AS_9VS1Z549

rdevNumber.3=3

rdevStatus.3=DISK_OK

rdevName.3=sde

rdevSize.3=1465138552

rdevId.3=ST31500341AS_9VS1Z549

rdevNumErrors.3=0

 

rdevLastIO.3=1403759786

 

rdevSpinupGroup.3=0

diskNumber.4=4

diskName.4=md4

diskSize.4=1953514552

diskState.4=7

diskId.4=WDC_WD20EARX-00PASB0_WD-WCAZA8379534

rdevNumber.4=4

rdevStatus.4=DISK_OK

rdevName.4=sdr

rdevSize.4=1953514552

rdevId.4=WDC_WD20EARX-00PASB0_WD-WCAZA8379534

rdevNumErrors.4=0

 

rdevLastIO.4=1403759786

 

rdevSpinupGroup.4=0

diskNumber.5=5

diskName.5=md5

diskSize.5=1953514552

diskState.5=7

diskId.5=Hitachi_HDS5C3020ALA632_ML0220F30ETWRD

rdevNumber.5=5

rdevStatus.5=DISK_OK

rdevName.5=sdo

rdevSize.5=1953514552

rdevId.5=Hitachi_HDS5C3020ALA632_ML0220F30ETWRD

rdevNumErrors.5=0

 

rdevLastIO.5=1403759786

 

rdevSpinupGroup.5=0

diskNumber.6=6

diskName.6=md6

diskSize.6=1953514552

diskState.6=7

diskId.6=Hitachi_HDS5C3020ALA632_ML0220F30LDVHD

rdevNumber.6=6

rdevStatus.6=DISK_OK

rdevName.6=sdp

rdevSize.6=1953514552

rdevId.6=Hitachi_HDS5C3020ALA632_ML0220F30LDVHD

rdevNumErrors.6=0

 

rdevLastIO.6=1403759786

 

rdevSpinupGroup.6=0

diskNumber.7=7

diskName.7=md7

diskSize.7=1953514552

diskState.7=7

diskId.7=WDC_WD20EARX-00PASB0_WD-WCAZA7876014

rdevNumber.7=7

rdevStatus.7=DISK_OK

rdevName.7=sds

rdevSize.7=1953514552

rdevId.7=WDC_WD20EARX-00PASB0_WD-WCAZA7876014

rdevNumErrors.7=0

 

rdevLastIO.7=1403759786

 

rdevSpinupGroup.7=0

diskNumber.8=8

diskName.8=md8

diskSize.8=1953514552

diskState.8=7

diskId.8=ST32000542AS_5XW2K2X7

rdevNumber.8=8

rdevStatus.8=DISK_OK

rdevName.8=sdq

rdevSize.8=1953514552

rdevId.8=ST32000542AS_5XW2K2X7

rdevNumErrors.8=0

 

rdevLastIO.8=1403759786

 

rdevSpinupGroup.8=0

diskNumber.9=9

diskName.9=md9

diskSize.9=1953514552

diskState.9=7

diskId.9=WDC_WD20EARS-00MVWB0_WD-WMAZA1059076

rdevNumber.9=9

rdevStatus.9=DISK_OK

rdevName.9=sdu

rdevSize.9=1953514552

rdevId.9=WDC_WD20EARS-00MVWB0_WD-WMAZA1059076

rdevNumErrors.9=0

 

rdevLastIO.9=1403759786

 

rdevSpinupGroup.9=0

diskNumber.10=10

diskName.10=md10

diskSize.10=1953514552

diskState.10=7

diskId.10=WDC_WD20EARS-00MVWB0_WD-WMAZA1010557

rdevNumber.10=10

rdevStatus.10=DISK_OK

rdevName.10=sdv

rdevSize.10=1953514552

rdevId.10=WDC_WD20EARS-00MVWB0_WD-WMAZA1010557

rdevNumErrors.10=0

 

rdevLastIO.10=1403759786

 

rdevSpinupGroup.10=0

diskNumber.11=11

diskName.11=md11

diskSize.11=1953514552

diskState.11=7

diskId.11=WDC_WD20EARS-00MVWB0_WD-WMAZA0987578

rdevNumber.11=11

rdevStatus.11=DISK_OK

rdevName.11=sdj

rdevSize.11=1953514552

rdevId.11=WDC_WD20EARS-00MVWB0_WD-WMAZA0987578

rdevNumErrors.11=0

 

rdevLastIO.11=1403759786

 

rdevSpinupGroup.11=0

diskNumber.12=12

diskName.12=md12

diskSize.12=1465138552

diskState.12=7

diskId.12=ST31500541AS_6XW0PY4L

rdevNumber.12=12

rdevStatus.12=DISK_OK

rdevName.12=sdg

rdevSize.12=1465138552

rdevId.12=ST31500541AS_6XW0PY4L

rdevNumErrors.12=0

 

rdevLastIO.12=1403759786

 

rdevSpinupGroup.12=0

diskNumber.13=13

diskName.13=md13

diskSize.13=1465138552

diskState.13=7

diskId.13=ST31500541AS_6XW0JM2Q

rdevNumber.13=13

rdevStatus.13=DISK_OK

rdevName.13=sdh

rdevSize.13=1465138552

rdevId.13=ST31500541AS_6XW0JM2Q

rdevNumErrors.13=0

 

rdevLastIO.13=1403759786

 

rdevSpinupGroup.13=0

diskNumber.14=14

diskName.14=md14

diskSize.14=1953514552

diskState.14=7

diskId.14=WDC_WD20EARX-00PASB0_WD-WCAZAC944241

rdevNumber.14=14

rdevStatus.14=DISK_OK

rdevName.14=sdn

rdevSize.14=1953514552

rdevId.14=WDC_WD20EARX-00PASB0_WD-WCAZAC944241

rdevNumErrors.14=0

 

rdevLastIO.14=1403759786

 

rdevSpinupGroup.14=0

diskNumber.15=15

diskName.15=md15

diskSize.15=1953514552

diskState.15=7

diskId.15=WDC_WD20EARS-00MVWB0_WD-WCAZA1239135

rdevNumber.15=15

rdevStatus.15=DISK_OK

rdevName.15=sdk

rdevSize.15=1953514552

rdevId.15=WDC_WD20EARS-00MVWB0_WD-WCAZA1239135

rdevNumErrors.15=0

 

rdevLastIO.15=1403759786

 

rdevSpinupGroup.15=0

diskNumber.16=16

diskName.16=md16

diskSize.16=1953514552

diskState.16=7

diskId.16=WDC_WD20EARS-00MVWB0_WD-WCAZA1241990

rdevNumber.16=16

rdevStatus.16=DISK_OK

rdevName.16=sdl

rdevSize.16=1953514552

rdevId.16=WDC_WD20EARS-00MVWB0_WD-WCAZA1241990

rdevNumErrors.16=0

 

rdevLastIO.16=1403759786

 

rdevSpinupGroup.16=0

diskNumber.17=17

diskName.17=md17

diskSize.17=1953514552

diskState.17=7

diskId.17=Hitachi_HDS5C3020ALA632_ML0220F30KUV9D

rdevNumber.17=17

rdevStatus.17=DISK_OK

rdevName.17=sdi

rdevSize.17=1953514552

rdevId.17=Hitachi_HDS5C3020ALA632_ML0220F30KUV9D

rdevNumErrors.17=0

 

rdevLastIO.17=1403759786

 

rdevSpinupGroup.17=0

diskNumber.18=18

diskName.18=md18

diskSize.18=1953514552

diskState.18=7

diskId.18=Hitachi_HDS5C3020ALA632_ML0221F3057MED

rdevNumber.18=18

rdevStatus.18=DISK_OK

rdevName.18=sdm

rdevSize.18=1953514552

rdevId.18=Hitachi_HDS5C3020ALA632_ML0221F3057MED

rdevNumErrors.18=0

 

rdevLastIO.18=1403759786

 

rdevSpinupGroup.18=0

diskNumber.19=19

diskName.19=md19

diskSize.19=1953514552

diskState.19=7

diskId.19=Hitachi_HDS5C3020ALA632_ML0220F30LBM0D

rdevNumber.19=19

rdevStatus.19=DISK_OK

rdevName.19=sdt

rdevSize.19=1953514552

rdevId.19=Hitachi_HDS5C3020ALA632_ML0220F30LBM0D

rdevNumErrors.19=0

 

rdevLastIO.19=1403759786

rdevSpinupGroup.19=0

diskNumber.20=20

diskName.20=

diskSize.20=0

diskState.20=0

diskId.20=_

rdevNumber.20=20

rdevStatus.20=DISK_NP

rdevName.20=

rdevSize.20=0

rdevId.20=

rdevNumErrors.20=0

rdevLastIO.20=0

rdevSpinupGroup.20=0

diskNumber.21=21

diskName.21=

diskSize.21=0

diskState.21=0

diskId.21=_

rdevNumber.21=21

rdevStatus.21=DISK_NP

rdevName.21=

rdevSize.21=0

rdevId.21=

rdevNumErrors.21=0

rdevLastIO.21=0

rdevSpinupGroup.21=0

diskNumber.22=22

diskName.22=

diskSize.22=0

diskState.22=0

diskId.22=_

rdevNumber.22=22

rdevStatus.22=DISK_NP

rdevName.22=

rdevSize.22=0

rdevId.22=

rdevNumErrors.22=0

rdevLastIO.22=0

rdevSpinupGroup.22=0

diskNumber.23=23

diskName.23=

diskSize.23=0

diskState.23=0

diskId.23=_

rdevNumber.23=23

rdevStatus.23=DISK_NP

rdevName.23=

rdevSize.23=0

rdevId.23=

rdevNumErrors.23=0

rdevLastIO.23=0

rdevSpinupGroup.23=0

[itimpi]

Have you tried accessing the unRAID GUI using the IP address (e.g. http://172.23.1.31) in case the server name is not being resolved?  If you can then you need to check under Settings->Disk Settings that autostart is enabled.

 

I notice that this setting appears to be store on the flash under /config/disk.cfg as an entry that reads:

startArray="yes"

so if you have a suitable editor it might be possible to edit that file directly rather than doing it the recommended way via the GUI.

[talmania]

Yes I've definitely tried the IP only...I'll look at the startarray piece of the disk.cfg  Thanks for that.

[bkastner]

Yes I've definitely tried the IP only...I'll look at the startarray piece of the disk.cfg  Thanks for that.

 

I see you mentioned you could ping the IP address, so this is unlikely, but from the UnRAID console can you ping out to your other machines? Or to your gateway?

 

Other than this, I would likely try a new USB drive with a virgin install. Since you have multiple disks you won't be able to mount the array, but you should be able to verify it gets an IP and try and connect to the GUI. If this works, you know the issue is with your original USB Config. At least at that point you can do a backup, reformat of USB and do a virgin install again with your Plus/Pro Key. Assuming you know which is your Parity and Cache drive you should be able to rebuild.

 

Of course, if the new virgin USB key doesn't work then you know it's a hardware issue somewhere. It will at least allow you to narrow it down a bit.

 

[talmania]

Ok I've checked the startarray and it was set to "no".  Changed it to yes and still no difference--I can now see the shares but all of them are "offline". I can ping the gateway and other machines but still no web ui.

 

I'll try the usb right now--thanks for that tip!

[talmania]

OK a new usb worked and I was able to access the gui.  Now how do I go about replacing it with my original config?  I do know which drives were my parity and cache but that's about it.

[bkastner]

Okay, that is good news.

 

So, with 5.0 or later drive placement is irrelevant. UnRAID uses the disk ID, not the position.

 

I would suggest you backup your original USB key (if you haven't already) and then reformat, do the clean install and copy back your key file (in the config folder).

 

You can also copy back ident.cfg to get your name back, network.cfg to get IP settings and share.cfg to get your existing shares.

 

Then boot up, and you will have to manually assign the drives. As mentioned, as long as you know which was parity and which was cache, the rest can be in any order. If you are 100% that parity was good you can select that as well when you go to boot up - however given the issues you've had you may want to rebuild and then test parity to make sure you are in good shape.

 

You can then go back and install whatever plugins you had.

 

Alternatively, if you had a lot of plugins and want to try and avoid the hassle, you could copy bzroot, and bzimage to your original USB and see if you get lucky. If that fails though you are basically rebuilding from scratch as outlined above.

 

 

[talmania]

Ugh..same result with the reformatted key and only copying over the .cfg files with the license key.  Is it the USB key then?  Can I copy these files to the previous usb key that worked?

[talmania]

To add I didn't get any errors when doing a checkdisk on the usb drive.

[SSD]

This is actually somewhat good news. One of the files you copied back from the backup is lukely the problem, and since your issue seems network related my guess is it's network.cfg. Copy  the stock network.cfg to the stick and try again. If you are feeling lucky you could put the disk.cfg and super.dat files from the backup onto the disk and quite likely your array configuration will be back.

 

If you have a complex setup with packages and add-ons loaded, I would suggest an alternate approach that would get you back up and running quicker. But first you need to test this hypothesis that the network.cfg file really is the problem. If it's not, try the ident.cfg file also.

[talmania]

Wow...that was it!!  replaced the network.cfg and brought back the other two and immediately it came up with correct shares and everything else!!  My huge thanks to everyone--I sincerely appreciate the help!

 

It'd be nice to have my plugins back but the only one that I used was the port 8080 web ui (name escapes me) and the email notification package.  I can and probably need to reinstall with the latest versions---off to read about plugins!

 

Thanks again everyone!

[SSD]

If you copy the go file, unmenu.directory, and package directory (might be packages) from the backup stick and reboot, I think you'll be back where you were.

 

Anyone reading this thread please realize that restoring the disk.cfg and super.dat files is dangerous and should be confirmed with someone knowledgeable on the forum. If you have made any changes to your array configuration it could cause data loss.