Hi,

 

I wanted to do a few (software/add-on) tests with unRAID and took some "old" spare Hardware (Gigabyte GA-965P-DS3 Rev. 1.0 + C2D E6600), shoved it into a case along with a PSU, a passiv Geforce 7300LE, 1GB RAM, Samsung SATA HDD and voila unRAID testing machine...

The problem now: I copied the newest unRAID files (V5 Final from the main site) on a 4GB USB (the same model I use for my regular unRAID) and at boot, the "SYSLINUX: No DEFAULT or UI configuration directive found!" error message pops up. I checked Google and the answers I found were about renaming the syslinux files, but they are already correctly named.

 

Any suggestions? 

Not sure why this system is giving that error, but I have seen several older systems that won't boot with the newest version of the loader that's installed by the current "makebootable".

 

Reformat your flash drive;  then use v4.7's "Makebootable" to make it bootable;  then copy the v5.0 files to the flash drive and try that.

 

If I do that, I get a "Could not find Kernel image linux" error... :\

Is it formatted as FAT or FAT32?

 

Did you run make bootable as admin in win7?

 

1. FAT32

2. Yes

Hey I get the same error!

 

This happened to me after flashing a new bios (Gigabyte GA-K8NS-939 Ultra), on a USB stick that has already been working.. I tried formatting it but same issue..

UPDATE:

 

I was able to get it working... I formatted the USB stick to FAT instead of FAT32 and it started working.

 

I googled and I found someone with a similar issue: http://superuser.com/questions/541219/linux-usb-key-only-able-to-boot-when-formatted-to-fat-gigabyte-motherboard

 

Might be an issue with newer BIOS vers of old mobos... oh well...

UPDATE:

I was able to get it working... I formatted the USB stick to FAT instead of FAT32 and it started working.

Damn... still doesn't work for me.

Downloaded BOOTICE and tried pretty much everything possible. FAT16 with 4GB, Multi Partition with only 9xxMB Partition Size and FAT16 (even tried FAT32 as well), tried using MBR and GPT, even tried all this with 4.7 instead of 5.

The only thing that changed: I don't get any error message at all, only the blinking pipe after the device listing. :\

 

Edit: Even updated the BIOS to Version F14... still nothing.

btw I tried my 2,5" external ~60GB HDD with Win 8.1 on it... that boots perfectly fine into the Windows installation setup.

Found a 512MB USB-Stick, formatted it FAT16, copied V5 Files on it, used the make_bootable.bat... aaaaaand it works.

Tried to format the 4GB Stick with >512MB and FAT16... doesn't work.

 

I really would like to use this Hardware/USB as my "new" unRAID Server, making my current one into a semi-passiv Linux everyday PC, is there any way to get my Plus License changed to this USB? (The License was connected with the USB-Sticks ID if I remember right?) 

Found a 512MB USB-Stick, formatted it FAT16, copied V5 Files on it, used the make_bootable.bat... aaaaaand it works.

Tried to format the 4GB Stick with >512MB and FAT16... doesn't work.

Many older BIOS have no idea how to deal with larger flash drives.  Some even had issues with drives as small as 1GB.

 

Since unRAID works fine on a 512Meg drive, just use it and be happy.  (You could look for a BIOS update though)

Since unRAID works fine on a 512Meg drive, just use it and be happy.  (You could look for a BIOS update though)

Already updated the BIOS as mentioned in the post before. The problem with the 512MB drive is the Plus License. If I remember right, the license was connected with the drive ID or not? (I want to move everything to the "new" machine, including the needed 512MB drive - else it wouldn't work )

email Limetech describing your issue and giving the GUID of the drive for which the Pro license applies, and the GUID for which you want it to apply.  They are normally good about issuing a new license for the new drive, although I believe Limetech always reserves the right to ask for you to send them the physical drive you no longer want to use.

For the TL;DR people: In case of this problem choose USB-FDD instead of USB-HDD. (in my case with "BOOTICE v1.1.5 x64" -> "Parts Manage" -> "Re-Partitioning")

 

 

Phew... good thing that Joe L. reminded me of older Hardware having problems with USB-Sticks of bigger size. Somehow that stuck in my head all the time. "Why could it boot a 60GB external HDD but not a stupid USB-Stick of smaller size?" ... "Let's check BOOTICE again". This time, instead of making a 4GB FAT16 "USB-HDD Single Partition" or a "Multi-Partitions" with the first partition being smaller than 512MB, I chose to good old "USB-FDD" Mode... and it works like a charm, even with 4GB!

 

 

I'm getting the same error. I have tried several different brand and age USBs, i have tried 5.0, 5.0.5, 6.0b3 and still i get the same error. I my virtual machine and on a netbook the USBs boot fine. I have no idea what to do @_@ Can somebody help please?

bump?

bump?

I'll help you with a bump.

 

The problem is pretty obscure...not many of us have encountered it and don't know how to walk you through possible fixes.

And its in a thread marked 'Solved'.

 

If you don't hear anything in a day, start a new thread in the 'General Support' forum...add a link BACK to this thread.

Be sure to describe your hardware setup (including motherboard model if you know it...)

and what you've already tried as fixes.  And were you successful at changing the format of your flash to FAT or FAT16 and not FAT32?

 

Edit: Just found this: http://www.geekzground.com/index/?p=27

Worth a try.

Thanks for the reply. I tried changing the names, that didn't have any effect. Trying 4.7 and 5.0b14 with Syslinux 3 instead of 4 i get Could not find kernel image: linux. Starting to worry it could be my motherboard? I'm not sure of the model but its a gigabyte.

 

Any ideas?