bungee91 Posted October 29, 2014 Share Posted October 29, 2014 This solution fixed the problem for me also. I'd call this solved! Quote Link to comment
jonp Posted October 29, 2014 Share Posted October 29, 2014 This solution fixed the problem for me also. I'd call this solved! Awesome. Thanks for everyone testing this out for us. Glad to see we got it resolved and without much trouble. Quote Link to comment
JustinChase Posted November 4, 2014 Share Posted November 4, 2014 Steps to Perform 1) Shutdown your unRAID server completely. 2) Unplug your USB flash device from your server and plug it into a Windows-based computer. 3) Download this zip file and extract it to the syslinux folder on your USB flash device, overwriting the files that are there. 4) Run make_bootable from the USB flash device root folder (make sure to Run as Administrator) NOTE: This will NOT work from a Mac at this time. 5) Unplug the USB flash device from your computer and plug it back into your server and boot. 6) After booted up, stop the array and reboot to ensure that the machine reboots correctly and that machine check errors are not displayed. 7) Coffee break! I've been annoyed by this problem for the last week or so, and was just referred to this thread. I followed these steps and can confirm it worked perfectly for me also. I just rebooted successfully for the first time in a long while. I'm currently running the latest BIOS (1.90) for my Fatal1ty Z87 Professional board. I don't recall having this issue with the previous BIOS (1.70), and only upgraded BIOS to try to help get my GPU passthru working. Anyway, thanks for this; at least one thing went right recently Quote Link to comment
garycase Posted November 5, 2014 Share Posted November 5, 2014 Very interesting -- and it continues the trend of this only happening with AsRock boards. It's very interesting that it did NOT happen with an earlier BIOS. It's now happened with x77, x87, and x97 chipsets ... all on AsRock boards. But at least the new version of Syslinux eliminates it. It'd be interesting to know exactly what the cause is ... but as long as there's a simple way to avoid it, it's clearly not worth the time to do any further isolation of the specifics. Quote Link to comment
JustinChase Posted November 5, 2014 Share Posted November 5, 2014 I'm not sure what the change was that fixed this, but I'm seeing the bootup stall for about a minute on this line... Triggering udev events: /sbin/udevadm Trigger --action=change /sbin/udevadm trigger --action-change it eventually completes, and I don't see any errors, just increases the bootup time quite a bit. just an FYI Quote Link to comment
fireplex Posted May 18, 2015 Share Posted May 18, 2015 Does anyone have a copy of this zip file as I can't download it? Thanks. Quote Link to comment
RobJ Posted May 19, 2015 Share Posted May 19, 2015 Does anyone have a copy of this zip file as I can't download it? It looks like current v6 releases already include it (syslinux v6.03), so if you prepare your flash drive with a current make_bootable, it should be fine. Quote Link to comment
fireplex Posted May 19, 2015 Share Posted May 19, 2015 Someone provided me a copy thanks Quote Link to comment
ChaOConnor Posted May 8, 2016 Share Posted May 8, 2016 Is there a copy of this anywhere? I know it's supposed to be in the latest version, but I'm getting the same error so I want to try the fix to eliminate it as a source. Thanks! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.