April 12, 201313 yr Problem: unRAID didn't boot - Screen shows it constantly Rebooting through bios after showing "Machine Check Error" - Problem is not persistent for every boot, it happens at random but when it does it loops indefinitely until interrupted. Probable source: Asrock B75 Pro3-M Motherboard (others may be affected as well since it seems to be Bios related, See more info below for links) Specific issue: Potential conflict between Syslinux 4.* bootmaker and Asrock UEFI Done so far: I have updated bios to latest (1.70) to see if maybe this fixed it. Need: I have found the newest version of syslinux (5.01) here and found the folder for the win32 binary. In case the issue isn't resolved by the bios updated can someone please confirm: a) To update I just plug flash into my win machine, copy the updated syslinux.exe and run: syslinux.exe -U (with volume drive, flags shown here for reference) b) Will this cause any problems with unRAID itself? making the 5.01 incompatible with current version of unraid? More info:I am a new unraid user, just finished setting up my configuration/plugins and copying over my data before I was going to start parity. Have restarted a handful of times without issues but today I couldn't connect. Connected screen to find computer going through boot over and over with it flashing Machine Check Error every time. Stoping boot with power button and starting it again allowed unraid to boot. After searching for the issue, discovered it may be a random error with Asrock motherboards whereby UEFI conflicts with Syslinux 4.* boot per here and here. Created this thread incase others suffer the same issue and also to ask for confirmation on possible upgrade of Syslinux. Edit: Including complete system configuration for posterity since signature may change in future: Unraid 5.0-rc12a Plus - ZALMAN MS800 - CORSAIR CX430 - ASRock B75 PRO3-M - Intel G2020 - 4GB DDR3 1333 - Data: 2 * WD RED 3TB - Cache: Seagate 7200.10 320GB - Parity: WD RED 3TB - Streaming to dedicated XBMC Box on Win7
Archived
This topic is now archived and is closed to further replies.