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

      Failed to update/create image log

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      42 Views
      Tom ElliottT

      @The-Dealman Can you switch to dev-branch and do a pull and test?

      Unfortunately I’m working out of two different branches as my focus has been mainly on working-1.6 and I had to fix a similar issue there. Forgot to do it as part of when the working-1.6 was reported. My apologies.

      This should be addressed in the latest of dev-branch.

    • A

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

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      1
      0 Votes
      1 Posts
      15 Views
      No one has replied
    • D

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

      Watching Ignoring Scheduled Pinned Locked Moved Hardware Compatibility
      7
      0 Votes
      7 Posts
      165 Views
      D

      Here is the working config

      # detect iPXE dhcp-userclass=set:ipxe,iPXE dhcp-match=set:ipxe,175 # FIRST STAGE: UEFI firmware -> iPXE using SNP dhcp-boot=tag:fog,tag:!ipxe,tag:!maas,snponly.efi,10.20.192.13,10.20.192.13 # SECOND STAGE: iPXE -> FOG (give it the script directly) dhcp-boot=tag:fog,tag:ipxe,tag:!maas,default.ipxe,10.20.192.13,10.20.192.13

      Factory default.ipxe.

      I think deleting autoexec.ipxe was the missing piece a la https://forums.fogproject.org/topic/17937/uefi-boot-kernel-panic-unable-to-mount-root-fs-on-dev-ram0/9?_=1768445663029? Unfortunately, I tried so many different things that I am afraid to try to reproduce the failure and not be able to get back to a working state.

      Regardless, it was not a missing NIC driver as I originally suspected. Thank you for your help nonetheless.

    • 1 / 1