Greetings all!!!!

 

I just built a unraid machine and installed the free version for now.  I got to the main page and began the parity sync.  However, I went into settings and changed the dhcp to static and assigned an ip within range of my dhcp router.  That is when the trouble began.  It disconnected the tower and i was no longer able to login, so i restarted the tower, i am now in bios purgatory.  Once the bios checks the PCI devices, it just hangs with a blinking cursor.  The bzroot and image do NOT run.  I have tried reformatting the flash drive and reinstalling 4.1 to no avail.  Any help would be great!!!!!

 

 

Ruby

First, make a backup of the files in the flash's config directory.  Then cut and paste the contents of ident.cfg and network.cfg, and post here.

 

Then, I would re-install the 4.1 distro files to the flash, that should get you going again.  Before starting the array, get all identity and network settings correct and reboot.  After rebooting and restarting your Windows browser, if all is well, then start the array and let it build parity.  This does not answer the question of what went wrong, but gets you running.  Perhaps someone may see something in the contents of network.cfg or ident.cfg that will provide a clue to what went wrong.

 

I don't know this for sure, but it's probably not advisable to change network settings with the array running, since you will or may lose the network connection briefly.  You probably would need to restart the browser, because the unRAID server address may have been changed.  Rebooting and restarting after network changes is probably safest.

 

Blinking Cursor sounds like what I get when the Asus Bios suddenly decides that a HDD would be a better default boot device than the USB key that has the OS on it.

 

Which mobo do you have?

 

I make all the assigned boot devices "Not Installed" other than the USB stick (usually referred to by name "Sony Micro" in my case).

 

Then I choose "Auto" in my USB setup, though plenty here have had success with USB-Floppy & USB CD-Rom.

 

Mark.

So, i cleared my CMOS and was able to get out of bios hell.  However, now, with my newly formatted and re-updated with 4.1 Cruzer mini, i have a new problem.  Once i select the boot order to USB-HDD, it says "remove disk or other media, press any key to reboot".  When i take out the usb drive, it says, "system disk not found".  Every time i reboot with the flash drive in the usb, it says to remove disk or other media.  I am using the Gigabyte 965-ds3 MB.

 

 

Any advise on this one? 

 

p.s., thanks for jumping in on this one!!!!!

 

 

Ruby

What other USB options other than USB-HDD do you have?  "Auto" would be great, others have previously suggested "Force FDD Mode".

 

On my Mobo the methos to treat USB boot as is separate from the boot order list.

 

I'm not familiar with your Mobo I'm afraid.

 

I have been there, and there will be a bios setting that'll work, it's just finding it.

 

Mark.

I am a tool.  (Says with head held low) I forgot to reinstall syslinux on the flash drive.  The only reason i suggest keeping this thread is so other noobie-chuckleheads like me can learn something. 

 

 

Thanks all!!!!

 

 

Ruby

 

p.s. - Everything is working again.

Not the same Mobo but this may help

 

If I recall, it said "Hard Drive 3-0", or something similar - that was when I updated the Bios using a flash drive.  When I loaded Unraid, I think I used the "boot drive selection menu" and it showed as a flash drive.  I''ll check.

 

 

Edit...The selection menu offers the following choices - Floppy, LS120, Hard-Disk, CD-ROM, ZIP, USB-FDD, USB-ZIP, USB-CDROM, USB-HDD, Legacy LAN.

 

Selecting the hard drive option to boot back into Windows gave me the choice of all the hard drives to boot from.  My plugged in Flash Drive was shown here as a USB-HDD (listed as a Sandisk U3 Cruzer Micro).  Hope this helps

 

from This Thread

 

Good luck!

 

Mark.

I am a tool.  (Says with head held low) I forgot to reinstall syslinux on the flash drive.  The only reason i suggest keeping this thread is so other noobie-chuckleheads like me can learn something. 

 

 

Thanks all!!!!

 

 

Ruby

 

p.s. - Everything is working again.

 

Hey!  I wouldn't have admitted it!  You're a bigger man than me!  I'd have just said "Thanks for the help!  I got it working!"

 

Mark.