Went through and imaged a new laptop with a 1703 image was able to make some changes and take an image from 1703 just fine. Upgraded to 1709 and got the same inode error, something must have change I’m going to try to sysprep the image to see if that helps but sysprep has been failing for me on 1709 as well.

@sebastian-roth

It was after I removed the previous Windows version is when I had issues. I could take an image after upgrading to 1709 but when I went to clean out the previous windows version the next attempt to take an image would fail. I would say this happened about 4-5 times with different PCs (same model) before I pin pointed what step caused the image to fail.

Steps for me were like this.

1. Win10 machine with 1703 - Image Success
2. Upgrade to 1709 - Image Success
3. Remove old patch data - Image Success
4. Remove previous Windows version - Image failed

I removed the patch data and previous Windows install via Disk cleanup > Cleanup system files.

@sebastian-roth Yes I’m able to reproduce this. Clean install upgrade to 1709 test capture > Windows cleanup to remove old patch data and previous versions of the OS.

The cleanup is done with windows disk cleanup.

Another update is that I am able to take an update with the “Multiple Partition Image - Single Disk” image type. I would prefer Single Disk Re-sizable but it always failed.

These settings are working for us to capture 1709 images.

I have some more info on this, it seems to only happen for me after I remove the old Windows versions from a PC I want to take an image of. A freshly updated PC to 1709 will have no issues until you try to cleanup those files. Which is annoying because they take up about 30gigs of space.

Went through and imaged a new laptop with a 1703 image was able to make some changes and take an image from 1703 just fine. Upgraded to 1709 and got the same inode error, something must have change I’m going to try to sysprep the image to see if that helps but sysprep has been failing for me on 1709 as well.

@sebastian-roth Tried your suggestions still having no luck, I’ll look at some of the other posts on the forums and see if I can find anything that works.

I’ve confirmed that fast boot is disabled and I am still getting the error.

FOG Verision: 1.4.4
Server: Ubuntu 16.04
Client Windows 10 (1709 Fall update)
Image: Single Disk - Re sizable, Everything, Partclone Zstd Compression 12

I’m getting the attached error when trying to take an image from a client after the Windows version 1709 update. I’ve used this model of PC to take images in the past before so I don’t think its a hardware issue.

https://imgur.com/a/vrhGk

Bitlocker must have kicked off at some point it was encrypted but it hadn’t generated a key or locked the drive yet.

My fog is version 1.4.4, same model of laptop with the exact same innards. I take images before bitlocker is enabled but I will take another look at this.

I’m having an issue where FOG seems to be imaging the blank space on a drive. I attached a screen shot that shows I took three images of the same PC with the same settings yet two of them came back with an on client size at 238GB. On the server its only about 50GB so it’s not a huge issue but it does seem to be slowing down the imaging process. I also noticed that it said the file type was ‘RAW’ when taking/laying down the image vs NTFS etc. Just wondering why taking an image off the same hardware with the same settings is getting me two very different images.