Good Day,

I’ve got a problem with fog on a new series of laptops. I thought it might be driver related so I grabbed the latest version of fog from the MASTER branch as IPXE is reporting it’s up to date with the master branch. It downloads the bzimage then when init.xz is running it’s stopping at 74%. I’ve left it running for hours it doesn’t move past this issue. I’ve tried other EFI files and it either doesn’t go anywhere or stops at 19%. I’m running snponly.efi. It takes me to the highest number.

Many thanks
Duane Ashwell

@george1421 and @Sebastian-Roth
The version is 1.5.9 and the INIT version is 20220203.

Thank you for telling me where to look.

@sebastian-roth I have backups of the FOG and FOS, is there an easy way to check the version of the INIT files, because that was the most recent change?

We used this image for deployment to 300 laptops before. However, after the recent FOG updates the following error is now occurring to a device that was previously imaged.

@sebastian-roth Thanks Sebastian, I know how to pull the latest kernel driver. However, I do not know how to pull the latest inits/ which files I should pull?

Recently restored an image from a 500GB SSD to a 1TB SSD.

However on further inspection the FOG server seemed to write the image to the end of the drive.

Fog version 1.5.9

Is there a way we can script the removal of a file or folder before the capturing of an image. Or, can it be scripted to be done after the image is deployed. Before the final reboot?

The hidden recovery partition Windows 10 creates is problematic if you restore the image to a different drive. Fog automatically shrinks the main partition and allows it to be dynamically expanded. Can’t the non-sizeable partitions after the shrunk partition be dynamically moved. This will avoid the following issue.

@sebastian-roth Good evening Sebastian. The MAC passthrough is set to system. I have the options of System, Custom or disabled. Which would you recommend.

We have three laptops from which we wish to capture images. We can successfully boot to the FOG bootup menu and can deploy images. However, when I do a quick inventory, first time the inventory runs fine. No Errors. I then schedule a task to capture an image for deployment. When the machine boots into the menu again it doesn’t trigger the auto capture but reports that the HOST is not Registered.

This fault is only occurring on machines where there is no built-in NIC, only WIFI. We are using a USB 3.1 NIC adapter.

We can capture images correctly on the other units with the Built-in NIC’s.

Kind regards
Duane