Chainloading Failed
-
I have a couple of computers that say chainloading failed, hit"s" for the iPXE shell and then it shuts the computer off and then loops. I have installed the lasted version and kernel update. Any help when be gladly appreciated.
Thanks
-
Well lets start with
-
What version of fog are you using?
-
What are you doing when you get this chain loading fails?
-
-
I am using 1.4.4. You can hit escape to bypass. Or I have went to my Active Directory setting and taken that off DHCP boot order.
-
@ntalbert From what you say it sounds as if some machines PXE boot fine but others don’t, right? So what do those that don’t, have in common? Are those setup as UEFI?
Usually there is a more detailed error message before the “chainloading failed, hit…” one. Please take a picture of the error and post here!
-
This post is deleted! -
@sebastian-roth Sorry it has taken so long to get back. Here are the images
-
@ntalbert Please try connecting one of the problematic computers to a different switch port where you don’t see the issue. Does it still occur then?
Edit: Ahhh, wait a second, in the picture I see client IP 10.10.20.x but it tries to load the iPXE config from 192.168.1.1, so totally different subnet. Did you change the FOG server IP at some point? Do you have just one node or storage nodes too?
-
@sebastian-roth I dont remember changing the server ip address but it should 10.10.150.54. That is the network ip address for fog and also for the web gui. Currently just one node. How can I change the iPxe config?
-
@ntalbert Please search the forum. There are a couple great posts by George and Wayne on how to change the IP. Just to make sure you have it all right.
But my Guss is you have another DHCP server or proxy in your network that is causing the issue. Are server and clients all in one subnet or spread across subnets? What server does provide the DHCP service? Windows Server, Cisco Router, … ?
-
@ntalbert If your fog server, dhcp server and pxe booting client are on the same subnet please try to do this: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
I suspect you have a second dhcp server or proxy dhcp server on your network issuing IP addresses. Upload the pcap file to a google drive and post the link here or IM either Sebastian or myself and we will take a look at it.
The confusing bit is that according to the picture iPXE is getting to the target computer some how, and then getting the wrong IP address when it requeries for the next server. As well as why is it using tftp to get default.ipxe? At this point it should be using http. Are you trying to boot a virtual box vm in the pictures? Virtual box uses iPXE as its boot roms. One last bit, I’ve seen many home routers send its IP address out as a next server for some reason and the ip address of 192.168.1.1 makes me thing someone might have plugged in a home internet router into your network as a rouge device.
-
@sebastian-roth Thank You!! Thank You!!! I have resolved the issue with that tip.
-
@ntalbert Please be so kind and tell us what exactly caused the issue and how you solved it. This is an open source community and this is build on sharing pretty much everything including solutions to locally caused issues as other might have same or similar problems…
