Unable to use FOG for PXE booting because of unresponsive menu

[george1421]

@quinniedid said in Unable to use FOG for PXE booting because of unresponsive menu:

Any ideas?

Lots of ideas, none to make me a million dollars overnight though…

What system are you trying to pxe boot?

Is this device in uefi mode or bios (legacy mode)?

What exactly do you have set for dhcp option 67 {boot-file}?

[quinniedid]

@george1421 This is the same PC’s that I have used before in the past to image, should be BIOS. For DHCP, I am using undionly.kpxe.

[george1421]

@quinniedid It would help if you posted a clear screen shot of the actual error taken with a mobile phone. The context of the error is almost as important as the actual error message.

My intuition is telling me that you are trying to send a bios boot kernel (undionly.kpxe) to a uefi system which is expecting ipxe.efi (or the other way around).

[quinniedid]

@george1421 Apologies for the vague details. The menu comes up now and is able to boot to the first hard drive. It was not able to do that till yesterday which you helped me with resolving. Now the issue is after I select Deploy Image and login, I do get a list of all the images. It is not until I select an image to deploy that this message comes up.

[george1421]

@quinniedid I’m getting the idea you have a botched install.

Looking at the screen shot I see bzImage (OS kernel) is transferred ok, but I don’t see init.zx (virtual hard drive) being sent to the target computer. They need to be passed in pairs.

I wonder if you are missing other values in the fog configuration page for the tftp server contains the correct info (specifically the *Image values)

[quinniedid]

@george1421 Here are the settings that are currently configured.

[george1421]

@quinniedid Has this computer been registered, or are you trying to register it right now?

If you are trying to register it, (stick with me here) manually register this host and then schedule an image capture or image deploy. It doesn’t matter we will not do either. Once the task is schedule, use the url I gave you before, this time use the mac address of the target computer and key that into a browser (you can leave the target computer off for this test). Post the results of the browser query here. As compared to the first time you did this setup, the results from this one should be very small about 5 or 6 lines long. I want to ensure what the client is being told to do.

Also can you confirm the target computer is in bios (legacy mode) and not uefi. If its in uefi mode you will need to disable secure boot and then change your ipxe boot kernel sent by dhcp option 67.

[quinniedid]

@george1421 Here is the results of a manual registration and deploy:

#!ipxe
set fog-ip 10.86.96.177
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.86.96.177/fog/ consoleblank=0 rootfstype=ext4 acpi=off mac=00:26:55:3f:14:45 ftp=10.86.96.177 storage=10.86.96.177:/images/ storageip=10.86.96.177 osid=9 irqpoll hostname=TEST-PC chkdsk=0 img=DISTWIN10 imgType=n imgPartitionType=all imgid=1 imgFormat=0 PIGZ_COMP=-9 hostearly=1 type=down acpi=off
imgfetch init_32.xz
boot

[Tom Elliott]

@george1421 Can you edit the TFTP_PXE_KERNEL_DIR so it reads as /var/www/html/fog/service/ipxe instead of /var/www/html/fogservice/ipxe (missing / between fog and service)

[Tom Elliott]

Also, please let’s make sure the links are all correct.

Would you mind doing:

mv /var/www/fog /var/www/fog_orig
mv /var/www/html/fog /var/www/html/fog_orig

Rerun the installer. This should help ensure the links are created/setup properly. It nearly sounds like it can’t find the right links.

For simplicity, run the installer with the -y argument so things will be more automated as the fact the tftp server settings were all blank leads me to think the installer wasn’t performed fully.

[george1421]

@Tom-Elliott I can/will/did, but how the hell did that / go missing and thing still work? Oh well I guess that is a discussion for another thread…

[quinniedid]

@Tom-Elliott @george1421 Moving those folders and running the installer again has resolved the issues. Thank you again!