Subcategories

  • Technical help directly related to FOG.
    9k Topics
    85k Posts
    Tom ElliottT

    @AUTH-IT-Center I added another update but the error you’re seeing is a little strange because it should’ve bene addressed, I don’t know. The min() item is saying it requires a value and the approach I took was to check if there is data in the array, pass it to the min funciton otherwise set it to null (which should work if true)

    Of course i don’t have much time to dig deep into this today, but my testing seemed to work without much issue.

    Let me see if I can create a host without an image associated, tie a snapin and make a snapin task.

  • Problems with specific computer models.
    710 Topics
    8k Posts
    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.

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    G

    Hi Again guys

    I have some news about this problem.
    I found a work around.

    I change the file d1.fixed_size_partitions deleting the recovery Windows partition. This change generated and error when I made the deploy image in Client PC.
    But if I cancel the job in the CLI fog server and reset the client machine after fog show the error
    It boot ok.

    I’ll continue reading …
    Thanks

  • Technical help related to a Linux Problem.

    726 Topics
    6k Posts
    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

  • Technical help related to a Mac Problem.

    80 Topics
    942 Posts
    B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    682 Topics
    5k Posts
    R

    @george1421
    to be adding some to this topic since our system was broken again with the same problems.

    I updated recently to newer fog version (1.5.10.1751 and today to 1.5.10.1754) and that seems to break it again.
    I noticed that updating also starts using latest Initrd. (2025.02.4)

    Things are broken with latest Initrd. I set it back to 2024.02.9 AMD/Intel 64 bit and it is working again.
    Then i updated Initrd to 202502.0 AMD/Intel 64 bit and it is still working.

    Strange thing is that in webinterface the latest version is shown multiple times.
    When I open and download the upper one during pxe boot I see version 20251221 loaded. That one is not working.

    Is there anywhere to analyse what the differences are?

    I also want to add that we were focussing on nvme. But VROC doesn’t seem to work with nvme in raid.
    There are sata ssd/nvme in those slots.

    4bcbb845-8bb5-458c-b27a-8794b9b0a5b6-afbeelding.png

164

Online

12.5k

Users

17.5k

Topics

156.2k

Posts