Unable to Load Fog PXE Menu



  • I can’t get my PC to actually PXE boot and load the first Fog menu. All I’m trying to do at this point is the initial host registration.

    I’m very new to Fog and I’ve never much with Imaging software before, so I’m trying to learn about it.

    Currently I’m getting a “Could not boot: exec format error 2e008081” message everytime I try to PXE boot.

    I’m using an Asus Z270-a motherboard with Secure Boot disabled, and UEFI.
    I’ve spent a few hours searching the internet for the issue and basically everything was saying it was secure boot causing the issue.

    Any assistance would be appreciated.


  • Developer

    @lordbob75 Good to hear you got this fixed! Though the error message for me didn’t point to be the IPs to be the issue. But well.

    Would you be interested to get in touch with the person who created the Docker image to see if he/she’d be keen to update the FOG version?



  • OK, so I fixed it.

    Honestly not really sure how, but here’s what I did:
    Removed the container and data
    Reinstalled with the server IP in the config set to .200 as well

    That’s all it took. Tried this as part of setting up a virtual machine to run it, but ended up not needing to finish that setup.

    Thanks!



  • @Sebastian-Roth said in Unable to Load Fog PXE Menu:

    I have to say that I have not used docker much yet. So I am not sure what you mean by “actual Server IP”. Can you run ip a s within the container and post output here?

    It’s the IP address of my server. The container was set with it’s own IP instead of using the servers IP address like other containers since it wants to use port 80 (which the webGUI for the server runs on).

    ip a s output:

    # ip a s
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
    2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
        link/ipip 0.0.0.0 brd 0.0.0.0
    3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
        link/gre 0.0.0.0 brd 0.0.0.0
    4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
        link/ipip 0.0.0.0 brd 0.0.0.0
    7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
        link/sit 0.0.0.0 brd 0.0.0.0
    34: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
        link/ether 02:42:c0:a8:01:c8 brd ff:ff:ff:ff:ff:ff link-netnsid 0
        inet 192.168.1.200/24 brd 192.168.1.255 scope global eth0
           valid_lft forever preferred_lft forever
    

    We don’t seem to find the time to support an official Docker image. So it’s up to community (you and other people) to keep this up to date.

    Fair enough.

    @Sebastian-Roth said in Unable to Load Fog PXE Menu:

    @lordbob75 The “Exec format error” makes me think the client might be the issue. Do you have other machines at hand to test PXE booting to see if another one can properly load the FOG menu?

    On the other hand I can imagine the iPXE binaries in 1.5.5 causing the problem. It’s not very likely but you never know. You can download the latest binaries from github and give it a try.

    I just pulled out a 10ish year old laptop (still works!) with a BIOS (not U/EFI) and PXE booted it. No errors, but it just sits and hangs after the:

    http://192.168.1.3/fog/service/ipxe/boot.php... ok
    

    Oh, and I’ll try updating the binaries later, out of time for the day.


  • Developer

    @lordbob75 The “Exec format error” makes me think the client might be the issue. Do you have other machines at hand to test PXE booting to see if another one can properly load the FOG menu?

    On the other hand I can imagine the iPXE binaries in 1.5.5 causing the problem. It’s not very likely but you never know. You can download the latest binaries from github and give it a try.


  • Developer

    @lordbob75 said:

    Correct on the 2 IPs. *.3 is my actual Server IP and *.200 is the IP of the container.

    I have to say that I have not used docker much yet. So I am not sure what you mean by “actual Server IP”. Can you run ip a s within the container and post output here?

    I could definitely spin up a VM and try running FOG on that, but my end goal would still be to use a containerized version if possible.

    We don’t seem to find the time to support an official Docker image. So it’s up to community (you and other people) to keep this up to date.



  • @Sebastian-Roth

    Correct on the 2 IPs. *.3 is my actual Server IP and *.200 is the IP of the container. This is how I originally set it up if that matters.
    I could try removing the separate IP, but I’d have to mess with the ports and stuff, and I didn’t think it was necessary.
    Here is a screenshot of the container settings that may be helpful.
    Annotation 2019-12-25 081352.png

    I get the error right when I first PXE boot. Once I choose IPv4 PXE boot, the picture above is the only thing I get. Takes about 1 minute from initializing devices to failing.
    I have never seen the FOG menu yet.

    I could definitely spin up a VM and try running FOG on that, but my end goal would still be to use a containerized version if possible.


  • Developer

    @lordbob75 There seem to be at least two different IP addresses involved (as seen in the picture). What systems do those belong to? If you ever changed the IP of your server you want to check our wiki on how to do this properly!

    The other thing I am wondering is when you get to the Exec format error? Does the FOG menu load and when you try to register a host it fails with the error or do you never get to see the menu?

    While 1.5.5 is old I don’t see this version would cause this problem per se. I would still suggest you setup your own server after you have played with the Docker version a bit.

    The forum is setup to have the newest posts at the top.



  • @george1421 not sure if I replied in the right way to this thread since it’s above your post.

    PFSense does not appear to have an Option 67.
    Untitled.png

    Picture of error:
    IMG_20191224_200144_1.jpg

    I am currently running FOG version: 1.5.5
    I’m using a docker container (https://hub.docker.com/r/mudislander/fogproject//Dockerfile/), which I realize is not the newest version. I’m fairly sure I have to wait for the update to the container rather than trying to update it myself, but not positive on that.

    Results of http://<fog_server_ip>/fog/service/ipxe/boot.php:

    #!ipxe
    set fog-ip 192.168.1.200
    set fog-webroot fog
    set boot-url http://${fog-ip}/${fog-webroot}
    cpuid --ext 29 && set arch x86_64 || set arch i386
    goto get_console
    :console_set
    colour --rgb 0x00567a 1 ||
    colour --rgb 0x00567a 2 ||
    colour --rgb 0x00567a 4 ||
    cpair --foreground 7 --background 2 2 ||
    goto MENU
    :alt_console
    cpair --background 0 1 ||
    cpair --background 1 2 ||
    goto MENU
    :get_console
    console --picture http://192.168.1.200/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
    :MENU
    menu
    colour --rgb 0xff0000 0 ||
    cpair --foreground 1 1 ||
    cpair --foreground 0 3 ||
    cpair --foreground 4 4 ||
    item --gap Host is NOT registered!
    item --gap -- -------------------------------------
    item fog.local Boot from hard disk
    item fog.memtest Run Memtest86+
    item fog.reginput Perform Full Host Registration and Inventory
    item fog.reg Quick Registration and Inventory
    item fog.deployimage Deploy Image
    item fog.multijoin Join Multicast Session
    item fog.sysinfo Client System Information (Compatibility)
    choose --default fog.local --timeout 3000 target && goto ${target}
    :fog.local
    sanboot --no-describe --drive 0x80 || goto MENU
    :fog.memtest
    kernel memdisk initrd=memtest.bin iso raw
    initrd memtest.bin
    boot || goto MENU
    :fog.reginput
    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.1.200/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.1.200:/images/ storageip=192.168.1.200 loglevel=4 mode=manreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.reg
    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.1.200/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.1.200:/images/ storageip=192.168.1.200 loglevel=4 mode=autoreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.deployimage
    login
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username ${username}
    param password ${password}
    param qihost 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    param sysuuid ${uuid}
    :fog.multijoin
    login
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username ${username}
    param password ${password}
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    param sysuuid ${uuid}
    :fog.sysinfo
    kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.1.200/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.1.200:/images/ storageip=192.168.1.200 loglevel=4 mode=sysinfo
    imgfetch init_32.xz
    boot || goto MENU
    :bootme
    chain -ar http://192.168.1.200/fog/service/ipxe/boot.php##params ||
    goto MENU
    autoboot
    

  • Moderator

    What do you have configured for dhcp option 67?

    That error almost sounds like an iPXE error and not a uefi boot loader error. If you could take a picture of the error with a mobile phone and post it here we can see the context of the error.

    Also what version of fog are you using?

    Finally, if you could call this url, replacing the <fog_ip_address> with the real IP address of your fog server we can see the text behind the iPXE menu. http://<fog_server_ip>/fog/service/ipxe/boot.php paste the results in this thread.


Log in to reply
 

354
Online

6.8k
Users

14.1k
Topics

133.3k
Posts