FOG clients not PXE booting

[John L Clark]

I tried to upload a picture of the error but could not get it to load.
Basically it boots and gets the DHCP address and shows the gateway like

CLIENT MAC ADDR: 50 7B 9D C9 D8 GUID: 014B5B90 7554
CLIENT IP: 192.168.93.82 MASK: 255.255.255.0 DHCP IP:
GATEWAY IP: 192.168.93.254
TFTP.
PXE-MOF: Exiting Intel Boot Agent.

then it reboots

[george1421]

What version of FOG?

What hardware are you booting?

What mode is the target in UEFI/BIOS?

What boot file are you sending to the target computer (DHCP option 67)

Is this a new FOG install or one that has worked and you are just having an issue with this specific computer?

[John L Clark]

What version of FOG? 1.3.5 SVN 6067
What hardware are you booting? Lenovo
What mode is the target in UEFI/BIOS? legacy
What boot file are you sending to the target computer (DHCP option 67) undionly.kkpxe
Is this a new FOG install or one that has worked and you are just having an issue with this specific computer?

Existing fog install that was working fine until I tried to boot a new HP but backed up all files like the bzImage file and the init.xz and the init_32.xz

[george1421]

@John-L-Clark Hmmm you can pxe boot a different computer but this lenovo fails to transfer undionly.kpxe If you are sure you are transferring a bios boot loader it should boot.

What model lenovo?

[John L Clark]

@george1421 no none of our machines are booting. The test machine I am using is a E550

[george1421]

@John-L-Clark said in FOG clients not PXE booting:

no none of our machines are booting

Ok well that changes the scope a bit.

So is the target computers on the same subnet as the FOG server?

Have your confirmed that your dhcp server has dhcp option 66 pointing to the FOG server’s IP and dhcp option 67 set to undionly.kpxe?

What device is your dhcp server? (make and model)

[John L Clark]

@george1421 Yes the option is there it was all working fine before Yesterday.

I just tried a Yoga 11e and got a little different message.

CLIENT MAC ADDR: 50 7B 9D C9 D8 GUID: 014B5B90 7554
CLIENT IP: 192.168.93.82 MASK: 255.255.255.0 DHCP IP:
GATEWAY IP: 192.168.93.254

TFTP.
PXE–T01: File not found
PXE-E3b: TFTP Error -File not found
PXE-M0F: Exiting PXE ROM.

[george1421]

@John-L-Clark FOG server on same subnet as pxe booting client?

https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

[John L Clark]

@george1421 no it is on subnet 101 and every thing is here in Tech is on 93 so let me move a port to 101 and see if it will boot. Thanks

[John L Clark]

@george1421 That worked fine. So the other day it was not connecting to the internet for me to update the kernel. I had a coworker that is better with Linux than I am mess with the ip and he made it a static ip and static dns and I think he did something so I will work with him. Unless you have any suggestions? Thanks

[george1421]

@John-L-Clark When I worked at a foundry in the early 1980s they use to have the saying, if something broke look for forklift tracks. Meaning, you might want to ask whoever changed something or we are going to be hunting and pecking all afternoon. Just remember that FOG doesn’t like the IP address of the FOG server changing after FOG has been installed.

Also this goes without saying you should update FOG from 1.3.5 to the latest version to support the latest hardware. 1.3.5 is pretty old, I don’t think it supports nvme disks.

[John L Clark]

@george1421 Thank you lol, yeah the ips are still the same, we are working through it and will post the resolution.