chainloading failed hit s for the ipxe shell
-
I am running Fog 1.5.8 on Debian 9 its a fresh install with fog as my DHCP server I was able to upload a Windows 10 image but when I try and deploy it on a Lenovo desktop I get the following error “chainloading failed hit “s” for the ipxe shell”. and it restarts and goes into a loop, anyone have any ideas?
-
Did you capture your golden image from a lenovo desktop or is this the first time you are deploying to a physical machine?
If you setup a test image capture to this machine do you get the same chainloading error?
If you run the FOG hardware compatibility test from the iPXE menu, what are your results.
-
This is the first time I am loading it on the machine I created it from a VM not from the Lenovo. I can try and load it to another VM and see what happens. I did run the comparability test and it ran just fine.
-
I tried it on a VM image and I get the same error.
-
@kstrout said in chainloading failed hit s for the ipxe shell:
I did run the comparability test and it ran just fine.
This is really strange because the error “chainloading failed” does happen before you can do the comparability test. So I don’t understand why it would boot to the iPXE menu and the test but would not start a deploy task. That doesn’t make sense to me. Would you be able to take a video of the boot process when a task is scheduled for the Lenovo machine and the error comes up?
-
-
@kstrout Thanks for posting the video! What we see here is that the iPXE FOG menu is set to be hidden and therefore it seems to use the default menu item - chainloading from the local hard drive instead of showing the menu.
Now if you schedule a deploy task for this particular client I am fairly sure it will actually do the deployment. If you think you have scheduled a deploy task for this host already, then take a look at the Active Tasks list to check.
-
@Sebastian-Roth I did a deploy the problem is when the deploy is over this is what I get it never boots to the hard drive with the image on it. It just keeps looping after the image is deployed.
-
@kstrout Well then check out the EXIT TYPE setting for this host. Play with the different settings.
Some particular hardware has issues with chainloading to disk. Please let us know which Lenovo desktop you actually have. Chances are good other users in the forum have the same hardware and can share their knowledge on this.
As well we need to know if the Lenovo is set to UEFI or legacy BIOS?
-
@Sebastian-Roth The Lenovo is a think Center M710s and it is running auto (legacy first)
-
It is working now so with Bios set to Auto (legacy First) and the exit mode set to GRUB_FIRST_HDD it boots!!! I tried it with UEFI and it didn’t work which is why I went to auto.
Thanks for the help I appreciate it!
