• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • J

      EFI Stub Errors on XCP-ng Virtual Machine Attempting 'Perform Full Host Registration and Inventory'

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      15
      0 Votes
      15 Posts
      683 Views
      R

      @JCS-RVK Okay so I don’t see why this kernel wouldn’t work for you with those settings. Only difference I can think of may be the initrd version that is being loaded. I know that @BPSTravis is using the latest released version so it wouldn’t hurt to update yours too.

      I also see that you are running an older version of FOG. You could upgrade to the latest stable release and that will also download the latest initrd.

      You could also download it manually if you don’t want to update FOG:

      On your FOG server, run this command to download the latest initrd
      wget https://github.com/FOGProject/fos/releases/download/20260306/init.xz

      Move it to the correct location like this:
      sudo mv init.xz /var/www/fog/service/ipxe/

      Then you need to change the permissions and ownership of that file:
      sudo chmod 644 /var/www/fog/service/ipxe/init.xz

      Red Had based server: sudo chown fogproject:apache /var/www/fog/service/ipxe/init.xz

      Debian based server: sudo chown fogproject:www-data /var/www/fog/service/ipxe/init.xz

    • B

      image Multicast issue

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      6
      0 Votes
      6 Posts
      207 Views
      B

      @Tom-Elliott
      I did not update yet to 1824, but i did SELECT * FROM HISTORY;

      MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 1 row in set (0.000 sec)

      the new session i create are not shown, and dont work until i run the maintenance queries

      then it shows in history table:

      MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | | 2 | [2026-04-01 09:10:37] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 09:10:37 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 2 rows in set (0.000 sec)
    • hariskarH

      Fog as a backup tool?

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      69 Views
      hariskarH

      @heix75 Thanks a lot for reply!
      I use a medical lab program that stores clients data and examinations results almost all day. Of course I take incremental SQL backups.
      So if something breaks I would like to have a recent PC backup to only restore SQL.
      I used Macrium for that and now I use UrBackup which is open source but not widely used and I wonder if Fog would be a better solution.

    • D

      Database Error when select a group

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      1 Votes
      3 Posts
      130 Views
      D

      @Tom-Elliott Hi Tom,

      log for apache error:

      [Wed Apr 01 16:05:36.847438 2026] [proxy_fcgi:error] [pid 1232] [client 172.28.1.84:48932] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.860169 2026] [proxy_fcgi:error] [pid 1233] [client 172.28.1.84:48946] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.877158 2026] [proxy_fcgi:error] [pid 1234] [client 172.28.1.84:48952] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.889945 2026] [proxy_fcgi:error] [pid 1231] [client 172.28.1.84:48968] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84'

      the php-fpm error:

      [01-Apr-2026 12:57:13] NOTICE: Terminating ... [01-Apr-2026 12:57:13] NOTICE: exiting, bye-bye! [01-Apr-2026 15:57:34] NOTICE: fpm is running, pid 758 [01-Apr-2026 15:57:34] NOTICE: ready to handle connections [01-Apr-2026 15:57:34] NOTICE: systemd monitor interval set to 10000ms
    • L

      Trying to deploy Windows 11 25H2 using FOG always leads to the Windows recovery screen

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems
      2
      0 Votes
      2 Posts
      63 Views
      F

      Have you sysprep your Windows before capture ? (i don’t think it’s related but it’s important to do this, if no need nothing just launch C:\Windows\System32\Sysprep\sysprep.exe and coche generalize, shutdown)

      I use “Multiple Partition Image All Disks” just for the upload, and after upload done, i set “single disk resizable” for the deploy.

    • L

      FOG PXE Boot Error – iPXE “Exec format error” / Chainloading failed

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      105 Views
      Tom ElliottT

      @lucasgfaj have you turned off secure boot?

    • T

      Sysprep in FOG?

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      70 Views
      R

      @trent_potter Yes you figured it out. Sysprep is a Windows utility, it has nothing to do with FOG. It is always recommended to sysprep before capturing an image.

    • D

      Schedule Multicast Tasks Issues

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      10
      1 Votes
      10 Posts
      489 Views
      Tom ElliottT

      @devle I’ve made a couple of edits, though I still cannot replicate the problem you’re seeing.

      You shouldn’t see the errors any more (just saying), though I don’t know if these things will fix whatever problem you’re seeing.

    • L

      Subject: Imaging and Domain Integration for 44 M4 MacBooks (FOG / Samba AD / LDAP)

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Mac Problems
      1
      0 Votes
      1 Posts
      22 Views
      No one has replied
    • K

      FOG Secure Boot with Shim

      Watching Ignoring Scheduled Pinned Locked Moved Tutorials
      6
      2 Votes
      6 Posts
      3k Views
      T

      @KMEH Hi,

      I tried your method and it only partially worked. It reached the FOG menu correctly after enrolling the key, but the problem arises when I try to perform a quickreg or deploy an image. In both cases, I get the following error (it starts working again when I disable Secure Boot)fog uefi error.png

      my version is 1.5.10

    • G

      Detected Hardware unit hang

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      1
      0 Votes
      1 Posts
      110 Views
      No one has replied
    • J

      Boot and Nuke/Disk Wipe PXE Menu - Any Method Welcome!

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      936 Views
      P

      Hello @jrajra,
      I got this to work on my instance using ShredOS by doing the following:

      Log in to your Fog web portal Go to “Fog Configuration” Click the “iPXE New Menu Entry” button Enter the following details:
      * Menu Item=ShredOS
      * Description=Boot and Shred (AutoNuke)
      * Menu Show with=Not Registered Hosts
      * Parameters= kernel https://${fog-ip}/shredos/boot/shredos console=tty3 loglevel=3 shredos_exclude_boot_disc="yes" nwipe_options="--autonuke --nowait --method=zero --noblank --nousb --PDFreportpath=noPDF --autopoweroff" boot Log into your Fog Linux server Open the terminal Run the following commands: mkdir /iso mkdir /var/www/html/shredos wget -O /iso/ShredOS.iso https://github.com/PartialVolume/shredos.x86_64/releases/download/v2025.11_28_x86-64_0.40/shredos-2025.11_28_x86-64_v0.40_20260204.iso sudo mount -t iso9660 -o loop /iso/ShreadOS.iso /var/www/html/shredos chmod -R 777 /var/www/html/shredos

      Doing these steps should create a “New Menu Entry” for ShreadOS and specify to shred upon boot, don’t write a completion file, & then turn off the device. (For safety in our environment, I have this option only appear if the device is not registered.)
      It then downloaded the ShreadOS file from Github & then mounted the iso as an accessible boot file in the Fog URL. (You can manually download the file & put it in the “/iso” folder instead if you want.)

      I have tried this with dban as well, but that only worked for old BIOS based computers. This one on the other hand works for UEFI computers.
      I also found this article that might help you: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images
      I hope this helps you,
      Preston

    • 1 / 1