@jherron Great to hear you figured it out. Well done!

I was going to setup a test scenario to see if I can replicate the issue. But would have been very hard to figure out not knowing that you use the location plugin.

@george1421 Ah ok so if im imaging without registering then location doesnt really do what i need in this case. Thanks though.

@george1421 Target is UEFI, image was captured in Legacy VM. Will try again with VM in UEFI mode

@sebastian-roth
That’s true, but every time I upgraded either fog or the OS, something would break. I used to have the advantage of Tom Elliott being available to assist in these cases, but he never returns emails or phone calls from me in like nearly 2 years.

@robertkwild yes, it can.

@austinjt01 said in Lenovo P52 - Stuck on iPXE 1.20.1:

Yes still stuck at the handoff to FOS.

One option you can try is to compile the latest version of iPXE. There has been some updates to iPXE since 1.5.9 has been released. There may be some value in trying the process outlined by Sebastian here: https://forums.fogproject.org/post/141618

You will need the github version of the fog installer to follow these steps.

@Tom-Elliott can you get me curl command or minimal list json params to create image in fog ?
Thanks

@sebastian-roth Thanks, we gave that a go and now there is an error with the chainloading failing. So progress from denied.

Researching the error on ipxe (3e11623b) the error seems to be based on the lack of a DNS server. Currently these custom certs don’t have the IP address of the fog server as part of the certificate SAN, so we’re going to see if a certificate with the SAN containing the IP and hostname resolves this error.

@tallier Vous devez rechercher des messages d’erreur plus détaillés sur le serveur et le client.
Vérifiez que /images est correctement monté sur le serveur.
Vérifiez si vous pouvez monter /images à partir d’un autre ordinateur.
Assurez-vous que les services NFS sont démarrés avec toutes les dépendances.

@trev-lchs now to test refind lol

@chris_unit said in move to Fog Pxe menu:

Is the directory /images/ shared out over http ?

No its not the docbase for http on ubuntu is /var/www/ I believe. So your os/ubuntu/Desk... path should start form there.

I would also confirm with a browser that you can reference the url to get the iso. That will tell you its working before you attempt to pxe boot.

@sebastian-roth Yup its was, “Is Graph Enabled (On Dashboard)” Working now. thanks.

@tesparza Search the forums for both topics. There are numerous posts on both.

@george1421

Hi Thanks for this informations, I maked the change but do you know if we can bypass the “press any key to continue” in rEFInd?

Thanks for your help

@yeet said in Error with UEFI:

Just two points to clarify here.

I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

snponly.efi for uefi is roughly equivalent to what undionly.kpxe is to bios. Both of these ipxe boot loaders use the network adapter’s built in firmware driver. For bios, the undi firmware interface is very mature and stable. For uefi the snp firmware interface has been historically very flaky until the last few years where it has matured a bit and become more stable. For both the undi and snp firmware drivers, its up to the nic manufacturer to make sure the firmware driver conforms to the strict standards. This doesn’t always happen.

Now ipxe.kpxe is to bios what ipxe.efi is to uefi. In the case of these boot loaders these are more like a linux kernel than not. These boot loaders have one of every known driver installed. The complete network and disk drivers are part of this boot loader kernel. The benefits are that ipxe has a very stable and known network and disk controller communication. The down side is that its sometimes difficult to keep up with emerging hardware. That is where undi and snp firmware drivers have helped since they are created by the hardware manufacturer when the new hardware is released. If the developers find that many people are having success with the snponly.efi drivers, they may change their default recommendations.

If that doesn’t work, I’d recommend updating the kernel version.

Don’t confuse the ipxe menu and the boot loader from the FOS Linux kernel. They are two different systems that work together. iPXE gets you to the FOG menu on the target computer. Once you select a menu item and bzImage is loaded then its FOS linux in charge. If you are having network issues and don’t get to the FOG iPXE menu then its a ipxe boot loader issue, if you get to the menu but when you select a menu item then see a network issue then its FOS Linux with the problem. I said all of that to say, if iPXE will not initalize then updating your {FOS Linux} kernel will not help you.

@sebastian-roth
indeed, I switched the fog server on the same network it works now
thank you

https://www.stellarinfo.com/article/repair-mysql-database-table.php