• How to insert pre-deployment scripts ?

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    511 Views
  • 0 Votes
    2 Posts
    198 Views
    DBailey635D

    Also occurring on Dell Latitude 5450 laptops.

  • Fog 1.6.0-beta.2268 Could not verify mount point

    Solved Bug Reports
    2
    0 Votes
    2 Posts
    154 Views
    S

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

  • 0 Votes
    2 Posts
    565 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.

  • 0 Votes
    8 Posts
    642 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.

  • 0 Votes
    6 Posts
    884 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?

  • Ubuntu version to be used for FOG v1.5.10.1734

    Unsolved FOG Problems
    4
    0 Votes
    4 Posts
    767 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.

  • 0 Votes
    7 Posts
    498 Views
    S

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

  • Configure iVentoy as netboot-Option in boot menu

    Tutorials
    7
    1 Votes
    7 Posts
    9k Views
    J

    I am very interested in doing this. I have a working FOG server which is working in my home network with no mods to my router which is a Firewalla gold if it matters. I have several FOG menu items that work but I am finding it increasingly harder to keep them up to date, for example parted image, which I can’t get to work with the latest versions despite reading alot of stuff in the forums. I also created a ventoy USB which also seems to work with what I have added to it so far with a few exceptions but having it all be in PXE would be even better since it is centrally located. The problem I have run into with FOG booting ISOs almost always comes down to the size of ISO though. Does iventoy via PXE solve that by any chance? I can also pull apart the ISOs but then I am micromanaging and spending hours getting it all to work which I am trying to minimize. I like the nerdyness of it all but I have enough other nerdy projects for now. lol. Dropping ISOs into iVentoy PXE would be super simple. If anyone else has done this, could you post your configs for FOG please? I really prefer to not make changes to my Firewalla if possible. FWIW, I have wired ethernet throughout the entire house which made PXE booting pretty easy.

  • 0 Votes
    6 Posts
    2k 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

  • Could Not Mount Issue

    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

  • Official Docker Container

    Feature Request
    14
    0 Votes
    14 Posts
    8k 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

  • Linux Client Install Dual Nics

    Unsolved Linux Problems
    9
    0 Votes
    9 Posts
    850 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

  • Snapin Pack Arguments double-quotes problem

    Solved FOG Problems
    13
    0 Votes
    13 Posts
    2k Views
    Tom ElliottT

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

  • FOG Portable

    General
    3
    0 Votes
    3 Posts
    322 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
  • Deploy Tasks Not Continuing After First Batch

    Unsolved FOG Problems
    6
    0 Votes
    6 Posts
    1k 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.

  • Queue problems when deploying

    Unsolved FOG Problems
    4
    1 Votes
    4 Posts
    688 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.

  • Following a migration, character encoding issue

    Solved FOG Problems
    10
    0 Votes
    10 Posts
    1k 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!

  • HD info not populating in log

    Unsolved FOG Problems
    22
    0 Votes
    22 Posts
    2k 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.

  • 0 Votes
    3 Posts
    280 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.