I know this problem is everywhere buyt I have found a workaround, but it is very annoying and I need to know if a definite solution was found.

 

I am running the latest beta, but this happens no matter what verison I am using.

 

I boot the server and everything works, then I turn it off or reboot it and I get this:

 

Triggering udev events: /sbin/udevtrigger --retry-failed

/etc/rc.d/rc.inet1.conf: line 18: /boot/config/network.cfg: No such file or directory

/etc/rc.d/rc.inet1.conf: line 19: /var/tmp/network.cfg: No such file or directory

 

To get it working again I have to pull the flash drive from the server, plug it into my laptop, recopy the bzroot and bzimage files to the drive, then plug it back into the server, and everything works again.

 

I seems to me something is not getting written correctly on shutdown.  This happens wether I shutdown from web interface, console on the server, or the power buttton.

 

Any ideas, I am not a Linux guru, more of a newbie actually, so I don't know many commands, I am quite good with computers though.

 

I am using a brand new Lexar firefly 1 gig flash drive too.

 

Any ideas?

 

Thanks

That particular problem is not everywhere.

I've read about flash drives going bad or getting corrupted every now and then, but not from a cold boot.

I would question the flash drive or the USB ports.

 

> I seems to me something is not getting written correctly on shutdown.  This happens wether I shutdown from web interface, console on the server, or the power buttton.

 

On shutdown the superblock is updated. Perhaps there is some issue with the drive or it's configuration

 

Try a different USB port or the one's on the motherboard.

 

What happens if you just unplug the drive and replug it in without copying bzimage and bzroot ?

 

When the machine does come up, does it do a parity check?

It's FAT formatted with the correct version of the HP format tool, syslinux 3.63 (the one on the UnRAID website).  I have tried different USB ports, directly on the mobo and thru a header.

 

If I just pull the drive while the server is running, flip the power switch on the computer to off, plug the flash drive back in and reboot, everything works and I can see it's running a parity check when I log into the web UI.

 

That's why I think something happens (or doesn't happen) during the shutdown process.

It's FAT formatted with the correct version of the HP format tool, syslinux 3.63 (the one on the UnRAID website).  I have tried different USB ports, directly on the mobo and thru a header.

 

If I just pull the drive while the server is running, flip the power switch on the computer to off, plug the flash drive back in and reboot, everything works and I can see it's running a parity check when I log into the web UI.

 

That's why I think something happens (or doesn't happen) during the shutdown process.

You might be right about what is happening.

 

If something happens at some point what takes your flash drive off line (after it has already been used to boot unRAID) it will not be available to write to when shutting down the array.  This will cause it to boot up next time and think ti needs to have a full parity check done as it was shut down without being stopped first.

 

You can confirm this by logging in via telnet the next time you are ready to shut down and type

ls -l /boot

 

You should see the files you loaded onto the flash drive and the config folder.  If not, then the flash drive is effectively unplugged.

If so, I suspect some hardware issue is taking it offline... it could be an interrupt conflict, or an issue with the USB port itself, or the flash drive.  (In the past, most of these issues went away by using a different flash drive)  The error would be logged in the syslog.

 

You should try to capture a syslog for us to analyze.  Since you cannot copy it to the flash drive, it makes your task a bit trickier.

 

You might be able to download and install the unmenu.awk web-interface from the thread in the user-customizations section of this forum.  It has a built-in syslog viewer, and a link to click to download a copy to your browser.  It might be just what you need to provide to us the clues needed to figure out what is happening.

 

Joe L.

 

What motherboard are you using?

 

I have this problem also, however I just hit reset a few times and it loads itself backup, no pulling the flash drive.  I am using a Gigabyte GA-P35-DS3R with current bios.