@davistran86 this worked excellently. i adopted mine to http flawless

@george1421 Thank you once again for great support!!!

@Lee-Rowlett Thanks!

Why would you want to run both clonezilla and FOG? FOG uses partclone which is the same program clonezilla uses. That said, it’s one thing if you wanted to use a CloneZilla Image on a host. We do have support for that, by simple creating the Image definition and setting the Image Manager to Uncompressed. FOG, however, has many more options readily available and configurable via the GUI. Again, this is not to say you cannot use Clonezilla images with FOG. However, FOG manages hosts, inventory, images, and much more through a simple web gui. Running clonezilla is possible, but still means you have the manual tasks to complete. I guess we need to understand the why of this more so we can try to help you out more.

@george1421 I used to see the issues with warm boots on older versions. That seems to not be the case in the latest version.

you da man!

Since the apache crashes did not correlate with the no directory or file errors I double checked everything attached to our workbench and… Found out one of my engineers had a test box attached to our workbench that was set for no reply to ICMP so I did not catch it had been static’d to 10.0.0.250 as well. Flipped it over to DHCP and now PXE boot works consistently. Sorry and thank you for your time!

@Deps I would recommend if your setup is not exactly the same as the OP in this thread that you open a new thread. We will need more information on what type of computer Mfg and Model, what version of FOG are you using and what FOS Linux kernel are you running. From your description, it sounds like the target computer is not registering correctly or the network adapter’s MAC address is changing between registration and the next reboot.

Hi @Junkhacker It’s an raid array of 6x900gb 15k SAS drives connected to an HP P408i-a SR Gen10 Controller. All of it combined to a single D: drive in Windows.

Hi all, i have secureboot working with ipxe (FOG) using a self-signed certificate and you do however need to enroll the keys but i have added an .efi program that you can run to automate all this from the pxe boot menu to ease this process. i’ve been testing it for the last 12 months or so to see if there is any gotchas but none yet and over 80% of our estate have secureboot with ipxe working (7K devices) - only lenovo x1 carbons have been problematic but this appears to be due to poor bios and/or secureboot implementation. this does mean you have to manage the certificates yourself going forward too as you are essentially taking ownership and provisioning the devices and applying your own PK which means you have to trust 3rd party CAs however the plus side there is no cost involved. i also don’t have assurances how to remotely distribute a renewed certificate when it expires but expiration is 10 years and there is going to be some work needed when microsoft CA expires in 2026. on first attempt, i hadn’t included microsoft CA so windows os failed to load with untrusted error from secureboot… i loved the irony… i dont trust microsoft either :-) if anyone is interested i can write up instructions however you have to remember technically this is outside of FOG remit, so support on FOG forums will be extremely limited and unfortunately with 2 jobs i have very little time to spare either.

i restored the background file, clicked “Update” on the menu settings page of the WebUI and all is fine now. Weird. One question though, from the main FOG ipxe menu, when i hit Deploy Image, and get the prompt to authenticate with fog/pass, that text is blue, i want it to be white. Where can i change that setting?

Some options. 1º Use a snapin pack including the executable. 2º Put it in a ftp server and use a cmd ftp client to download it. (You can use the fog server/node as ftp and the built-in ftp client) This two solutions works!!!

If you are seeing bzImage being transferred you can remove iPXE out of the problem. The default you should have for uefi is ipxe.efi. Now you should focus on the FOS Linux engine (bzImage). What version is the FOS Linux kernel? I know I have a Dell 7400 2 in 1 with a Dell usb c dongle (as well as a WD15/WD19 docks) that boot into FOS Linux and pick up a dhcp address. I find it strange that it finds the network adapter, and sees the link come up but can’t communicate over that link. Lets start with what version of kernel are you using? The next part is to schedule a new capture/deploy task but tick the debug check box before you schedule the task. Then pxe boot the target computer that will but the target computer in debug mode so we can key in some additional commands.

To clarify, all I’m doing is modifying the MAC address on a host in FOG and clicking the update button. After that, when refreshing the page, I noticed it added the old address as an additional MAC. You might not see it until you refresh. I’m not clicking any other buttons related to adding an additional MAC. FOG just adds one itself.

@Wayne-Workman Worked for me

@Peter365 The only comment I can make is watch the permissions on the /images directory now. If you run into upload issues issue this command (note is a bit loose with the security, but its not too big of a risk) chmod -R 777 /images

@Wayne-Workman a bit late in the day but have just setup Fog Imaging server. Could get Realtek Nics to work. Your post solved the issue.

@paat So just to be clear, you have a Dell branded usbc cable? I have a dell branded usb c ethernet adapter on a 7400 and I can pxe boot into the fog compatibility menu (I don’t want to image my workstation at the moment) and ping devices. So I know the network adapter works. Also when we image we typically use the WD15 dock (the WD19 docks are flaky some times with pxe booting). That way we charge the laptop as well as image at the same time. This is the dell usbc dongle we are using: https://www.dell.com/en-us/shop/dell-adapter-usb-c-to-ethernet-pxe-boot/apd/470-abnd/pc-accessories Also what version of FOG are you using as well as what FOS Linux kernel version do you have?

I have been paying with this for a bit now and was working through a scenario where the OS doesn’t get an IP so trying to statically assign one, at least temporarily. I wasn’t able to get it to work but I think it just needs a little more time to work on this scenario. Otherwise, this works quite well. I did some minor tweaks so that my end user only had to boot to the USB drive and after the cron job runs keep an eye on the screen for the IP of the FOG server which I echo’ed out at the end of the script using: printf “The IP of the FOG server is: $IP \N” > /dev/console I sent it off to a co-worker in another location and asked them to just plug in the USB drive, boot to it, wait for the message then try another machine to see if he got the FOG menu. He did and was able to register the machine with FOG and pull an image down so I’m marking this: SOLVED!!! I may try to go back when I have some time to finish hashing through the statically assign an IP if you don’t get one scenario…

Current Solution set Kernel to 4.19.64 and set global option in Fog Configuration–> FOG Settings --> General Settings --> Kernel ARGS to tsc=unstable Luckly this is the last year for these machines.