Could not boot: Exec format error
-
Server
- FOG Version: 1.3.4
- OS: Ubuntu Server (current rev)
Client
- Service Version: N/A
- OS: N/A
Description
When booting an UEFI client, I can get to the FOG menu successfully but when I navigate to the Advanced menu and launch one of the ISOs I have configured (Jetico disk wipe software), I get the error:
Could not boot: Exec format error (http://ipxe.org/2e008081)
failed to bootipxe.efi is the current bootfile that is being used per https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
I can use the same ISO to boot into BIOS without issue and works in our current production environment with FOG 1.2.0
Any ideas?
Thank you
Server
- FOG Version:
- OS:
Client
- Service Version:
- OS:
Description
Server
- FOG Version: 1.3.4
- OS: Ubuntu Server (current rev)
Client
- Service Version: N/A
- OS: N/A
Description
When booting an UEFI client, I can get to the FOG menu successfully but when I navigate to the Advanced menu and launch one of the ISOs I have configured (Jetico disk wipe software), I get the error:
Could not boot: Exec format error (http://ipxe.org/2e008081)
failed to bootipxe.efi is the current bootfile that is being used per https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
I can use the same ISO to boot into BIOS without issue and works in our current production environment with FOG 1.2.0
Any ideas?
Thank you
-
SO you cannot boot the ISO’s from UEFI, but you can from BIOS?
I would think, then, the ISO is not designed to be run from a UEFI layout.
-
Similar threads
https://forums.fogproject.org/topic/9406/ubuntu-pxe-boot-fails-with-uefiOne that has real good examples:
https://forums.fogproject.org/topic/8666/uefi-won-boot-tools-via-fog-menu/87But I agree with Tom that the third party iso image has to support uefi or it won’t boot anyway. You can tell by burning the iso to a cd/dvd and then inserting it into the target computer and select the firmware boot menu (typ F12) and see if in the uefi section there is an option to boot the cd/dvd. The other way to check is to look at the contents of the iso and see if there is a /efi/boot/bootx64.efi file off the root directory of the iso image
-
I was able to confirm that the ISO does support UEFI booting (I knew previous versions had, I just wanted to confirm), as you said, the USB key shows up in the boot menu and it does load successfully afterwards.
Looking through the two threads mentioned, looks like I need to dig into how it’s being loaded into memory, here it is today:
:DiskWipePRODDEBUG initrd ${boot-url}/service/ipxe/diskwipe/DiskWipe_2.31_MC_Debug.iso chain memdisk iso raw || echo failed to boot prompt goto MENU
Looking through the ISO in question, I found the /efi/boot/x64 directory where it lays out grub.cfg as:
insmod part_gpt insmod part_msdos insmod fat insmod iso9660 insmod efi_gop insmod efi_uga insmod font loadfont /efi/boot/font.pf2 insmod gfxterm set gfxmode=800x600 set gfxpayload=keep terminal_output gfxterm linux /vmlinuz.x86_64 root=/dev/ram0 rw init=/init video=efifb loglevel=3 initrd /wipe-x86_64.lz /firmware.lz /bcwipe boot
I’ll be taking a look at this later today once I get time.
Thank you for pointing me in the right direction.
-
@lazybeard In this case, you could extract the contents of the iso into a http path on the fog server (i.e. /var/www/html/iso/diskwipe
And then reference the files via http
linux http://<fog_server_ip>/iso/diskwipe/vmlinuz.x86_64 root=/dev/ram0 rw init=/init video=efifb loglevel=3 initrd http://<fog_server_ip>/iso/diskwipe/wipe-x86_64.lz http://<fog_server_ip>/iso/diskwipe/firmware.lz /bcwipe
Understand this is just a guess and it will need to be translated into what iPXE needs to boot the file (you can see that from the url I provided before).