Hi @Sebastian-Roth

That fixed it Thanks for your and Tom’s assistance.

@Sebastian-Roth Ok here is a video of the original machine that was imaged showing when it tries to boot from pxe. I have been unable to get the video from a machine that has had this image deployed to it as they are busy being used in training at the moment but the video below is pretty much what happens to them as well. Its odd because the pxe boot that is used to copy the image to the server works without problems.

https://drive.google.com/open?id=1Jd41t2JMfF-fT-_s9gu9x3Pz7kPnwaPV

This is what it looks like if the hard disk is the first boot device. On the machines that have had the image deployed, they just end up pxe booting. Will try and see about adding a uefi entry once the training is over.

https://drive.google.com/file/d/1-raEQt-t6j5ziMqJV7s-M1LCbQk6JAeD/view?usp=sharing

Sorry had to use links due to file size limit. I might be the boot option as you suggested so will play around with that when we get the time and check the uefi entry.

thanks @Sebastian-Roth will do a video capture and test the machines tomorrow. I will try changing the exit options to test the result too. I did change those setting from the default so maybe that is the issue. Although when the image was deployed to a different type of hardware device it didn’t give any issues. UEFI definitely sounds like it could be an issue in this scenario.

Hi all,

We have some oldish Jetway Mini-Top 700 that support uefi, if its relevant. We imaged one of these devices installed with Ubuntu 18.04. Upon reboot of the machine that was imaged, PXE boot is first tried, and instead of successfully booting from the hard disk we get the following:

launching grub
begin pxe scan
start cmain()

And the device hangs. We can turn off pxe boot in the bios and the device that was imaged can then boot without issue. However any machine who has the image of this device deployed hangs at the grub prompt even if we turn pxe boot off in the bios. It seems to completely ignore the bios setting.

We tried reinstall grub off a live ubs on the deloyed machines figuring it was easier than trying to reinstall them but no matter what we tried the grub prompt hangs. It looks like the devices are still getting hte pxe image from fog and trying to boo the hard disk but failing. As stated they shouldn’t even try network boot as we turned it off in the bios. Very odd.

Any ideas?

I know this is going to sound weird but the Linux KVM image started failing to find the tftp server as well. Once I set up tcpdump to investigate on the fog server it all started working.

I tried the same with the windows image and now its working too. Only straw I can cluck at here is latency of some kind in the vm network layer. Maybe by delaying the boot up it gave the dhcp server time to respond?

Will see what I experience going forward and try and build up a conceptual model of what is going on so I can test and verify.

Hi @Sebastian-Roth

That fixed it Thanks for your and Tom’s assistance.

Hi @Tom-Elliott

Sorry, I mentioned it on the other post. I should have put it here too. It was version 6557 but I have since upgraded to fix the white screen of death bug. I am not at the office now so can’t get the exact version but it was less than 3 hours ago that I did a git pull.

regards

Hi @Tom-Elliott

Just to let you know I tried to upload a non-resizable image and it too failed after the upload on the “Update database” step as well. I couldn’t see anything in the mysql log files.

Maybe one of my tables is corrupted?

cheers

Hi @Sebastian-Roth,

I think I was wrong in my understanding that the Ubuntu instance times out. I have been trying so many things while also doing a full days work I get a bit lost

Will do the wireshark dump tomorrow.

kind regards

Hi @george1421

The F12 is the option that SEABIOS uses to allow one to interrupt the boot process to choose which device to boot. It can be configured to boot straight into PXE mode if desired.

I think I may have been mistaken on the need to push F8. The F8 settings come from my dnsmasq configuration file. I am not sure if its needed but it was added a year ago to get things working so its just been left there.

So in short the Ubuntu PXE boot in the vm works fine.

The windows vm is on the same infrastructure. It appears never to download anything from the tftp server. I will run a tcpdump on the tftp server tomorrow and see what gives.

Thanks for the help.

@Tom-Elliott I didn’t have my cell phone with me but the upload fails on the reboot when it i says it is resetting the partition sizes. It fails saying

“Updating data - Failed” or something like that. Basically it looks like it fails trying to update the db after a successful upload and resize?

Will bring my phone tomorrow.