Hi All

 

This is my first post, so I am a TOTAL newbie to unRaid. I have now built my first unraid server. The hardware is:

2GB(2x1GB) Corsair XMS3 Dominator D

Gigabyte GA-MA785GT-UD3H, AMD 785G,

AMD Athlon II X2 250, Regor Core,

Coolermaster Centurion 590 Black

450W Corsair CMPSU-450HXUK, Modular

2GB Kingston Datatraveler102 USB

2TB Hitachi Saturn, 0F10311, Deskstar    x3

Only using 3 disks for the starter system without pro license.

I had a few issues getting the mobo boot correctly from the usb drive. Initially I used the 2gb Kingston (ordered specially) flash drive above - with the usb boot set to fdd in BIOS (as advised by wiki). While unraid showed ok on the boot screen (bzimage - bzroot loading with progress dots) but when it gets to end of dots, it says system ready but then reboots pc and starts all over again.

After a few attempts, I tried another old USB drive I had lying around - a 4gb sansdisk cruzer). Again, exactly the same issue as the 2gb kingston.

Now I tried an oldish 512Mb usb which I got as a promo item at a show!! Sure enough, the system booted fine and mounted the UNRAID flash volume as advertised!!

I ordered (hard to find low capacity usb flash drives!!) a Transcend JetFlash V30 - USB flash drive - 512 MB - and 2x pro unraid licenses (not sure how reliable the old 512Mb unbranded usb flash will fair in the long run!) although the unbranded drive does have the required GUID to make it unraid usable.

My assumption is: that as a boot device, the mobo does not like large volumes i.e. anything 2gb or bigger. Does this make sense??

 

Any thoughts, ideas??

Thanks

K

 

Hi Keyvan,

 

Please take a look at an earlier thread that I started, after having the exact same problems. The solution is in there as well (at the end):

 

http://lime-technology.com/forum/index.php?topic=5143.0

 

-Rob-

I have the same mobo.  Use 2 Gig for flash and have an internally mounted 8G usb drive for scratch.  Had a problem ysesterday after 2 months of no issues.  Reformatted the 2 G stick, redid the syslinux step,  copied back the saved config from the stick and was okay.