• 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
      823 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.

    • S

      Huge database entries number

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      11
      0 Votes
      11 Posts
      749 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.

    • B

      Following a migration, character encoding issue

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      10
      0 Votes
      10 Posts
      551 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!

    • D

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

      Watching Ignoring Scheduled Pinned Locked Moved Hardware Compatibility
      8
      0 Votes
      8 Posts
      222 Views
      george1421G

      @djgalloway Just to add a bit of detail here. All of the work you did was on the iPXE side, which is great work by the way. The kernel driver I updated was after you select an FOG iPXE menu item that is when bzImage is loaded and run. It relies on kernel parameters that is provided by iPXE to find the root file system. This is technically what you fixed by ensuring that default.ipxe/boot.php from the fog server was being called. At the end of the day, I’m glad you got that working because your setup is definitely an edge case that works well in your environment.

    • S

      Fog 1.6.0-beta.2262 Create Task successful but no Active / Scheduled Task

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      7
      0 Votes
      7 Posts
      137 Views
      S

      Can you help me with bug topic ?
      Fog 1.6.0-beta.2141 remove folder with image

    • F

      Clients Booting into FOG are Met With "Attempting to check in......failed"

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      6
      0 Votes
      6 Posts
      225 Views
      F

      @Tom-Elliott Alrighty. So my FOG server at another location is acting up in the same fashion with the failure to check in.

      Before we used it I updated to 1.60-beta.2265 to hopefully negate it but I did not drop the fog table from mysql before doing so.

      Are there any logs you want me to pull?

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

    • T

      Failed to update/create image log

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      4
      0 Votes
      4 Posts
      183 Views
      Tom ElliottT

      @The-Dealman they auto build every month. On the 15th of the month. So technically it already is backported. Dev-branch is the branch meant to fix the bugs reported. These then roll up into stable automatically on the 15th.

    • A

      Ubuntu version to be used for FOG v1.5.10.1734

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      4
      0 Votes
      4 Posts
      163 Views
      A

      Was not sure which ubuntu version of these (20.04, 22.04, or 24.04) was used as the basis for the FOG release v1.5.10.1734.

      Thanks, @FOGBreaker101, for the version you are using.

      Some software doesn’t use the latest released version of the OS distro, but often one major version back.

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

    • J

      FOG Portable

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      120 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
      112 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
      55 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.

    • R

      Docker image and external Mysql database extension

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

      @ramone

      I got your message on the github repo. In regards to the DHCP issue, I’ve updated the code and it should work now. Please test and follow up in the issue thread. Please note that some of the variables in the .env file have changed so you might want to review that before starting it up.

      thanks!!

      88

    • DBailey635D

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

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Bug Reports
      2
      0 Votes
      2 Posts
      46 Views
      DBailey635D

      Also occurring on Dell Latitude 5450 laptops.

    • S

      Fog 1.6.0-beta.2268 Could not verify mount point

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Bug Reports
      2
      0 Votes
      2 Posts
      30 Views
      S

      @sgennadi
      Fixed by
      touch /images/dev/.mntcheck

    • S

      Fog 1.6.0-beta.2141 remove folder with image

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Bug Reports
      3
      0 Votes
      3 Posts
      343 Views
      S

      Problem exists also with latest 1.6 builds…
      I think problem something in my database…
      When fog competed image early I see failed to update database… latest version no error but folder with previous version of image removed

    • A

      could not verify mount point, check if .mntcheck exists /bin/fog.download

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      106 Views
      george1421G

      @alperi The bit if detail you are missing is what the kernel parameters were that was sent to the fog client. From what you posted it appears that the FOG server has all of the bits in the right spots.

      In the kernel parameters that are passed to bzImage during boot up it lists where the FOS engine can find the deployment server. I would verify the IP addresses are correct. If everything appears correct with the parameters, we can debug this a bit more by debug deploy and then manually interact with the fos engine from the target PC’s console.

    • J

      Linux Client Install Dual Nics

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Linux Problems
      9
      0 Votes
      9 Posts
      646 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

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

    • 1
    • 2
    • 1 / 2