Subcategories

  • Technical help directly related to FOG.
    9k Topics
    85k Posts
    J

    Hello,

    We have a Windows 11 image that we are deploying to Geekom A6 Mini PCs
    I captured and deployed the image successfully from the first FOG server onto three of these Geekoms at this site.

    I’m following this wiki post > https://wiki.fogproject.org/wiki/index.php?title=Migrate_images_manually#Image_Definitions
    We have a second FOG server running at a different site, I used NFS to copy the folder of this image over to the /images directory on the second FOG server. Then, I exported the image definitions to a CSV from the FOG GUI and imported that into the second FOG server.
    I confirmed that the owner/group permissions of the directory match the permissions on the original FOG server.

    The image appeared in the FOG GUI of the second server, and I was able to run a Deploy task.
    The deploy completes, but when the machine restarts, Windows fails to boot, “Your device ran into a problem and couldn’t be repaired.”

    I’ve tried deploying it three times, to the same PC over at this second site.

    Is there anything I’m missing?

    FOG Server 1 - Version 1.5.5, bzImage/bzImage32 version 6.12.35
    FOG Server 2 - Version 1.5.9, bzImage/bzImage32 version 6.12.35

  • 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

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    L

    @mashina I used a Windows bootstick to go into recovery and checked. All partitions are there but C:\ or the one that would be C:\ is RAW.
    I modified my golden image files to “fix” the problem I’ve been having and here’s the output of the modified files:

    Directory output:

    total 5.7G -rwxrwxr-x 1 fogproject fogproject 4 Apr 7 13:44 d1.fixed_size_partitions -rwxrwxr-x 1 fogproject fogproject 1.0M Apr 7 12:18 d1.mbr -rwxrwxr-x 1 fogproject fogproject 697 Apr 7 13:18 d1.minimum.partitions -rwxrwxr-x 1 fogproject fogproject 59 Apr 7 13:44 d1.original.fstypes -rwxrwxr-x 1 fogproject fogproject 0 Apr 7 12:18 d1.original.swapuuids -rwxrwxr-x 1 fogproject fogproject 697 Apr 7 13:17 d1.partitions -rwxrwxr-x 1 fogproject fogproject 697 Apr 7 13:18 d1.shrunken.partitions -rwxrwxr-x 1 fogproject fogproject 15M Apr 7 12:18 d1p1.img -rwxrwxr-x 1 fogproject fogproject 767 Apr 7 12:18 d1p2.img lrwxrwxrwx 1 root root 12 Apr 7 13:42 d1p3.img -> d1p3.img.000 -rwxrwxr-x 1 fogproject fogproject 5.6G Apr 7 12:27 d1p3.img.000

    As you can see I used I symlink to attempt a fix of d1p3.img.000 and maybe that was my demise.

    d1.partitions:

    label: gpt label-id: 99934977-65D0-41C6-B5E0-92E8085EC24F device: /dev/nvme0n1 unit: sectors first-lba: 34 last-lba: 500118158 sector-size: 512 /dev/nvme0n1p1 : start= 2048, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=740FC648-717D-439E-9AC9-224A270007E2, name="Basic data partition", attrs="GUID:63" /dev/nvme0n1p2 : start= 411648, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=45621D9E-3DD9-4D22-9D25-BCCDE3D0D714, name="Microsoft reserved partition", attrs="GUID:63" /dev/nvme0n1p3 : start= 444416, size= 498042880, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=F20FBC57-04B6-4522-9D20-33998BF119F9, name="Basic data partition

    d1.original.fstypes

    /dev/nvme0n1p1 vfat /dev/nvme0n1p2 raw /dev/nvme0n1p3 ntfs

    d1.fixed_size_partitions

    1:2

    The changes I made resulted in partclone not breaking off after d1p2 and saying it’s done. Now it starts deploying d1p3 and stops after around 80% and gives me this error screen. I tried accessing the log they mentioned but it doesn’t exist on my FOG server.

    WhatsApp Image 2026-04-08 at 17.06.31.jpeg

    I could try and fix this for days but how do y’all capture an image so that it doesn’t break or get captured in a wrong way? I just want a clean image of Windows 11.

  • 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
  • Technical help related to a Mac Problem.

    81 Topics
    943 Posts
    L

    Hello,

    We are preparing a lab with 44 MacBooks (Apple M4, 16 GB RAM) and have a few infrastructure requirements:

    We need the Macs to authenticate against our Samba Active Directory (LDAP/Kerberos) domain.
    We would like to understand whether FOG Project can clone a macOS image and replicate it across the other machines, since all devices share the same hardware configuration.
    If FOG is not suitable for this scenario, we would appreciate recommendations for tools or methods that can help us deploy a standardized macOS image to all machines.
    This imaging/deployment process is performed once every semester, so we are looking for a reliable and repeatable solution.

    Could you please advise on the feasibility of this approach and suggest best practices or tools for mass deployment and domain integration in this context?

    Thank you.

  • General Developer questions relating to FOG.
    684 Topics
    5k Posts
    AUTH IT CenterA

    @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

133

Online

12.6k

Users

17.5k

Topics

156.4k

Posts