Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9k Topics

  85k Posts

  S

  During upload of new image receiving error in title shown in following screenshot imageUploadCapture.PNG

  checked through through the troubleshooting guide

  cat /etc/exports #ro,sync,no_wdelay,subtree_check,insecure_locks,all_squash,anonuid=1001,anongid=1001,fsid=0 /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) #rw,async,no_wdelay,subtree_check,all_squash,anonuid=1001,anongid=1001,fsid=1 /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

  these test.txt from the troubleshooting guide seen below with the folder for the upload device made

  ls -al /images/dev total 20 drwxrwsrwx 4 fogproject fogproject 4096 Mar 26 12:56 . drwxrwxrwx 18 fogproject fogproject 4096 Mar 26 12:53 .. drwxrwsrwx 2 fogproject fogproject 4096 Mar 26 10:44 00155dc81904 -rwxrwxrwx 1 fogproject fogproject 0 Mar 26 11:16 .mntcheck drwxrwxrwx 2 fogproject fogproject 4096 Jul 1 2025 postinitscripts -rwxrwxrwx 1 root fogproject 23 Mar 26 12:13 test.txt

  after following the guide deleted the folder and the capture task remade it like this

  drwxr-sr-x 2 root fogproject 4096 Mar 26 12:56 00155dc81904

  still caused the same error. Ran chown and chmod after to match the permissions as they looked after after the troubleshooting guide still no luck.

• Hardware Compatibility

  Problems with specific computer models.
  710 Topics

  8k Posts

  M

  @dimoura

  Hello!

  Do you have Secure Boot enabled?

  I worked with this Dell Machine about 6 months ago and don’t have it with me now.

  So here it goes.

  Ensure secure boot is disabled. You will need to re-enable it for Windows 11 to work., You need to ensure your SATA mode setting is set to “AHCI”. - If you have “RAID” selected (which was the default from the Dell Machines I tried) it will not work. If you have legacy IPv4 PXE booting that would work best, newer computers no longer have a legacy PXE boot, but use UFEI IPv4 PXE booting. Check if that is enabled.

  Otherwise, check what bzImage files you are using. The bzImage files have the linux kernel drivers which I think I used the latest stable ones I could find. These are placed in /var./www/html/fog/service/ipxe

  There are 4 files in there which need to be there
  bzImage
  bzImage32
  init.zx
  init_32.zx

  Or others depending on what CPU architecture your machines use. These are available on the following URL
  https://github.com/FOGProject/fos/releases

  I found that some work better than others as the FOG project is maintaining their FOS releases and adding computers. It is possible that one you are using simply does not have the drivers for the PC you are using. I would back up these files before updating these to ensure your older machines can PXE when updating your FOS (fog OS).

  Matt

• Windows Problems

  Technical help related to a Windows Problem.
  1k Topics

  8k Posts

  B

  Hello,
  I have a FOG 1.5.10.1734 server. I’m deploying a 25H2 image and I want this computer to integrate into an Active Directory OU.
  The image deploys correctly, but the integration fails, and I’m asked to create a local account.

  Thank you for your help.

• Linux Problems

  Technical help related to a Linux Problem.
  727 Topics

  6k Posts

  H

  Hello,

  I’ve ran into a problem. When upgrading from Debian 12 to Debian 13 I no longer can get to the webpage for fog. I get a 503 service unavailable. After seeing that I decided to re-run the installer to see if that would help but then I get the following dependency conflicts and was wondering if anyone has ran into this yet with Debian 13 Trixie.

  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
  systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
  Conflicts: insserv but 1.26.0-1 is to be installed
  Conflicts: startpar but 0.66-1 is to be installed
  Conflicts: sysv-rc but 3.14-4 is to be installed
  Conflicts: sysvinit-core but 3.14-4 is to be installed
  sysvinit-core : Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
  Recommends: orphan-sysvinit-scripts but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
  E: The following information from --solver 3.0 may provide additional context:
  Unable to satisfy dependencies. Reached two conflicting decisions:

  sysvinit-core:amd64 is not selected for install because: systemd-sysv:amd64 is selected for install systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2
  [selected systemd-sysv:amd64=257.9-1~deb13u1 for install] sysvinit-core:amd64 Conflicts systemd-sysv
  [selected systemd-sysv:amd64=257.9-1~deb13u1]
  For context, additional choices that could not be installed: In systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2: systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install sysvinit-core:amd64 is selected for install because: sysv-rc-conf:amd64=0.99-10 is selected for install sysv-rc-conf:amd64 Depends sysvinit-core
• Mac Problems

  Technical help related to a Mac Problem.
  80 Topics

  942 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.
  684 Topics

  5k Posts

  A

  @astrugatch we have firewalld but you can make the adjustments… some ports have been changed from the initial setup due to network restrictions.

  - name: FOG_Services short: FOG Server network rules description: >- For FOG Server to handle boot, image and various tasks on workstations sources: - SUBNET_IPS allow_icmp: - echo-request - echo-reply services: - ftp - http - mountd - nfs - rpc-bind - tftp ports: - { port: 20048, proto: tcp } # nfs - { port: 20048, proto: udp } # nfs - { port: "35350-36350", proto: udp } # tftp - { port: "49512-65532", proto: udp } # multicast