• problem with debian/ubuntu images

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    8 Views
    Tom ElliottT

    @xavier-duthilleul I suspect it’s your /etc/fstab is looking at a UUID instead of a physical medium.

    The one drawback to the uuid method of bootloading (which is great to always ensure you get the same files) is that the UUID’s are not the same between systems.

  • Clients stuck at iPXE initialising devices

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    14 Views
    No one has replied
  • FOG 1.5.10.1698 - UI bugs

    Unsolved Bug Reports
    2
    0 Votes
    2 Posts
    54 Views
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

  • All services are globally disabled

    Unsolved FOG Problems
    5
    0 Votes
    5 Posts
    437 Views
    Greg PlamondonG

    @Tom-Elliott
    That may be my problem Tom. I switched to the Stable build, I may have inconsistant DB schema between the two?
    The GUI says I am on Version 1.5.10.1763

  • Golden image questions

    Unsolved Windows Problems
    1
    0 Votes
    1 Posts
    18 Views
    No one has replied
  • Debian Trixie Dependancy Errors

    Unsolved Linux Problems
    1
    0 Votes
    1 Posts
    31 Views
    No one has replied
  • Unable to Fast Wipe | Chainloading failed

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    474 Views
    C

    @Tom-Elliott apologies for the delay but here is what I see in the error log when this occurs:

    For context the 'Client IP Detected as <IP ADDRESS> is a small modification to the Subnet Groups plugin which I log the IP of the client checking in, this is working as intended.

    The ‘PHP Fatal error’ is what I only see when we have the chain loading error.

    I can confirm this is working on: 1.5.10.1734 as I have rolled back any sites to this version and have seen no issues.

    [Mon Feb 23 15:07:55.208763 2026] [proxy_fcgi:error] [pid 501804] [client 10.9.209.159:33595] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:08:27.815241 2026] [proxy_fcgi:error] [pid 501806] [client 10.9.209.159:1025] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:09:00.456158 2026] [proxy_fcgi:error] [pid 501802] [client 10.9.209.159:1555] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:09:33.088040 2026] [proxy_fcgi:error] [pid 501802] [client 10.9.209.159:6935] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:10:05.672334 2026] [proxy_fcgi:error] [pid 501803] [client 10.9.209.159:16900] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:10:38.336356 2026] [proxy_fcgi:error] [pid 571479] [client 10.9.209.159:43335] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:11:10.976801 2026] [proxy_fcgi:error] [pid 501803] [client 10.9.209.159:36391] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496'```
  • FOG hangs on "... free base memory after PXE unload"

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    456 Views
    J

    @rodluz 0f341e2a-1996-4ec7-91ac-4269fe20a31c-image.png

    I’ve updated the iPXE on my proxmox server, still hangs on this message. Other VMs work fine, as they did with the older iPXE version.

  • After BIOS update no connection or timeout

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    203 Views
    No one has replied
  • Dell Pro Slim

    Hardware Compatibility
    5
    0 Votes
    5 Posts
    2k Views
    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

  • DHCP works, but then keeps trying

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    351 Views
    C

    I have just discovered that somehow all the MACs are changing sometime after the final successful DHCP lease.
    My DHCP server is set to only answer to specific MACs, so if I add in the “new” one, it works.
    No idea how this is happening, I’ve never seen MACs just suddenly change like this.
    It sucks that now I have another MAC per server to deal with, but at least it’s working.

  • version 1.5.10.1763 on debian 13.3.0 problem KEYMAP

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    251 Views
    F

    I’m also interested in knowing if a solution exists.

  • Version 1.5.10.1763 incorrect Image Size ON CLIENT

    Unsolved Bug Reports
    3
    0 Votes
    3 Posts
    109 Views
    H

    @rodluz yes, directly from 1.5.10.1754 to 1.5.10.1763 when I saw the prompt in the FOG gui that I’m not using the latest version - it was up to date before.

    in 1.5.10.1754 recapture didn’t added up, just updated the image size to the latest one.

  • Anyone with a working imgargs for PXE installing Ubuntu 24.04?

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    364 Views
    No one has replied
  • FOG Boot via HTTP without DHCP

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    477 Views
    T

    @Greg-Plamondon
    Hi,

    we got a dhcp server. The computer got network, the path to the efi file is connected.
    I have no access to the dhcp settings that i could set the next-server or anything else.
    But i think the efi file maybe is corrupt? i have tried to edit the efi file, but then the boot stick does not work anymore.

  • Unable to Capture an image: ERROR: Could not adjust the bad sector list

    Unsolved FOG Problems
    11
    0 Votes
    11 Posts
    2k Views
    B

    @deharter i could capture changing the image type , from “Single Disk - Resizeable” to “Multiple Partition Image - Single Disk (Not Resizeable)”

  • Failed to capture images from RAID computer

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    432 Views
    No one has replied
  • Configure iVentoy as netboot-Option in boot menu

    Tutorials
    8
    1 Votes
    8 Posts
    10k Views
    Cire3C

    @youzersef Ok, see how long it takes me to get back on a project…lol

    I did some more looking, and found yes, the GUI will re-write the dhcp config file. However I did some more reading and I guess services.inc determines what is written by the GUI.

    Sorry, not a CLI guy, and I love the quick and easy edits, viewing issues that the GUI provides. Like Fog ! However my servers are headless…lol

    Anyway, looking that route now, and will update if I find how Negate wants services edited so when it reboots, DHCP will remain.

    Determined 🙂

    Any thank you everyone here . This place has always been great for information !

  • Quick Registration and Invenotry not working

    Unsolved FOG Problems
    9
    0 Votes
    9 Posts
    1k Views
    S

    @Tom-Elliott

    So f144ad5 is the last working commit. In case anyone else have the same problem, this is my script to grab it and modify so it works fine with EFI keyboard in some PCs as discussed here: https://forums.fogproject.org/topic/17870/fog-ipxe-menu-no-input. It also removes neverssl.com site because it’s down now so script hangs on checking internet connection. Don’t mind main sed part, it’s probably overcomplicated since I used ChatGPT for it, but it works fine so who cares 😉

    #!/bin/bash # Checkout last working FOG project commit cd git git clone https://github.com/FOGProject/fogproject.git cd fogproject git checkout f144ad5a30bdab23be4d207b471ca80057e367fd # Modify functions.sh to remove non working neverssl.com site cd ~/git/fogproject/lib/common sed -i 's+http_sites=("neverssl.com" "httpbin.org")+http_sites=("httpbin.org")+g' functions.sh # Modify buildipxe.sh to grab last working ipxe commit and fix EFI USB drivers cd ~/git/fogproject/utils/FOGiPXE cat > transform_buildipxe.sed <<'SED' /^[[:space:]]*git pull$/a\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a /^ cd \${BASE}\/ipxe\/src\/$/c\ cd \${BASE}/ipxe/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe/src/ /^ cd \${BASE}\/ipxe-efi\/src\/$/c\ cd \${BASE}/ipxe-efi/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe-efi/src/ /^sed -i 's+#define[[:space:]]*USB_HCD_USBIO+\/\/\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/c\ sed -i 's+#define<----->USB_HCD_USBIO+//#define>USB_HCD_USBIO+g' config/usb.h /^sed -i 's+\/\/\#define[[:space:]]*USB_HCD_USBIO+\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/, /^sed -i 's+\/\/\#undef[[:space:]]*USB_EFI+\#undef[[:space:]]*USB_EFI+g' config\/usb\.h$ #sed -i 's+//#define\tUSB_HCD_USBIO+#define\tUSB_HCD_USBIO+g' config/usb.h\ #sed -i 's+//#undef\tUSB_KEYBOARD+#define\tUSB_KEYBOARD+g' config/usb.h\ #sed -i 's+//#undef\tUSB_EFI+#undef\tUSB_EFI+g' config/usb.h\ sed -i 's+//#define+#define+g' config/usb.h\ sed -i 's+#define USB_CMD+//#define USB_CMD+g' config/general.h SED sed -i -f transform_buildipxe.sed buildipxe.sh rm -f transform_buildipxe.sed # Start FOG install/update cd ~/git/fogproject/bin ./installfog.sh
  • 0 Votes
    6 Posts
    579 Views
    raulR

    @Tom-Elliott Do the values in .fogsettings get applied only the first time installfog.sh is executed, or are they supposed to be applied on every subsequent run as well?
    In my case, updating .fogsettings after the initial installation doesn’t seem to change anything, so I want to confirm whether this is expected behavior or if I’m missing something.