Hello, I am seeing an interesting issue with hosts that have more than 2 network interfaces when attempting to deploy images. This is only happening with UEFI based machines. I am able to reproduce this on physical and virtual machines with 3 or more NICs attached. Reducing the NIC count to 2 eliminates this issue.

I have edited the fog.deployimage menu item to include the users credentials. This works with BIOS machines and UEFI machines with less than 2 NICs. But in a UEFI machine with more than 2 NICs when I select ‘Deploy Image’ I am prompted for the FOG users credentials. After entering the credentials the ‘Client System Information’ item runs for some reason.

I attempted to resolve this by adding the following to the fog.deployimage parameters:

isset ${net3/mac} && param mac3 ${net3/mac} || goto bootme
isset ${net4/mac} && param mac4 ${net4/mac} || goto bootme

I verified that these settings were applied by checking this page:
http://<fogIP>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00

Now, when I PXE boot to FOG, select ‘Deploy Image’ from the menu, then select any image I am immediately returned to the FOG main menu.
The same behavior is observed when selecting ‘Boot from Hard Disk’, the FOG menu is simply refreshed.

I think I might need to edit another script somewhere to look for more than 2 NICs.
My best guess is editing this function in functions.sh to include net3 and net4.

configureDefaultiPXEfile() {
    [[ -z $webroot ]] && webroot='/'
	echo -e "#!ipxe\ncpuid --ext 29 && set arch x86_64 || set arch \${buildarch}\nparams\nparam mac0 \${net0/mac}\nparam arch \${arch}\nparam platform \${platform}\nparam product \${product}\nparam manufacturer \${product}\nparam ipxever \${version}\nparam filename \${filename}\nparam sysuuid \${uuid}\nisset \${net1/mac} && param mac1 \${net1/mac} || goto bootme\nisset \${net2/mac} && param mac2 \${net2/mac} || goto bootme\n:bootme\nchain ${httpproto}://$ipaddress${webroot}service/ipxe/boot.php##params" > "$tftpdirdst/default.ipxe"
}

Has anyone run into this behavior before? Thanks

@george1421 I think I may have found a workaround, I’m not sure what ill-effects it may have yet.

While testing the CentOS image on a physical host I noticed it was able to boot fine using grubx64.efi
This file is located at /boot/efi/EFI/centos on my machine

In the refind.conf file I added two lines:

also_scan_dirs /boot/efi/EFI/centos
dont_scan_files mmx64.efi,MokManager.efi,shim.efi,shimx64-centos.efi,shimx64.efi

Basically these two lines say, also search the centos folder for boot files and ignore every .efi file listed above.

I’ll run with this configuration and update if I come across any issues.

@george1421 Thank you, I appreciate it. Let me know if you need any other configuration information

@george1421
Gotcha, I removed the menu entry and added this line instead:

also_scan_dirs /boot/efi/EFI/BOOT

I verified that the change I made to the file was saved by navigating to: http://<FOG_IP>/fog/service/ipxe/refind.conf

The behavior is still the same, CentOS is still failing to exit the FOG menu properly.

@george1421
I added this block to refind.conf and rebooted the FOG server but it did not change the behavior.

menuentry CentOS {
    loader /boot/efi/EFI/BOOT/BOOTX64.EFI
    enabled
}

I copied the BOOTX64.EFI file to /boot/efi/ but that didn’t change anything either.

@george1421
I believe it is a standard boot layout. When installing the OS I selected ‘Standard Partion’ instead of using LVM. I then just left the defaults for /boot, /boot/efi, /, and swap

bootx64.efi is not at that location, I found it here: /boot/efi/EFI/BOOT/BOOTX64.EFI

I checked the Fedora system that is working correctly. BOOTX64.EFI is in the same location as on the CentOS machine.

I am having an issue with my CentOS7 image. After deploying to a host I see the following:
The host boots into FOG
The menu timer counts down to 0
Then this screen is displayed:

After this timer reaches zero the computer reboots and starts the sequence over.

The CentOS image was created on a Hyper-V Gen2 VM with secure boot disabled. I used the following partition layout:

Standard Partition

• /boot - xfs 1024MiB
• /boot/efi - EFI 200MiB
• / - xfs 16.8GiB*
• swap - swap 2GiB

I see the same behavior on both a VM and a physical machine.

If I escape out of PXE before it gets a DHCP address or disable PXE booting, the OS will boot up without a problem.

I have ‘Exit to Hard Drive Type(EFI)’ set to REFIND_EFI in the global settings. I also tried setting it for the registered hosts but this did not change anything.

The obvious workaround is to put the drive to the top of the boot order but for my implementation I need PXE to remain at the top.

I have also created a Fedora29 image using all the same settings as this CentOS image and it is able to exit the FOG menu and boot the OS fine.

Thanks