February 28, 201511 yr This is starting to drive me nuts, so time to ask for help. I've had an UNRAID server running for years, most recently on 5.0.6. A recent syslog review indicated that the USB stick might be corrupt, so I decided to pull it, reformat, and start fresh. Since that time I have not been able to boot. I have formatted using Windows XP and Windows 7, Mac OS X and Ubuntu. I've tried FAT 32, exFAT and EXT4. Have also tried versions 5.x and 6.x of UNRAID. Have also changed boot sequence in the BIOS from USB-HDD to USB-FDD. When I boot I get one of two error messages, either Invalid UI or DEVICE configuration or boot disk not recognized, replace and try again. The original stick was a Sandisk Cruzer 1GB. I bought a Sandisk Cruzer 8GB and am having exactly the same issues. Have also tried booting my regular desktop PC with both sticks and get the same errors. Both my desktop and the UNRAID server will boot to Ubuntu from a USB stick, so I can't figure out why they won't boot to UNRAID. UNRAID motherboard is a Gigabyte GA-G33M-DSR2. Thank you!
February 28, 201511 yr Author Here's the full error: SYSLINUX 4.03 2010-10-22 ERROR: No configuration file found No DEFAULT or UI configuration directive found boot:
February 28, 201511 yr Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at http://lime-technology.com/getting-started. I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable.
February 28, 201511 yr Author Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at http://lime-technology.com/getting-started. I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32. I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that? And yes, have run the .bat file and all files, including the hidden ones, seem to be present and accounted for.
February 28, 201511 yr Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at http://lime-technology.com/getting-started. I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32. I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that? And yes, have run the .bat file and all files, including the hidden ones, seem to be present and accounted for. Strange then. Although it does not say so explicitly, the error message seems to imply that the syslinux.cfg file (in the syslinux folder) cannot be found. It obviously got far enough to invoke the syslinux loader. Having said that, I seem to remember something about some motherboards having problems with the latest syslinux versions. In these case an older version of syslinux worked for them.
February 28, 201511 yr Author Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at http://lime-technology.com/getting-started. I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32. I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that? And yes, have run the .bat file and all files, including the hidden ones, seem to be present and accounted for. Strange then. Although it does not say so explicitly, the error message seems to imply that the syslinux.cfg file (in the syslinux folder) cannot be found. It obviously got far enough to invoke the syslinux loader. Having said that, I seem to remember something about some motherboards having problems with the latest syslinux versions. In these case an older version of syslinux worked for them. That would make sense. I've upgraded UNRAID versions several times, but always by overwriting bzimage and bzroot files. I may have quite happily been using an old version os syslinux which I've now wiped out.
February 28, 201511 yr Author What file specifically needs to be an older version? ldlinux.sys? I tried formatting, copying the 5.0.6 files onto the stick, running mkae_bootable and then copying all files from a v4.7 back-up across to the stick. Still getting same error.
February 28, 201511 yr Author What file specifically needs to be an older version? ldlinux.sys? I tried formatting, copying the 5.0.6 files onto the stick, running mkae_bootable and then copying all files from a v4.7 back-up across to the stick. Still getting same error. Has to be some kind of compatibility issue. Was just able to boot both the old 1GB and new 8GB sticks to UNRAID 5.0.6 on my HTPC. Apparently the Gigabyte MB's in my server and desktop don't like the latest version. I still haven't been able to figure out how to roll back syslinux to an earlier version, though. Any ideas?
February 28, 201511 yr Setup your flash drive as an earlier version of v5 (maybe even down to the RC stage). See if it boots. If it does, then copy over bzimage and bzroot I've got 5rc11, rc12a, rc16c, 5.04 I can upload too you... No idea when syslinux changed however
February 28, 201511 yr Author Setup your flash drive as an earlier version of v5 (maybe even down to the RC stage). See if it boots. If it does, then copy over bzimage and bzroot I've got 5rc11, rc12a, rc16c, 5.04 I can upload too you... No idea when syslinux changed however Would very much appreciate it if you could upload 5rc11 to me. I have back-ups of working sticks, but never kept the downloads. Can you transfer the file to me in this forum? Or e-mail?
February 28, 201511 yr Author Sent PM Thank you! Unfortunately it still didn't boot. I formatted the 8GB stick, made it bootable and was able to bring up 5.0rc11 on another server. Still getting same error message when I try booting on the Gigabyte server, though. Going to go through my files and see if I can find something older that would work.
February 28, 201511 yr Is the Bios's on the server / desktop uefi? Try pounding F12 to get the boot order up. You may see the flashdrive in the twice - uefi and efi / legacy / whatever Try the legacy settings.
February 28, 201511 yr Author Is the Bios's on the server / desktop uefi? Try pounding F12 to get the boot order up. You may see the flashdrive in the twice - uefi and efi / legacy / whatever Try the legacy settings. No, I think both MB's are too old to support UEFI. I checked boot order on both and there was no mention of UEFI / EFI / Legacy (except for legacy LAN). Found a dl of 5.0rc8. Trying that now
February 28, 201511 yr Its almost starting to sound like it could be that you need to set up some boot codes for it to boot Check this out: http://www.lime-technology.com/wiki/index.php/Boot_Codes Use Notepad++ to edit
February 28, 201511 yr Author Its almost starting to sound like it could be that you need to set up some boot codes for it to boot Check this out: http://www.lime-technology.com/wiki/index.php/Boot_Codes Use Notepad++ to edit Ok, will give those a try. With 5.0rc8 I at least get a new error message: SYSLINUX 3.72 Could not find kernel image: linux boot:
March 9, 201511 yr Author I've marked this solved, but I'm not entirely sure why it's working. I decided to move all disks into a different server. That didn't work, so I was intending to change motherboards on my existing server and then move all the disks back into that box. Before I swapped MB's I tried booting from the original flash drive and it worked. So at some point I must have created an issue where the BIOS was trying to boot from a disk and wasn't able to, so it froze. I still don't know why Syslinux would freeze when it was trying to boot from the flash, but somehow I guess I got past that. So my advice would be to disconnect all disks and try booting. That seemed to help me pinpoint an eventual BIOS conflict. Good Luck!! Dave
Archived
This topic is now archived and is closed to further replies.