• 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
    • M

      HD info not populating in log

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      22
      0 Votes
      22 Posts
      478 Views
      M

      @Tom-Elliott Thank you, Tom. The init version is now 2025xxx. I’ll test soon to confirm the SSD info is showing in logs.

    • D

      The DDP package file was not found or could not be read

      Watching Ignoring Scheduled Pinned Locked Moved Hardware Compatibility
      5
      0 Votes
      5 Posts
      74 Views
      george1421G

      @djgalloway Well you have a pretty complex environment when you are chain loading other boot loaders. What I would do on a temporary debugging bases, update your dhcp server settings to use the fog server’s IP for dhcp option 66 and ipxe.efi for dhcp option 67. This will use a fog only solution. Something else that might cause the issue is that the linux kernel that is booting, is not the kernel shipped with FOG. Or the opposite, the init.xz image is not a FOG image. The fog developers compress the init.xz image with an uncommon (in regards to linux file systems) compressor, if the booting linux kernel doesn’t have that image decompressor built in you will get that error about unknown block (because its still compressed).

      It does look from your screen shot that both a bzImage and init.xz is being copied over to the target computer. Another but less likely issue could be that you are not using the custom ipxe.efi boot loader that was shipped with FOG.

    • I

      Snapin Pack Arguments double-quotes problem

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      13
      0 Votes
      13 Posts
      1k Views
      Tom ElliottT

      @Infojoe They are one in the same lol and you’re welcome.

    • C

      FOG boot issue after BIOS update on HP ZBook Fury 16 G11 – iPXE autoexec.ipxe not found

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      6
      0 Votes
      6 Posts
      709 Views
      JJ FullmerJ

      @CanadienITGuy Just for your and anyone’s fyi the autoexec.ipxe... Not Found is not an error. It’s more of an info message than a warning or error.
      I actually have tested adding an autoexec.ipxe, even just an empty file to remove that message but even an empty file or a file that is even just a symlink or copy/paste of our normal ipxe/boot menu files causes things to break in the process.
      The autoexec.ipxe is meant for adding customization to the ipxe process without needing to re-build the ipxe binary. But my testing with it within the fog workflow was that it’s best to just let that message exist and to see it as it being not found means the process will not be altered from your expected Fog ipxe workflow

    • J

      FOG Portable

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      64 Views
      J

      @george1421 I have installed fog with DHCP server but DNS doesn’t work at all (no dns server appear on windows client) so I’m stuck.
      It’s my first time installing DHCP and DNS on Debian so I think I made mistakes.
      DHCP work fine.

      edit : It’s fixed. I forgot to add “option domain-name” and “option domain-name-servers” in dhcpd.conf

      For the script, I think it must be simple to set FOG as DHCP server at startup if after 10 min no IP is given from a DHCP server then set server to static IP and start DHCP and DNS services.
      And then reverse this at shutdown.
      Maybe this can be done manually first.

      edit : Here is the first script.
      I have create files ending with .dhcp for conf for external DHCP/DNS and file ending with .static for conf for local DHCP/DNS.
      It looks to work fine.

      # Configuration actuelle echo "Etat DNS local :" systemctl is-active bind9 echo "Etat DHCP local :" systemctl is-active isc-dhcp-server echo "" loc(){ # Configuration DHCP local echo "DHCP local" # Configuration if [ -e /etc/network/interfaces.static ] then echo "Copie interfaces" cp /etc/network/interfaces.static /etc/network/interfaces else echo "interfaces.static not found" exit 1 fi echo "Redemarrage service reseau" systemctl restart networking.service if [ -e /etc/resolv.conf.static ] then echo "Copie resolv.conf" cp /etc/resolv.conf.static /etc/resolv.conf else echo "resolv.conf.static not found" exit 1 fi # Services systemctl start bind9 systemctl start isc-dhcp-server } ext(){ # Configuration DHCP externe echo "DHCP externe" # Configuration if [ -e /etc/network/interfaces.dhcp ] then echo "Copie interfaces" cp /etc/network/interfaces.dhcp /etc/network/interfaces else echo "interfaces.dhcp not found" exit 1 fi echo "Redemarrage service reseau" systemctl restart networking.service if [ -e /etc/resolv.conf.dhcp ] then echo "Copie resolv.conf" cp /etc/resolv.conf.dhcp /etc/resolv.conf else echo "resolv.conf.dhcp not found" exit 1 fi # Services systemctl stop bind9 systemctl stop isc-dhcp-server } # Demande de Configuration while true; do read -p "Voulez vous passer en DHCP externe ou en DHCP local? (e:externe l:local) " el case $el in [Ee]* ) ext; break;; [Ll]* ) loc; break;; * ) echo "Please answer yes or no.";; esac done
    • raulR

      Automating FOG installfog.sh – setting interface, IP, and hostname

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      3
      0 Votes
      3 Posts
      46 Views
      K

      @raul I have an Ansible role which does something akin to what you’re trying to do here:
      https://forgejo.cwavs.xyz/Cwavs/ansible-role-fog it might be worth taking a look and seeing if it helps give you any ideas on how to solve your problem. Happy to answer questions about it.

    • D

      Imaging Log for unregistered hosts

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      3
      0 Votes
      3 Posts
      40 Views
      D

      @Tom-Elliott Really for the purposes of user tracking. It is helpful for us to keep track of who is deploying and capturing. This is purely for transparency and accountability. I can instruct my team to always register devices they are imaging but I cannot force it.

      EDIT: Is there a way to force full reg prior to image deployment? Like a prereq for deployment.

    • J

      Linux Client Install Dual Nics

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Linux Problems
      9
      0 Votes
      9 Posts
      606 Views
      J

      Ok so I now have a second system with the EXACT same issue. I purchased a Dell Precision 7875 which has 2 on-board nics. I updated our dhcp server to issue an IP address for one of the two NICs. With the system connected to that interface I PXE booted the system. The first stage of the fog shows as it notices the system is not registered and asking whether I would like to register the system. Yet once I say do full registration that’s it it will not proceed further.

      So similar to the issue that I’ve raised prior with multiple NICs and @george1421 suggested I PXE booted the system again but went into DEBUG mode. Well as it appears the unused MAC address is now showing up on the interface that I had configured to connect to the network. Seeing that I did not assign an IP address to the second mac address the system would not proceed any further. The odd thing is that BOTH interfaces show up having the same mac address. It seems that there’s an issue with the FOS with newer Dell systems with multiple NICs.

      If I disable one of the two NICs in the BIOS, and do the re-imaging process everything works fine…

      Really looking for a fix for this…

      Cheers

      Jason Naughton

    • S

      Huge database entries number

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      11
      0 Votes
      11 Posts
      518 Views
      JJ FullmerJ

      @siarkowski I believe I have found the cause of this.
      A while back, right after the version you reverted too, we added an improved queueing system which is working perfectly in 1.6. However when we ported it backwards into 1.5.10.x I made a simple syntax error (the wrong $task->id vs $task->get('id') ). I have fixed this in the latest dev-branch.

      This should also greatly improve the experience of the imaging task queue (see also https://github.com/FOGProject/fogproject/issues/736 and https://github.com/FOGProject/fogproject/issues/691) I thought I also wrote a post somewhere in the forum walking through the updated process that fixed some longstanding date math issues, but I can’t find that now.

      Point being, if you would be so kind as to update to the latest dev-branch version and see if it fixes the issue, that would be very helpful.

    • DBailey635D

      FOG 1.5.10.1734 - Kernel panic on Dell Precision 3590 hosts while syncing

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Bug Reports
      1
      0 Votes
      1 Posts
      11 Views
      No one has replied
    • M

      Could Not Mount Issue

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      4
      0 Votes
      4 Posts
      3k Views
      rogalskijR

      @george1421 Thank you for this suggestion. This disabling of “fastboot” worked PERFECTLY! I interrupted the OOBE with Shift + F10 and got the command line window. I shutdown using the “shutdown.exe -s -t 0” command you suggested. Then after booting up, the FOG capture task I had already started took over and it captured 100% as it should have.

      Essentially, I had forgotten to disable fastboot like I normally do on EVERY computer I have. So when it “rebooted” it technically wasn’t rebooting the device since fastboot is a misguided absurd hibernation feature Microsoft developed. The error I got was nearly identical to the one in the original post.

      Thanks so much for this suggestion George and all!

      9d53d15e-eb10-4045-9c90-31f6c156aa7d-image.png

    • L

      Official Docker Container

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      14
      0 Votes
      14 Posts
      7k Views
      8

      I know this is an ancient topic, but I wanted to make sure I updated anybody who was interested in a docker image to my new one.

      please check my post here

      https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

    • E

      Deploy Tasks Not Continuing After First Batch

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      6
      0 Votes
      6 Posts
      898 Views
      JJ FullmerJ

      @eliaspereira This should be fully fixed in the stable release of 1.5.10.x coming on the 15th of this month and in the dev-branch as of now.
      I thought it was already fixed back in September, and it has been working in 1.6 since then but we just got a report of a related issue here https://forums.fogproject.org/topic/18081 which I believe I just fixed.

    • T

      Queue problems when deploying

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      4
      1 Votes
      4 Posts
      583 Views
      JJ FullmerJ

      @tian @DBailey635 @eliaspereira Apologies for missing this post. This was fixed in August-ish of last year, see also:
      https://github.com/FOGProject/fogproject/issues/736

      I found this searching for a post I wrote about it, as I’m pushing another fix for this for a bug just found in 1.5.10.x

      If you update to the latest dev-branch (or what will be stable on the 15th of this month) or give the working-1.6 branch aka 1.6-beta a try, you’ll find the queuing problems fixed.

    • B

      Following a migration, character encoding issue

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      10
      0 Votes
      10 Posts
      338 Views
      B

      @Tom-Elliott

      Great news!

      I updated my server to Debian Bookworm, restarted the Fog installation, and the accent problem disappeared. Awesome!

      Thanks for your help and happy new year 2026, all the best for the FOG project!

    • K

      FOG Secure Boot with Shim

      Watching Ignoring Scheduled Pinned Locked Moved Tutorials
      5
      2 Votes
      5 Posts
      2k Views
      K

      @Florent Thanks Florent. Hopefully it does!

      The issues I’ve listed here do seem to only affect older models of Dell, however UEFI (despite having the word unified in the name) varies wildly by vendor, and even within Vendors, so I wouldn’t be surprised to learn there are similar or different issues affecting newer Dells or even non-Dell machines.

      That said, based on my experience at work. I can’t say I’ve seen too many machines have the number of bizarre issues as I have seen with the older Dell PCs we have.

      As with all things, I’d suggest testing it on some of the machines common in your fleet of computers and seeing what works and what doesn’t.

    • L

      1.6 official release ?

      Watching Ignoring Scheduled Pinned Locked Moved General
      1
      0 Votes
      1 Posts
      60 Views
      No one has replied
    • 1 / 1