techiefreak

OK, so using another USB stick, the server does indeed boot to idle. So then, just as the initial error indicated, a corrupt flash drive? This brings up another issue then (after I run out and buy another "authenticated" flash drive). I have to re-register the "Flash GUID". What would the process be for that? (assuming that unRAID reps are reading this forum).

Yes.

I don't have any extra Kingston sticks laying around. I do have other (Patriot) sticks, but they are not deemed "acceptable" when I tried to register them. This is why I had to get this Kingston stick.

The server no longer boots. My BIOS settings have not changed since it was working previously. I have so far followed the BIOS setup tips as per http://lime-technology.com/unraid-server-installation/ to no avail. As the server boots, it appears to go normally, until it comes to a line... VFS: Insert root floppy and press ENTER I then hit enter and then I get... VFS: Cannot open root device "(null)" or unknown block (2,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0800 7819264 sda driver: sd 0801 7819248 sda1 00000000-01 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) Pid: 1, comm: swapper/0 Not tainted 3.9.6p-unRAID #23 Call trace: (then a lot of text)

Yes I did run the "Make Bootable" file. When I reformatted, and rebuilt the USB flash drive, I followed the instructions as indicated on the the unRAID site. I was running on 5.0rc10, but decided to upgrade to rc16c after the power failure.

We recently had a (3 hours) power failure. When everything came back up, I could no longer connect with my unRAID server. When I connected a monitor/keyboard, I saw what was happening... "LZMA data is corrupt" was the error. I figured all I had to do was reformat and re-install the latest/greatest load onto the USB stick and put my Plus.key back into the config directory. Well that didn't work. So now what?