A couple images won't shrink/resize on capture..
-
I’ve captured most of the boxes around the house, but a couple of them don’t appear to resize. FOG tells me I’m capturing 232GB images.
During capture the bar says it is basically done at 122GB.
Image lists show it at 232GB
The folder shows something like 42GB
I’ve run cleanup, chkdsk, & defrags. These boxes aren’t encrypted.
Any tips to get these to behave/report properly?
-
I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.
Nice thought, but the thread you note doesn’t hold my solution.
https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Bit locker is off as evidenced by the encryption control commands.
manage-bde -off
manage-bde -status“Way 1” from the FOG wiki made no change either.
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_BitI believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.
-
@geardog When the image is being captured by fog. Look at the partclone screen. My bet is that it is being captured in RAW mode. If that is the case my bet is that bitlocker is enabled on that disk, even if you have it never turned on to start.
ref: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Please run through the commands by @THEMCV and recapture again. Disk encryption will stop it from shrinking the disk
-
I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.
Nice thought, but the thread you note doesn’t hold my solution.
https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
Bit locker is off as evidenced by the encryption control commands.
manage-bde -off
manage-bde -status“Way 1” from the FOG wiki made no change either.
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_BitI believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.
-
@geardog Excellent job finding the problem!! Is it ok to close this case then?
-
I consider it resolved. Thanks for chiming in.