Stuck at bzImage after selecting image to deploy
-
Hi,
We got the new HP Elitebook 840 G6 with m2 drives, they were working just fine before. But I recently received a new batch (same exact model as others), and they get stuck at bzImage. I went ahead and updated Fog server to 1.5.8.24 but the issue still persists.
See screenshot here
What is odd, if I try to register it, it gets stuck at int.xz
There was a fix I read in previous threads where to try different bzImage/int.xz files. Was wondering if there was maybe an updated one. See screenshot of what I used in the past for laptops that caused me issues.
-
@robbit @Sebastian-Roth I have experienced the same issue with the same laptop. Running FOG 1.5.9. Until now, we have a mix of UEFI and BIOS computers with a huge variety of brands, form factors, and NICs that have had no problems imaging with FOG. Our Windows DHCP server with appropriate scope policies hands out the proper boot file and imaging just happens. With this model, it was taking 50 minutes (on a network with a 10G backbone and 1G to the endpoint) just to download bzImage. I tried the NVME fixes and the alternative init.xz files, but that did nothing. However, creating a DHCP scope policy (based on MAC address, as I only have one of these machines) that handed out snponly.efi as the boot file for this machine (instead of ipxe.efi) completely and immediately solved this issue for me. Just wanted to post this, as I came across this unsolved thread in my attempts to find a solution. Hopefully it can help someone else.
-
@robbit said in Stuck at bzImage after selecting image to deploy:
But I recently received a new batch (same exact model as others), and they get stuck at bzImage.
Please check BIOS/UEFI firmware version. Are those exactly the same as well?
What is odd, if I try to register it, it gets stuck at int.xz
Do you really mean init.xz here? Above you say stuck on bzImage. Not sure if that makes a difference but I just want to make sure we talk about the same things here. So is it all stuck at the same spot that we see in the picture with
bzImage ........but not showinginit.xz .....?There was a fix I read in previous threads where to try different bzImage/int.xz files. Was wondering if there was maybe an updated one. See screenshot of what I used in the past for laptops that caused me issues.
As far as I remember those were mostly used/tried because of slow speed issues with NVMe drives, so way past the issue you seem to see here. Using different kernel or init as see in the screenshot (e.g.
bzImage-4.9.51) should not play a role in the issue you describe here (unless the files might be missing) because iPXE should be downloading the kernel/init but has not yet finished to actually execute the kernel and go on with it.So if what we see on the picture is really where it’s stuck I am wondering if it’s some kind of network issue (NIC driver in iPXE, different NIC driver in UEFI firmware, …?) when loading larger files. Loading text content from boot.php seems to work perfectly fine but not larger ones as kernel/init?!
This is all based on what we see in the picture. If that’s not where it hangs, then I may ask you to capture a video of the boot process.
-
@Sebastian-Roth said in Stuck at bzImage after selecting image to deploy:
Please check BIOS/UEFI firmware version. Are those exactly the same as well?
I will check once we’re back in the office. As you may have guessed, we’re all WFH now and our fog server is back in the office so might be some time before I have a chance to test again. I will try updating to latest BIOS and try again.
Do you really mean init.xz here? Above you say stuck on bzImage. Not sure if that makes a difference but I just want to make sure we talk about the same things here. So is it all stuck at the same spot that we see in the picture with
bzImage ........but not showinginit.xz .....?Wopos, I do mean init.xz. I didn’t take a screenshot of it but after booting into PXE, when I try to do the “quick register” option, then it gets stuck at init.xz
But for now, I guess we’re sort of stuck until I find a chance to visit the office to test.
-
@robbit Any news on this?
-
@robbit Are you still WFH?
-
@robbit @Sebastian-Roth I have experienced the same issue with the same laptop. Running FOG 1.5.9. Until now, we have a mix of UEFI and BIOS computers with a huge variety of brands, form factors, and NICs that have had no problems imaging with FOG. Our Windows DHCP server with appropriate scope policies hands out the proper boot file and imaging just happens. With this model, it was taking 50 minutes (on a network with a 10G backbone and 1G to the endpoint) just to download bzImage. I tried the NVME fixes and the alternative init.xz files, but that did nothing. However, creating a DHCP scope policy (based on MAC address, as I only have one of these machines) that handed out snponly.efi as the boot file for this machine (instead of ipxe.efi) completely and immediately solved this issue for me. Just wanted to post this, as I came across this unsolved thread in my attempts to find a solution. Hopefully it can help someone else.
-
@chipdewolfe Great! Thanks for sharing this here.
-
@chipdewolfe said in Stuck at bzImage after selecting image to deploy:
snponly.efi
I’m having exactly the same issue, I’ve tried all the .efi boot files and get the following results.
ipxe.efi -> Configuring (net0 xx:xx:xx:xx:xx:xx) … No configuration methods succeeded
snponly.efi and snp.efi -> show the boot menu, but hangs showing bzImage… 0%
intel.efi and intel7156 -> DHCP failed
Version 1.5.9
Any advice?
-
@Rig @chipdewolfe Seems like you both use the same version of FOG, so same iPXE version. So what I can think of making the difference is the firmware version. Have you all updated to the very latest firmware?
-
@chipdewolfe hi, can you tell me what you mean by create a dhcp scope policy?
-
-
@sebastian-roth hi, im using a UDM pro from Ubitiqui as DHCP so that doesnt help…i have a laptop and only boots with snponly.efi…but stuck in bzimage at deployment. Dont know what else to do
-
@kvothe88 said in Stuck at bzImage after selecting image to deploy:
hi, im using a UDM pro from Ubitiqui as DHCP so that doesnt help…i have a laptop and only boots with snponly.efi…but stuck in bzimage at deployment. Dont know what else to do
Well from your first message this sounded fairly different. Something about policy…
In this case I suggest you open a new topic in the forums so we don’t cause unneeded confusion. Post a picture of the screen where it is stuck along with information on yor FOG version, kernel version and the exact make and model of the device you see this issue on. We’ll take it from there.