• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Could not boot: Exec format error

Scheduled Pinned Locked Moved Unsolved
FOG Problems
3
5
7.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    lazybeard
    last edited by Jan 31, 2017, 8:10 PM

    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:

    0_1485893272592_fog_uefi_boot.PNG
    Could not boot: Exec format error (http://ipxe.org/2e008081)
    failed to boot

    ipxe.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:

    0_1485893272592_fog_uefi_boot.PNG
    Could not boot: Exec format error (http://ipxe.org/2e008081)
    failed to boot

    ipxe.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

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jan 31, 2017, 9:48 PM

      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.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • G
        george1421 Moderator
        last edited by george1421 Jan 31, 2017, 6:26 PM Feb 1, 2017, 12:23 AM

        Similar threads
        https://forums.fogproject.org/topic/9406/ubuntu-pxe-boot-fails-with-uefi

        One that has real good examples:
        https://forums.fogproject.org/topic/8666/uefi-won-boot-tools-via-fog-menu/87

        But 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

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • L
          lazybeard
          last edited by Feb 1, 2017, 3:58 PM

          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.

          G 1 Reply Last reply Feb 1, 2017, 5:10 PM Reply Quote 0
          • G
            george1421 Moderator @lazybeard
            last edited by Feb 1, 2017, 5:10 PM

            @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).

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              4/5
              Last post

            199

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project