PXE boot problem after setup
-
I’m running my server in a master congiruation on Centos 7. I followed the guide in the wiki, and everything went great.
I changed my DHCP (windows 2008 server) server to reflect the option 66 and 67, and tried to boot my first PC via PXE to register it with FOG, however this is what happens.
Upon trying to boot to PXE, i get the following message :
Downloading NBP File : NBP File Downloaded succesfully Downloading DBP File : NBP File Downloaded succesfully.After that runs two times (its in the blink of an eye) the laptop reverts back to its boot menu. Any help is appreciated.
-
@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!
-
Further Clarification. The laptop model I am trying to PXE is a Toshiba TECRA A50-D, fairly new.
I WAS able to successfully boot a desktop sitting next to me and register it. I don’t know why i cant get this laptop to do the same. Any help is appreciated.
-
@tneuber Does the other one show the exact same messages on screen “Downloading NBP File …”?? I am asking because the boot sequence is kind of different if it is set to legacy BIOS boot or modern UEFI boot. Other than that I think it could be different firmware versions causing this. Please see if both have the exact same BIOS/firmware installed.
-
@sebastian-roth They are both different TYPES of computers alone.
One is a Toshiba Tecra A50-D laptop, the other is an HP Elitedesk 800 G3. The 800 G3 did the pxe fine, however ALL of my Tecra A50-d laptops are not booting to BXE (I have about 30 of them, and I tried two of them).
They all show the message above when trying to PXE boot. I’ll take any suggestions you might have. Even If i have to go into bios to update something on the laptops to make it work.
-
@tneuber What do you have configured for dhcp option 67 {boot-file}?
-
@tneuber said in PXE boot problem after setup:
They are both different TYPES of computers alone.
Well then I am not at all surprised they do behave different. That’s how things are. Different vendors have different firmware implementations (supplied by external companies!) and there is now way you can tell that if one is working another different model will just play nicely as well.
One is a Toshiba Tecra A50-D laptop, the other is an HP Elitedesk 800 G3. The 800 G3 did the pxe fine, however ALL of my Tecra A50-d laptops are not booting to BXE (I have about 30 of them, and I tried two of them).
They all show the message above when trying to PXE boot. I’ll take any suggestions you might have. Even If i have to go into bios to update something on the laptops to make it work.If all the Toshiba A50-D’s don’t PXE boot it’s something to do with that model. Some have crappy firmware implementation which you can’t do much about. We have spent months trying to figure out such an error with some HP devices, even talked to HP people and the firmware developers. They sent us a fixed firmware but never officially released it. That’s just one story and it might be very different in your case. Just wanted to warn you, this is most likely not something FOG is doing wrong and it might be a long endeavor to figure out.
So let’s start from the beginning. Is secure boot disabled on the Toshiba devices?
-
@sebastian-roth Inside the BIOS for the Toshiba’s I have Secure Boot disabled yes.
I Called Toshiba to see if there is an updated firmware available for this problem. I Agree this wouldn’t be an issue with FOG necessarily, however I feel that, given the knowledge most people had here on this forum, it might be the best place to ask.
-
@tneuber Are you keen to get into the details of this? You can compile your own iPXE binaries with debug enabled. Read the last two dozen messages of this forum thread to see if you wanna give it a try: https://forums.fogproject.org/topic/11348/hyper-v-and-pxe-boot-to-fog-problems
-
@sebastian-roth The issue was changing the LAN boot selection from UEFI to CSM Boot. Thanks all!
