• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Fog_Newb
    3. Posts
    F
    • Profile
    • Following 0
    • Followers 0
    • Topics 52
    • Posts 251
    • Best 16
    • Controversial 0
    • Groups 0

    Posts made by Fog_Newb

    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott Fog now tells me the latest dev version and the one I have is 1.5.10.1671

      alt text

      Was 1.5.10.1771 all a bad dream or were we both mistakenly calling 1.5.10.1671 1.5.10.1771?

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott Thanks. I grabbed a full fresh release but haven’t had a chance to reinstall 1.5.10.1771 over itself to confirm the included inits work. But if they are the same inits you posted earlier… it definitely should

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott Awesome sounds good. Another one can be marked as Solved

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott No, but I just did now and it is working! Thank you. So for now, whenever I update FOG, I should copy over that init until it is worked into the dev or release version?

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott Thanks.
      I grabbed the new init.xz and copied it to /var/www/fog/service/ipxe/ and I was still able to capture the an image from the PC with FOG 1.5.10.1667. I updated FOG to the latest 1.5.10.1771 and tried to capture from the PC again and it failed with same error.

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott sounds good!

      posted in FOG Problems
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott

      Yes, I will test these as soon as they are available and have access to the PC, around 2pm EST. Just to confirm, the steps to test would be - update to 1.5.10.1771, then drop the everything into /var/www/html/fog/service/ipxe/ and try to capture again?

      Thanks

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott Should add… I have 2 NVMe drives that are the same size. And since they initialize randomly at each boot, I can’t specify /dev/nvmeXXX
      https://forums.fogproject.org/topic/14822/nvme-madness?_=1753960837885

      At some point, a few years ago, someone said you could use the drive serial number if both NVMe drives are the same size, and it’s been working for a long time now.

      posted in Bug Reports
      F
      Fog_Newb
    • RE: Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      @Tom-Elliott

      Hello Tom,

      Yes, I am using the disk serial number (21297930000130911023) in the Host Primary Disk field. It’s been working fine going on a few years now.

      posted in Bug Reports
      F
      Fog_Newb
    • Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      FOG 1.5.10.1667 to 1.5.10.1771

      Running on Ubuntu 24.04.2 LTS

      Last night, I captured an image from my PC. FOG was version 1.5.10.1667 everything went fine. Today I updated to FOG 1.5.10.1771 then went to test capturing an image from that same PC, no changes were made hardware wise etc.
      This happened. No valid drives found

      NOTE: I use the drive serial number for Host Primary Disk because I have 2 NVME drives which are the same size. <— Could this be the problem?

      alt text

      I bypassed PXE boot and went into Windows fine.

      I restored the FOG server (It’s running in a VM) from a backup prior back to 14 hours earlier version, when it was running 1.5.10.1667. And it captured fine. What is going on!?

      posted in FOG Problems
      F
      Fog_Newb
    • Updated from FOG 1.5.10.1667 to 1.5.10.1771 Fatal Error: No valid drives found "Host Primary Disk"

      FOG 1.5.10.1667 to 1.5.10.1771

      Running on Ubuntu 24.04.2 LTS

      Last night, I captured an image from my PC. FOG was version 1.5.10.1667 everything went fine. Today I updated to FOG 1.5.10.1771 then went to test capturing an image from that same PC, no changes were made hardware wise etc.
      This happened. No valid drives found

      NOTE: I use the drive serial number for Host Primary Disk because I have 2 NVME drives which are the same size. <— Could this be the problem?

      alt text

      I bypassed PXE boot and went into Windows fine.

      I restored the FOG server (It’s running in a VM) from a backup prior back to 14 hours earlier version, when it was running 1.5.10.1667. And it captured fine. What is going on!?

      posted in Bug Reports
      F
      Fog_Newb
    • FOG Dashboard showing wrong date of captured images?

      Fog 1.5.10.1667 Running on Ubuntu Server 24.04.2 LTS

      The PC’s the images were captured from were set to use Windows time.
      The FOG server, tzlocal is set correctly to NY Time and so is fog.

      The 3 images from the 2 PC’s were captured a little past 4:AM July 16th. But the dashboard shows they were captured on the 15th.

      alt text

      The image section under FOG shows the correct date and UTC time the images were captured not local but that isn’t a big deal and I can’t figure out how to change it to show local time.

      alt text

      I set both Windows PC’s to use UTC time, then captured an image again.

      It is 6:19pm July 16th The FOG server and both Windows PC’s know this

      alt text

      But the FOG Dashboard see’s all 4 images being captured on July 15th

      alt text

      The FOG Images section shows it was captured today but doesn’t show local time even though FOG is set to NY timezone

      alt text

      alt text

      posted in FOG Problems
      F
      Fog_Newb
    • RE: Resize Test Failed - Could not adjust bad sector list - But drive is clean

      @Small0145 No, it’s not.

      posted in FOG Problems
      F
      Fog_Newb
    • Resize Test Failed - Could not adjust bad sector list - But drive is clean

      FOG 1.5.10.1667

      Running on Ubuntu 24.04.2 LTS

      I updated to the latest FOG dev version a couple of days ago and tried capturing an image from my PC after installing July 8, 2025—KB5062554 (OS Builds 19044.6093 and 19045.6093) Win 10 LTSC Enterprise

      I got
      This error

      alt text

      alt text

      I ran a chkdsk /x/r/f on reboot, drive came up clean

      https://pastebin.com/KHc6vd59

      Error persists even after running chkdsk /x/r/f, then trying to capture.

      I rebooted the FOG server, then installed the previous version FOG 1.5.10.1660 - Same problem

      Crystal Mark Info shows SMART is good, drive is fine. I restored the last captured image to the PC, ran the Windows Update and tried to capture, same error.

      posted in FOG Problems
      F
      Fog_Newb
    • RE: After updating from .1622 - Could not boot: Result too large - Chain loading failed.

      @Tom-Elliott All good with 1.5.10.1629

      Thanks

      posted in FOG Problems
      F
      Fog_Newb
    • After updating from .1622 - Could not boot: Result too large - Chain loading failed.

      After updating from 1.5.10.1622 to 1.5.10.1625, I went to capture and image and got error message in the subject. Then I saw After updating from 1.5.10.1628 was available so I updated to that, same thing.

      What do?

      posted in FOG Problems
      F
      Fog_Newb
    • RE: FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS

      @JJ-Fullmer @Tom-Elliott

      I’ve found a work around. I now have /images on USB HDD passed through the to VM. When I run a standard back up of the VM via the VM software (Virtualization Station), it only back-ups the OS VM drive.

      For the /images drive - I use a sync program to back-up the files, not the disk .

      posted in FOG Problems
      F
      Fog_Newb
    • How to refresh "Image Size" ON SERVER

      I thought I’d posted about this before but it doesn’t show up in my post history. After capturing an image, Image Size ON SERVER shows as 0 or sometimes 1GB/MB. All the partitions and other information were captured successfully in /images/[imagename] and are the correct size. Once the FOG server is rebooted, Image Size ON SERVER displays correctly.

      Thank you

      posted in FOG Problems
      F
      Fog_Newb
    • RE: FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS

      @JJ-Fullmer said in FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS:

      How big of an issue is this disk size inflation for you?

      It’s not a big deal. I’ve since stopped capturing non-OS drives and now use file sync / mirror program to back those up. I actually like that better than huge image captures once a week. Currently, FOG is just capturing 2 relatively small OS drive images.

      All this is running on a QNAP box someone gave me and QNAP’s Virtualization Station software is lacking features to cleanup/shrink or compact virtual machine disks.

      This all started out as a Feature Request

      https://forums.fogproject.org/topic/17651/local-time-and-alternate-temp-directory-for-capture-option

      It’s odd that linux/php are having this limitation but that’s where we’re at.

      Is this something the devs would change if it was brought to their attention?

      Thanks

      posted in FOG Problems
      F
      Fog_Newb
    • 1 / 1