Posts made by Fog_Newb

@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.

I ran chkdsk prior to capturing and it came up clean

UPDATE: So I tried everything for the ntfsresize error … turns out, I had to shrink the partition in windows a bit then expand it. After that, I could capture.

@Tom-Elliott

Some additional info. I believe I was able to successfully capture an image of this PC right after updating to 1.5.10.1688. on Aug 26th. I am restoring a back up FOG from that time to a new VM to see.

UPDATE: So I restored the FOG server back up from a couple of days ago to a new VM and yes, I was able to back up the PC once after updating to 1688.

@Tom-Elliott

Here it is. It is packed

error.log

I updated to 1.5.10.1688 and attempted to capture an image. Win 10 resizable whole disk. It captured the main partition then failed at some point. I couldn’t see the error on the screen. The drive is now too borked to boot into Windows. So I tried to deploy an image I took before the update to the PC but was unable to check in

An idea on how to fix?

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

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

@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

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

@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?

@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.

@Tom-Elliott sounds good!

@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

@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.

@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.

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?

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!?

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?

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!?

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.

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.

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

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

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

@Small0145 No, it’s not.

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

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.

@Tom-Elliott All good with 1.5.10.1629

Thanks

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,

What do?