I have done a fresh installation of ubuntu_20.04 and fog_1.5.9 on VirtualBox environment and works fine. Probably it’s a vmware issue or vmware config issue.

@tesparza Thanks a ton for your good will to help! Appreciate.

It’s a paid software. I need it to keep the students from destroying the computers.

I have found another thread talking about this RRRx software (which does the same so I don’t mind using it instead) and he fixed it by replacing the boot file, he used ipxe.kpxe instead of undionly.kkpxe.

And here is the proccess I made trying to figure out the problem: https://forums.fogproject.org/topic/15636/unable-to-boot-properly-after-radix-smartrecovery-installed/2?_=1628169887941

@tesparza Probably a database maintainace might help. Search the wiki or forums to find the instructions.

@esmatos Well the error is saying that the boot file needed is not found.

I can say that pfsense does work with fog. You need to make sure you fill out the Network Booting section properly.

Enabled: Checked
Next Server: (ip address of fog server)
Default BIOS: undionly.kpxe
UEFI 32 bit: i386/ipxe.efi
UEFI 64 bit: ipxe.efi

If that doesn’t work then lets grab a pcap of the pxe booting process as long as the FOG server and pxe booting client are on the same subnet you can use the FOG server to capture the pcap: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

@astrugatch if this host isn’t already registered, this can be enabled globally, and likely won’t hurt anything even if it’s forgotten about.

FOG Configuration Page -> FOG Settings -> KERNEL ARGS add noapic

@sebastian-roth

Solved!!!

The error was in /etc/default/isc-dhcp-server.
It was set to eth0 instead of ens18

I have more problems. I will open new posts if necessary

Thank you for all!

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.