Same Model Same Settings Different Results
-
I have a new issue. I have 10 of the exact same model of computer Lenovo Thinkpad E15, Gen3. All new out of the box. I seem to get different results with each computer.
All have the same BIOS settings as a computer that successfully boots to PXE and gets to the FOG server. I’m using the same network cable in my office for all of them. I just unplug and try it on the different machines.-one of them goes to Starting PXE over IPV4 and hangs there with no additional text or messages and goes back to boot options after about a minute.
-another starts over PXE then gives the error: pxe-e16 no valid offer received -
@cwentwo OK, so lets make sure I got this right.
You can get into the fog ipxe menu with every other model of computers except the Thinkpad E15, Gen3? Or is it just these 10 Thinkpad E15’s and other E15’s work as expected.
If its specifically the E15 models that won’t pxe boot then
- Do you have secureboot disabled on these computers?
- Are these computers in bios or uefi mode? Is this different than other computers that are working?
-
@george1421
I’ve tested it with 5 of these so far. I can get 2 of them to see the FOG server through PXE. One was the machine I prepped for imaging the other was new and had not yet been started up.- Secure boot was disabled. (That was the setting holding me back on the other 2 that now work.)
- I don’t totally understand this, but I believe it is in UEFI. I do have older computers that I have tested just to make sure things were working and they connect without a problem.
-
@cwentwo Ok so question 2 was geared towards ensuring you have dynamic dhcp setup for pxe booting. uefi computers need ipxe.efi in dhcp option 67 and undionly,kpxe for bios based computers. Since you mentioned these are new computers, I don’t know if these are the first uefi based computers on your campus or what else.
So its not clear if its the model or something unique with the system. I’m going to have to say since others of the same exact model are being a bit random its something unique with the specific computer.
So I want you to go in and ensure these computers are on the latest firmware (bios version) and then do a factory firmware reset on one that doesn’t work (again make sure that secure boot is disabled). Make sure they are in uefi mode.
If this doesn’t work, lets place a dumb/cheap-o/unmanaged network switch between these computers and the business network switch. Lets see if this masks the issue.
-
@george1421
Thank you for your help with this. Please forgive me as this is all new to me so I may be misspeaking.
Option 67 is set to ipxe.efi.
They do have the latest firmware. R1OET31W (1.10)
I have not found in this BIOS version a way to switch to or from UEFI mode. Is it possible it is just always in UEFI?
I have tried a USB-C dock, a USB 3.0 ethernet adapter, and a 5 port switch all with the same result. It goes to the black screen that says “Start PXE over IPV4” waits there for 10-15 seconds then goes back to the boot options. On the ones that work it shows the IP address then continues. -
@cwentwo said in Same Model Same Settings Different Results:
black screen that says “Start PXE over IPV4” waits there for 10-15 seconds then goes back to the boot options
Secure boot turned on will do this. I’m not saying its your problem, but this is an indication that secure boot rejected the ipxe.efi file.
OK so lets dig a bit more into the problem. First please answer if the fog server and these non-pxe booting computers on the same IP subnet? The answer will give us a path to find the solution.
-
@george1421 I’ve double and triple checked that secure boot is off.
Yes, I booted one to Windows and ran ipconfig and confirmed that it was in the same subnet as the FOG server.
-
@cwentwo Ok great on the single subnet.
I have a tutorial here on using the FOG server to capture the pxe boot information. On this system that fails to pxe boot follow this tutorial on how to setup the packet capture. Upload the captured file to a file share site with public read with the link and then either post the link here or DM me the link using FOG chat. I’ll take a look at the pcap to see what the client isn’t being told correctly.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
The filter used will specifically only collect the pxe booting process and nothing else. The total packet count of a healthy PXE boot is about 8 packets captured.
