Error capturing Win 10 image after updating to the latest dev version - Resize Test fails

[Fog_Newb]

Hello,

I have been capturing images of my OS drive every few days for a while now. The last capture was on the 14th. Two days ago I updated the dev branch to1.5.9.122 and when I tried to capture from the OS drive,a few minutes ago and got an error. chkdsk shows the drives is clean. The error was …Not enough MFT space. I so I did a debug and captured. I have no idea where the debug log is located, I just see the usual FOG Linux Service Logs which don’t have any info about the error I could find.

I have some pics though.

The system has 2 NVMe drives so the host primary disk is set to the drive size (250059350016)

I’ve since run Privazer on the Win 10 drive and cleaned the MFT and $Logfile but the same error occurs. Although it does notate a different New Volume size

[Sebastian Roth]

@george1421 said in Error capturing Win 10 image after updating to the latest dev version - Resize Test fails:

Would it just create a larger disk image?

Yes exactly.

If yes then 7 or 8 might be a good start if size is the only penalty.

Ok, will 7 do for now.

[george1421]

@sebastian-roth said in Error capturing Win 10 image after updating to the latest dev version - Resize Test fails:

Should we go to 7, 8 or even 10

So I have to ask, what are the risks for going too large?

Would it just create a larger disk image? If yes then 7 or 8 might be a good start if size is the only penalty. I think 5 was picked ages ago when smaller disk size was common. It appears that modern operating systems need a bit more headroom to start up.

[Sebastian Roth]

@george1421 said in Error capturing Win 10 image after updating to the latest dev version - Resize Test fails:

Yes FOG default has always been 5%. The devs may need to revisit this decision for FOG 1.5.10 since it appears that current MS OS’ needs a bit more space than previous versions.

Sure we can increase the default for new installs. Should we go to 7, 8 or even 10?

[george1421]

@fog_newb Yes FOG default has always been 5%. The devs may need to revisit this decision for FOG 1.5.10 since it appears that current MS OS’ needs a bit more space than previous versions.

[Fog_Newb]

@george1421

Thanks. Setting it to 7 did the trick. Was the default always 5 or… ?

[george1421]

@fog_newb Lets see if we can clear that MFT error.

Please check in FOG Configuration -> FOG Settings -> General Settings -> CAPTURERESIZEPCT.

The default is adding 5 % and you can increase that as much as you like up to 99%. What is going on is FOG is squeezing the disk to make it as small as possible for capture. Sometimes it squeezes too much air out of the disk not leaving room to move things around. Increasing the CAPTURERESIZEPCT leaves a little free space left on the disk to move things around. Try 7 or 10% to see if that is enough. Once you update this value you will need to recapture your golden image.