I recently ran across this same issue, but it was not due to the fast spanning tree protocols. Our IT department added 802.1x authentication on the wired ports of all our switches, but the time out to fail back to MAC authentication was just longer than the 27 seconds @george1421 referenced in his post. We had a handful of hosts work, but a large majority failed. Our IT department had to shorten the 802.1X authentication timeout in order to make this work for us.

@exworker9to5 said in Perform Full Host Registration and Inventory - Failed:

Which Version of Linux is better for FOG? Centos, Ubuntu, or Debian?

They all work fine. It’s more a question of personal preference.

@sebastian-roth

I used the latest inits and I was able to capture the mac OS drive. I forgot about needing the debug option to get the partclone log.

I didn’t know the dev inits were using the disk size option. I try to keep up on that by going here.
https://github.com/FOGProject/fogproject/compare/dev-branch

Thanks for your time.

I think we got it figured out. I researched that init.xy error and found another ticket that talked about websites being blocked. I did not realize that the tarball still made calls out for files for the update. Sure enough, I found websites blocked. I added those sites to our whitelist, and tried it again and it worked perfect. I guess sometimes you just got to throw your hands up in the air and reset!

Thank you for your help throughout this long drawn out process. 🙂

@devlinn said in Deployment task loops when deploying a Windows image:

Failed to mount C :
mount: can’t find /systemdisk in /etc/fstab

As far as I know this is not part of the official FOG/FOS code base. Please see if you custom have post deploy scripts enabled that are causing this issue.

@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.