@brad-chamberlain If you edit the dhcp config file make sure you restart the isc-dhcp service.

The next step is to see what the dhcp server is telling the client. The easiest way is to use tcpdump to capture the dhcp process.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

You can use tcpdump on the fog server or install wireshark on the fog server if you have the Xwindows ui installed. For wireshark use the capture filter of port 67 or port 68 or port 69 or port 4011 Start tcpdump/wireshark and then pxe boot the target computer to the error. Then stop the capture.

Review the pcap with wireshark. You should see the DORA process (Discover, Offer, Request, Ack/Nak). The target computer will send out a DISCOVER packet, look at packet at dhcp option 93 this will be the target computer saying what type it is uefi or bios. Then look at the OFFER packet from the dhcp server. In there the header should be set with {next-server} and {boot-file} matching dhcp options 66 (fog server IP) and option 67 boot file name. The answer should be in the dhcp process. If you can’t spot it upload the pcap to a file sharing site and either DM me the link or post it in the thread and I’ll take a look at it.

The dhcp settings you copied from the coexistence page should be accurate.

@sebastian-roth Thank you very much for the quick reply! PhP was running on version 8.x. Downloading and running the current dev-branch now allows me to connect to the web interface. Thank you for your help!

@Joshjb Either use Ubuntu 20.04 or the latest development version (a.k.a dev-branch) found on GitHub.

@adami said in Blank screen during install on Fedora:

Any ideas? Fog version 1.5.4. Fedora 36.

@adami Version 1.5.4 is years old - not compatible with PHP8. Please use the latest dev-branch version.

@leonjv The FOG 1.5.9 installer was not smart enough to check for an exiting DB and tried to use whatever it considered right. This was fixed in the latest dev-branch version (github commit). You can wait for the next release or use the dev-branch version.

@george1421 Alright. Thank you very much!

@george1421 Hi, I`m sorry , i have attached wrong info and screenshot with video. It was a result of my attempts to boot from .tgz ubuntu which i found in an old sysadmin files, which very like a foreman tools.

@thebaz The number of times someone has upgraded the OS of their FOG server and broken FOG is a lot. So many that it prompted me to write this article about five years ago. The article is still valid. My advice is to not upgrade the OS of your FOG server, unless it’s in a VM and you take a snapshot before hand. If it’s not in a VM, your safest choice is to migrate.

@george1421 Hey George, sorry I didn’t reply yesterday. I did get everything running successfully. Captured an image and deploying image right now! Appreciate all your help! Not sure how to mark this is as solved but its working!

@alansmithee said in Proper way to install client on Linux hosts:

Actually I was wondering if it was feasible to install the client before capturing/deploying

That is how you typically would do that in the windows world. From a windows perspective the fog client is installed then the service is set to disabled. At the end of the winsetup process windows calls a batch file called setupcomplete.cmd that is used to issue the commands to the fog client to startup on every reboot. The issue with windows is as soon as the fog client starts it will start executing its tasks. If windows oobe/winsetup is still doing their bits the fog client may reboot the computer without oobe being done, thus creating a botched install. Linux first boot is nothing like windows, so it may be OK to leave the linux fog client configured to auto start at each reboot.

@wt_101 said in CentOS LVM Slow Imaging:

what do u mean by RAW image type?

This is a mode for partclone when it can’t determine the format of the disk, this is a default mode when no other disk format filters exist, such as with LVM. In linux terms partclone uses dd (disk dump) format to image the disk. This is the slowest and largest format since it copies all disk blocks. Partclone might change to this format if it detects and encrypted drive where it can’t read the partition information because its encrypted.

ref: https://partclone.org/usage/partclone.dd.php

fixed from me and working

kernel tftp://${fog-ip}/os/redhat/r9/vmlinuz
initrd tftp://${fog-ip}/os/redhat/r9/initrd.img
imgargs vmlinuz initrd=initrd.img root=live:nfs://${fog-ip}:/images/os/redhat/r9/images/install.img ip=dhcp inst.repo=nfs:${fog-ip}:/images/os/redhat/r9/BaseOS splash quiet
boot || goto MENU

@george1421 I finally got it working!

I ran fsck.ext4 /dev/sda2 and it fixed the partition layout.

Thanks again for your time 🙂

Thanks Wayne, I’ll get the the swap partitioned removed, recapture and try again!

@george1421

That was totally it! I was confusing myself with the /images directory for tftp. After changing the command to match the /tftpboot directory everything works perfectly. Thanks for your help!