Unable to Capture an image: ERROR: Could not adjust the bad sector list

[jfink-jpg]

Hi Fog Support Community,

I am all of a sudden having an issue capturing an image the error is

Error: Could not adjust the bad sector list
(ShrinkPartition)
Args Passed: /dev/sda3 /images/00155d0a050f/d1.orignal.fstypes 1:2:4:5

I have tried the following
chkdsk via both the command prompt and windows media
Updating FOG to the latest
Change the Kernel Version
chat CAPTURERESIZEPCT to 15

Still no go, I am able to deploy my old image still but not capture

I still have plenty of disk space

any help would be great.

[jfink-jpg]

This looks to be an issue related to the latest windows update. When I used an older image from October everything worked

[darksidemilk]

This looks like a hardware specific issue for the machine you're capturing from. Have you tried capturing from a different machine or VM? Have you tried to run chkdsk or booting it to a linux live cd and trying to run fsck?
Or are you saying you reinstalled the october iso and made the image that way and everything was fine on that machine?

[jfink-jpg]

Its a Windows Hyper-V VM that I update a few times a month and take a new Fog image. My Fog Backup image capture from October worked, so I just deployed that image to my VM updated the files on there and recaptured. I am fully back up and working using that image as my base.

So something happened to the VM over the month of November that made the Fog capture VM to fail.

I have tried a check disk using the following methods
Windows ISO Check Disk
Check Disk built into Windows
Check Disk Using GParted

All came back clean.

I am guessing its a windows update that is causing this as its the only thing that makes sense at this point, I am just happy I had the October backup that I could use to update my image.

[darksidemilk]

Is this happening with windows 11 25H2 or windows 11 24H2?

[mastacontrola]

This one dies inside ntfsresize: the resize test gets as far as "Updating $BadClust file" and fails truncating the NTFS bad-cluster file, on a volume chkdsk reports clean. That code has not changed upstream since the ntfs-3g release FOS ships, so it is not something a package update fixes, and the real resize would fail the same way.

FOS now handles it (FOGProject/fos#174): when the resize test fails with that message the partition is recorded as fixed size and captured at its present size, the same thing the "not resizable" image type does for the whole image, applied to that one partition. The capture completes; the image cannot be deployed to a smaller disk than it came from.

If you still have a VM in that state, the experimental init at https://github.com/FOGProject/fos/releases/tag/EXP_20260902-204611 has the change. Put its init.xz in /var/www/html/fog/service/ipxe/ on the server (keep a copy of the current one) and recapture. The console should show "Not resizing filesystem ... cannot adjust its bad sector list" and then carry on.