Running v4.3.3 & everything was fine.  Moved all hardware to a shiny new case and now the server doesn't start properly. 

 

Everything appears to go as normal when booting, but it almost appears as if something is wrong with the files on my USB key.  After BZROOT finishes decompressing and stuff start to load things fly past on my screen too fast to see what's going on but when it finishes I'm left with a "Tower login:" prompt (which should say "unraid login:" because I've renamed my server), however things are clearly not OK.  For starters, my server is not visible on my network and above the prompt are some errors like:

 

  "/var/tmp/network.cfg: No such file or directory"

 

  "/boot/confit/network.cft: No such file or directory"

 

  "mount: special device /dev/disk/by-label/UNRAID does not exist"

 

Also, when I login as "root" it doesn't ask for a password.

 

I'm down HARD and I'm clueless.  I could really use some help.  Anyone??  Please??

 

EDIT:  I don't imagine it matters but I actually did change one piece of hardware.  I installed a new "PC Power & Cooling EPS12V 610W" power supply.

It is acting as if the UNRAID volume label cannot be found.

 

Are you using the same motherboard, etc?

Are you using the same flash drive? 

Are you using a different USB socket on the motherboard?

(normally does not matter, but who knows)

 

After logging in type:

ls -l /dev/disk/by-label

 

ls -l /dev/disk/by-id

 

mount

 

ls /boot

 

report back with what you get as results.

 

Joe L.

The strangeness continues.  After I posted my first cry for help, I rebooted my server again and it fired up as it was supposed to.  The only thing that didn't seem to work was web access to the unMENU web interface.  All the page showed was "e 0" in the upper left hand corner.  (however the unRAID web interface worked just fine).

 

This morning after reading Joe L.'s reply, I restarted the server and now it won't start up properly again.

 

All the hardware is the same except that I moved to a brand new Lian Li case (it's pretty, but I'm not expecting that its a better looking case that caused this problem).  Also, it doesn't seem to be any particular USB socket that causes the problem because that was the first thing I suspected when I thought I could correct the problem myself.

 

When I type "ls -l /dev/disk/by-label" I'm told "/bin/ls: cannot access /dev/disk/by-label: No such file or directory"

 

When I type "ls -l /dev/disk/by-id" my 4 disks are listed 16 times (each twice as ata and again 2 more times as scsi - sda thru sdd and sda1 thru sdd1)

 

When I type "mount" I get the following:

 

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

usbfs on /proc/bus/usb type usbfs (rw)

 

When I type "ls /boot" I get no response at all

 

 

 

Are you using any PCI cards?  If so, reseat them.

Reseated my PCI SATA controller... Restarted... worked this time.

 

I did a little more experimentation with the USB sockets.  From what I can tell so far, it will consistantly fail to start properly if I'm plugged into a socket cabled to the motherboard.  If I plug into a socket out the back (socket soldered to the MB) it starts properly.

 

This makes no sense to me.  It shouldn't matter.  But, there you go.

You may have to enable power to the USB socket via a jumper. It could be that or there is not enough standby power to satisfy all the USB sockets. It could also be a cable or interference with the cable.

Your USB flash drive could also be going bad.  RobJ once noticed some issues in one of my syslogs and suggested possible flakienss of my flash.  Eventually, it would usually take two tries to get my unRAID started (yep, I would get what looked like a good unRAID boot but the last couple of lines were files missing from /boot/config).  I continued using the flash until I got some kind of write error in vi and half my custom packages directory dissapeared.  I changed to my 2nd flash and haven't had any more issues.  My flash was attached to the USB ports from the montherboard.