December 4, 201411 yr unRAID OS Version: unRAID 6b12 Description: Performing a fresh unRAID 6b12 install on a USB flash drive fails to boot. It boots to the unRAID menu but throws an error: failed to load libcom32.c32 How to reproduce: Follow the instructions for 'Installation on a New Flash Device' using Windows. Then boot from your new USB drive. Expected results: Should boot and allow me to select an unRAID menu option or automatically proceed to boot the default option. Actual results: Continuously cycles trying to load libcom32.c32 and/or /syslinux/mboot.c32 Other information: I tried a fresh install using two different flash drives that are know to be good and error free. I can restore a flash drive backup to either key and it will boot as normal. I also tried setting up a new flash drive using the syslinux folder and make_bootable.bat from unRAID 6b10a and that does work. Performing a fresh install using unRAID 6b12 and booting the flash drive, I get to the unRAID boot menu, but it continuously cycles in a loop with the following information shown below the menu: failed to load libcom32.c32 failed to load COM32 file /syslinux/mboot.c32 My hardware info is in my sig if needed. If you want me to try something, I'll be glad to help. I thought I might download syslinux 6.03 and add or replace a file in the syslinux folder but it didn't look that simple plus you might have your own compiled version. Gary
December 4, 201411 yr I see that you have an Asrock motherboard. You may want to see if this helps: http://lime-technology.com/forum/index.php?topic=35739.msg335033#msg335033
December 4, 201411 yr Author Thanks for the help, but that fix didn't help and showed the same symptoms. I can boot fine using the syslinux from unRAID 6b10a. I think that fix included some of the syslinux v6.03 files that are also included in unRAID 6b12. Gary
December 5, 201411 yr I had the same issue, and solved it by using the make_boot and syslinux files included with the b12, apparently if your flash drive was set up with a pre-b12 syslinux boot, and you DON'T replace the syslinux folder it'll still boot, but if you replace the syslinux folder, you MUST re-run the makeboot that they included (NOT the fix files from the linked thread above), as they upgraded the version of syslinux in this release.
December 5, 201411 yr Author I had the same issue, and solved it by using the make_boot and syslinux files included with the b12, apparently if your flash drive was set up with a pre-b12 syslinux boot, and you DON'T replace the syslinux folder it'll still boot, but if you replace the syslinux folder, you MUST re-run the makeboot that they included (NOT the fix files from the linked thread above), as they upgraded the version of syslinux in this release. I started with a fresh formatted flash drive and proceeded with the unRAID 6b12 installation just as if it was my first time installing unRAID. I did this with 2 different flash drives that I have previously used with unRAID. 99% of us are usually doing upgrades so we always use the older syslinux version from previous installations. Gary
December 8, 201411 yr I have the same problem! Anyone able to upload the older syslinux file? Sure would be nice if they would have the old files on the website so i dont have to go on a tresure hunt everytime a upgrade doesnt work.... EDIT: guessed the URL http://dnld.lime-technology.com/beta/unRAIDServer-6.0-beta10a-x86_64.zip
December 8, 201411 yr Heres the fix for me. Powerdown the server, and put the usb drive in the PC Delete the syslinux FOLDER from the drive. Copy the syslinux FOLDER from http://dnld.lime-technology.com/beta/unRAIDServer-6.0-beta10a-x86_64.zip and place on the USB DRIVE Re-run make_bootable.bat Plug USB drvie into server and boot.
December 10, 201411 yr Author Marking this as solved. Adding the libcom32.c32 file provided in Eric's post as instructed fixed this on both of my flash drives. Here is the link to his post: http://lime-technology.com/forum/index.php?topic=36527.msg341361#msg341361. Gary
Archived
This topic is now archived and is closed to further replies.