@george1421 We have assigned a new flag and applied the ipxe.efi file to the flag. Seems like it has worked.

Thank you @george1421

@george1421 Fog is a waaaaaaayyyyyyyyyyy better fit than Zenworks at the moment, it images 4x faster and its more stable. Fog is actually working very well without these refinements that I want to do

Solved. It was the init.xz file that was customised for our environment, The default was applied and seems to be working now.

Hi Fog community

We have just upgraded our fog application from 1.5.9 to 1.15.10.

After the update, we are now unable to boot our client machines to pull an image from the fog server.

We assume that all the settings would have stayed the same as prior to the update.

The error on the client machines is as follows:
Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(1,0)
Kernel Offset: disabled
-[ end Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(1,0) 1

we have no idea how to fix this.

@george1421 We have assigned a new flag and applied the ipxe.efi file to the flag. Seems like it has worked.

Thank you @george1421

@george1421

yes, the BIOS is set to use UEFI mode only, and the NIC is set to first boot in the priority. We have complied the lastest build and still not able to successfully PXE

Hi fog community

We are unable to PXE boot to fog on an Asus B660 m-c motherboard.

We are running 2pxe files - namely, the snponly and undionly - these files are linked to flags on the network - the flag system works perfectly.

The machine BIOS has been updated and is set to network boot.

It seems like the drivers for the B660 are not included in the efi file set.

Is there any way to get the boot files loaded and to get the machine to PXE boot?

We had to enable 2 flags on the network side of things a C flag has been set to ipxe.efi and a d flag as been assigned to snponly.efi. when a new machine comes in, its registered on the network and assigned either one of these flags. The machine then “knows” to pull the corresponding file for a successful PXE boot.

turns out that the image had to be set to “Multiple partition image - single disk (not resizeable)”

@Sebastian-Roth for future reference, I will be sure to mention version numbers

Everything else worked including the .xml file.

Thank you for the assistance!!

Hi there

we’ve experienced similar issues. We updated the BIOS to the latest stable version - do version-by-version to avoid bricking the machine. Then:

1. disable secure boot
2. make sure that the boot order is set to PXE first (for obvious reasons)
3. set the boot mode to UEFI boot as the partition is set to EFI mode - as seen in the disk management screenshot (partition 1)
4. perhaps try to move your efi partition to the end of the disk - download gparted and make it a bootable flash/thumb drive and you will be able to move the efi partition. you’d want to see your disk looking something like this (attached

boot see what happens?.. ps it of course goes without saying that you should backup your image/disk before playing around with the partitions…

Good day Fog community

I have an image that is not capturing to 100%, it stops and 99% and stays in the active task list. The machine reboots and goes into a BSOD loop.

When checking the image size (size on client), it tells me its 500mb - this seems to me that its the System reserve partition ( its first in the partition table)

The image itself on Fog is set to capture the whole disk “partition = everything”, the "image type = single disk- resizeable.

The same thing happens whether capturing from a VM or a physical machine.

Before closing the image, a chkdsk /f is run and machine rebooted successfully.

Then a .bat file that links to an .xml file that runs specific closure commands ( this process works perfectly for other images)

We have 2 storage nodes - both with more than enough space to hold the image. The above mentioned happens when changing the storage location “image path”

What or where can I start looking for a solution to capture the image to completion (100%) and stop the machine from BSOD boot looping.

Please let me know if you; the community, needs some screenshots or more info, happy to share!

SOLVED! Thank you for the assistance!