@cjiwonder It may help if you tell us what model of PC you’re trying to boot. There may be a BIOS setup option that needs adjustment.

For example, my Dell 3430s’ BIOS setup requires the following boot options:

General -> Boot Sequence: Onboard NIC(IPV4) (checkmark to enable)
General -> Boot Sequence: UEFI (checkmark to enable)
AND “Onboard NIC(IPV4)” must be the first device in the boot sequence list

But I must also have the following options in different menu set:

System Configuration -> IntegratedNIC: Enable UEFI Network Stack
System Configuration -> IntegratedNIC: Enabled w/PXE

@cjiwonder said in UEFI is not booting with Windows DHCP:

@george1421 There is no error message, “>>Start PXE over IPv4” message and after a minute booting to HDD. Fog Server and PXE boot client are in the same VLAN but DHCP server is in a different VLAN. Tried with snponly.efi, intel.efi and pexe.efi but no luck. There is no issue with the DHCP IP release if I boot the PC in Windows, and there is no issue in booting with undionly.exe on the same PC. I am new to Wireshark, please guide me to run the capture filter. Thanks.

I just remembered that I had pretty much the same problem recently.

My problem was that the Ethernet link negotiation was taking too long on the Cisco 3850 switch I had the client connected to. The link negotiation took about 30 seconds and the IPXE wait for DHCP also took about 30 seconds, but always failed. This problem only happened for me when booting UEFI - worked fine booting BIOS / Legacy.

The solution for my case was to add this to the client port configuration on my Cisco switch:

spanning-tree portfast

@cjiwonder said in UEFI is not booting with Windows DHCP:

@george1421 There is no error message, “>>Start PXE over IPv4” message and after a minute booting to HDD. Fog Server and PXE boot client are in the same VLAN but DHCP server is in a different VLAN. Tried with snponly.efi, intel.efi and pexe.efi but no luck. There is no issue with the DHCP IP release if I boot the PC in Windows, and there is no issue in booting with undionly.exe on the same PC. I am new to Wireshark, please guide me to run the capture filter. Thanks.

I just remembered that I had pretty much the same problem recently.

My problem was that the Ethernet link negotiation was taking too long on the Cisco 3850 switch I had the client connected to. The link negotiation took about 30 seconds and the IPXE wait for DHCP also took about 30 seconds, but always failed. This problem only happened for me when booting UEFI - worked fine booting BIOS / Legacy.

The solution for my case was to add this to the client port configuration on my Cisco switch:

spanning-tree portfast

@Afif

It looks like you’re using the latest available FOG Linux kernel (6.12.35) for the client to boot.

It also looks like you’re using an Intel NUC and the kernel crash occurred while partclone was running.

Do you have any other information about the context that might be helpful?

My only suggestion at this point is to try booting the client to an older kernel. You can select a different kernel in the FOG web management GUI by:

(1) click FOG Configuration (wrench / spanner icon)
(2) Kernel Update
(3) select an appropriate older “AMD/Intel 64 Bit” kernel
(4) click “Download” for the selected kernel
(5) click “Install” at the “Save Kernel” page

You might start by verifying the actual stored image name on the storage node at 10.149.50.21:/images

Next you might use some SQL tool (I use phpMyAdmin) to check the ‘fog’ database on your FOG server, table ‘images’ and verify that the values for ‘imageName’ and ‘imagePath’ both look correct.

‘imageName’ could be different from ‘imagePath’, but only if someone has renamed the image in the FOG server web GUI. ‘imagePath’ should be the same as the desired image directory in your storage node(s) /images directory.

@cjiwonder It may help if you tell us what model of PC you’re trying to boot. There may be a BIOS setup option that needs adjustment.

For example, my Dell 3430s’ BIOS setup requires the following boot options:

General -> Boot Sequence: Onboard NIC(IPV4) (checkmark to enable)
General -> Boot Sequence: UEFI (checkmark to enable)
AND “Onboard NIC(IPV4)” must be the first device in the boot sequence list

But I must also have the following options in different menu set:

System Configuration -> IntegratedNIC: Enable UEFI Network Stack
System Configuration -> IntegratedNIC: Enabled w/PXE

@marcolefo Sounds like the package ‘build-essential’ should be an install target of the FOG install script? It doesn’t seem to be.

However I think my distro installs of Debian 12 and Mint 22.1 both installed that package by default.

Solved for me on Linux Mint 22.1

The base problem is that php-mysqlnd is a “virtual package” that is included in the package php-mysql, and trying to install it individually (as the FOG install script does) fails with apt dumping a list of php mysql versions and that “You should explicitly select one to install.” Even if php-mysql is already installed.

The solution for me was to remove php-mysqlnd as an install target in the FOG install scripts. As of this date, that includes:

In file [fog install pkg path]/lib/ubuntu/config.sh:

• remove ‘php-mysqlnd’ from line 26 "packages="apache2[…]

In the file [fog install pkg path]/lib/common/functions.sh:

• remove the lines

        php-mysql*)
            for phpmysql in $(echo php-mysqlnd php-mysql); do
                eval $packagelist "$phpmysql" >>$error_log 2>&1
                if [[ $? -eq 0 ]]; then
                    x=$phpmysql
                    break
                fi
            done
            ;;