• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. juelson
    3. Topics
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 4
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by juelson

    • J

      my machine is Dell Latitude 3420

      General
      • • • juelson
      2
      0
      Votes
      2
      Posts
      393
      Views

      george1421G

      @juelson Yes and what didn’t work? From your other thread you are using fog 1.4.4. That should support uefi systems, but it probably won’t see your nvme drives. For UEFI systems you need to send a different boot loader than for bios. For bios, dhcp option 67 should be undionly.kpxe that will pxe boot a bios based computer. For uefi based systems you need to have dhcp option 67 set to ipxe.efi. or snp.efi. Since you are using a really old version of FOG with new hardware you might be out of luck until you upgrade to FOG 1.5.x branch.

      Points of interesting.

      You need to update your FOS Linux kernel to 5.15.x series for the latest hardware support (FOG Web UI -> Kernel update) You need FOG 1.5.9 to update your version of iPXE to the latest version. In the Dell firmware set the disk mode to ahci mode. The default of raid-on will not work with FOG. Disable secure boot in the uefi frimware.
    • J

      erro to deploy Image

      FOG Problems
      • • • juelson
      4
      0
      Votes
      4
      Posts
      353
      Views

      george1421G

      @juelson The output of the commands I asked you to run look normal except the directory listing of /images. There is a missing hidden file that FOG uses to know its connected to the correct image store.

      There should be a file called .mntcheck in both /images and /images/dev This file is created by the fog installer so it should be there unless someone adjusted the contents of the /images directory.

      So we can fix it with the following command. We will fix /images/dev so uploads work correctly while we are at it.

      Key in these commands at the FOG Server’s linux console. You may need to use sudo if you are using a debian variant or do this as the root user.

      touch /images/.mntcheck touch /images/dev/.mntcheck

      This is a non destructive command so its OK to run them even if the file exists. Once the .mntcheck file is created you download should work better.

    • J

      error to captur host no FOG server

      FOG Problems
      • • • juelson
      2
      0
      Votes
      2
      Posts
      126
      Views

      george1421G

      @juelson I’m not exactly sure what you are saying here, so let me reword what I think I understand your issue is using my words.

      I’ve pxe booted and selected full registration to register my computer with FOG. Registration works just find but when I go to deploy an image and create the deploy task, when I pxe boot into the fog the iPXE menu it shows the computer is not registered with FOG. I know it completed registration OK because I can see it in the web ui.

      I know I used more words than you did, but I applied what I think I understood with your issue to ones I’ve seen before. Did I explain the situation you see now?

    • 1 / 1