@mcana66 Well I want to thank you again BrakCountry. Although the solution you posed did not work, you got me delving into the scripts to figure this out on my own. Took a while but here is what I did to fix my issue of the reboot loop in the FOG menu.

First I started playing with chain boot and replaced the initial chain statement with the one below:

chain https://(Fog-IP)/fog/service/ipxe/refind.efi

This booted directly into refind.efi and booted the first hdd. So I got the thought of how many items can you chain boot?

I kicked off a job to image my target and added that chain statement to the bottom of default.ipxe because hey why not. lol. After FOG completed imaging the target, the machine performed a normal reboot and booted to boot.php##params however and I am only guessing, there were no jobs present in FOG so when the menu appeared, “Boot from HDD” was the default selection and then chain booted to the refind.efi which booted the os on the HDD.

Again thank you to all who tried to offer help or advice!!

@mcana66 Well I want to thank you again BrakCountry. Although the solution you posed did not work, you got me delving into the scripts to figure this out on my own. Took a while but here is what I did to fix my issue of the reboot loop in the FOG menu.

First I started playing with chain boot and replaced the initial chain statement with the one below:

chain https://(Fog-IP)/fog/service/ipxe/refind.efi

This booted directly into refind.efi and booted the first hdd. So I got the thought of how many items can you chain boot?

I kicked off a job to image my target and added that chain statement to the bottom of default.ipxe because hey why not. lol. After FOG completed imaging the target, the machine performed a normal reboot and booted to boot.php##params however and I am only guessing, there were no jobs present in FOG so when the menu appeared, “Boot from HDD” was the default selection and then chain booted to the refind.efi which booted the os on the HDD.

Again thank you to all who tried to offer help or advice!!

@brakcounty Very Nice! I am going to give that a try! Thank you.

@george1421

So I was under the impression (possibly wrong) that refind would pass the boot to continue the EFI/BIOS boot order if there was no PXE job available. I was confused since the target machine picked up PXE and processed a tftpboot even though no job was pending. I was spoiled many years ago using Altiris where the server would boot through PXE if no job was pending, so Fog is new to me but I suppose the concepts are still the same.

That you have a fix for exit is awesome and I will be applying that at the next chance I get! Thanks!!

@george1421

Thank you. So I had tried all of the options and that was just what I last had selected. REFIND did not work either. I am using 1.5.9 and “sniff, sniff” exit mode has a problem is not a happy answer. Is there anyway to help the Devs with the problem? I’m happy to help testing!

Or alternatively is there a previously working version that I can download?

@brakcounty

Thanks for the reply. So if autoexec.ipxe is the default, where can I find or create that script. I’ve been doing a lot of searches but I haven’t really seen anything pointing me to “download and edit this”. More developers talking about embedding their own options.

Hello All, Hoping I’m posting this in the right spot and providing as much info as I can think of. So I have 2 machines on their own tiny subnet for testing, an Intel NUC running ubuntu 20.04 (fog host) and an Asus based motherboard with UEFI PXE running as the 1st boot option. I am able to reliably image the Asus machine but cannot get the machine to boot through the PXE menu to the next boot option. DNS & DHCP are running on the fog server btw.

Ubuntu Server 20.04 (UEFI) registered for Asus client but no job specified
EFI Boot Exit - Refind_efi

iPXE Boots
received dhcp answer on interface net2
tftp://<fog ip>/default.ipxe
tftp://<fog ip>/fog/service/ipxe/boot.php
tftp://<fog ip>/fog/service/ipxe/grub.exe
Could not boot: exec format error (https://ipxe.org/2e008081)

When I do a pcap the “could not boot” error line is looking for autoexec.ipxe which I do not have on my machine.

No job being pushed but client (Asus) is registered with an image in fog. So I guess my real question should be, why is iPXE booting and starting TFTP if there is no job to be pushed? Is autoexec.ipxe a needed component to continue the boot process? I appreciate any help or questions for info I did not specify in advance.