Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9k Topics

  86k Posts

  V

  Working in a VM (QEMU/KVM/Libvert) I found that attempting to capture (single disk resizable) a fresh ISO (June 2026 Windows 11 Enterprise) install where I enter audit Mode and then sysprep, the capture fails to resize during the FOG capture process:

  “An error has been detected! … Resize test failed! … Device name: /dev/sda3 … Space in use: 10535MB (16.6%) … Needed relocations: 1610313 (6596MB) … ERROR(28): Could not update runlist for attribute 0x80 in inode 156294: No space left on device (shrink partition) Args Passed: /dev/sda /images…”

  Previously I had no issue capturing an install using Windows 11 Build 28000.1836 via FOG. The older build allowed for smaller VM disk size such as 40GB if I recall. The newer June 2026 ISO Build requires around 50GB for Windows 11Enterprise to install (else there is an error) so I allocated 60GB to the current VM (where I am getting the capture error).

  I found that on the June 2026 Build (28000.2269) if I set the EFI partition size to 2GB (still using 60GB VM disk size) during the installation using diskpart, complete the install, enter audit mode, sysprep, and then attempt the capture I am successful and there is no resize failure. Why does setting the EFI partition to a larger size allow the capture process to succeed? (I found this by accident as I was increasing the EFI partition for another reason discussed in the side note here)

• Hardware Compatibility

  Problems with specific computer models.
  711 Topics

  8k Posts

  T

  @JCS-RVK Understood and apologies there’s not a good method around this.

  Thanks for at least understanding. I wonder if some of the similar types of issues we’ve seen historically have a similar style of problem that I’m only coming to realize now-a-days.

• Windows Problems

  Technical help related to a Windows Problem.
  1k Topics

  8k Posts

  G

  @Tom-Elliott

  I pulled latest dev-branch version 1.5.10.1856, re-run installer and snapins are working again.

  Thank you very much for help.

• Linux Problems

  Technical help related to a Linux Problem.
  730 Topics

  6k Posts

  J

  Shoutout “The Minester”

  https://github.com/FOGProject/fogproject/issues/685

  On the storage node, create a .my.cnf file in root’s home directory:

  sudo tee /root/.my.cnf << ‘EOF’
  [client]
  skip-ssl = true
  EOF

  MariaDB will try to connect with SSL by default but that’s not enabled on the main FOG server. This is why I had to use the --ssl=FALSE flag when I connected to mysql manually.

  The installation succeeded!

• Mac Problems

  Technical help related to a Mac Problem.
  81 Topics

  943 Posts

  B

  Hello everyone,

  As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
  I already use FOG to deploy Windows and Linux images on PCs.

  I would like to deploy a LinuxMint image on these iMacs.

  However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

  I modified my DHCP server as follows:

  ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

  I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

  I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

  Thanks in advance!

• General Problems

  General Developer questions relating to FOG.
  686 Topics

  5k Posts

  B

  @Tom-Elliott

  I’ve updated my FOG to the stable release and also updated my script with the following three lines, and everything’s fine – the database has been backed up successfully, it’s perfect!

  fogApiToken="XYZ=" fogUsrToken="ZYF" curl -ik -X GET "http://$fogServerAddress/fog/system/export" -H "fog-api-token: $fogApiToken" -H "fog-user-token: $fogUsrToken" -o $backupDir/mysql/fog.sql 2>>$backupDir/logs/error.log 1>>$backupDir/logs/progress.log 2>&1

  Thanks again for all your hard work on the FOG project!