The disk contains an unclean file system (0, 0)

[willian]

I have a Fog installation (1.5.6) and am having trouble trying to capture a Windows 10 image. I created the image in a VM and ran Sysprep.
Two months ago I had done an installation with version 1.5.5 and gave the same problem, but I had managed to solve, I just can not remember how

Thanks.

[EduardoTSeoane]

Hi @willian
With this screenshot I think you have problems with the dirty bit or the hiberfile mark on ntfs block device /dev/sda1.

You can do something like:

on the fog.postinit script

if [[ ${osid} -eq 9 ]]
then
ntfsfix -d /dev/sda1
## Begin put here the rest of ntfs partitions if you want

## End
mount -t ntfs-3g -o remove_hiberfile  /dev/sda1 /mnt
umount /mnt
fi

This is the idea. I have code like that in my fog.postinit and fog.postdownload script to grant access to the file system to deploy drivers and hostinfo data on fog.
Can you repeat on every ntfs partition.
Maybe it works.

[willian]

@EduardoTSeoane Thanks a lot for the help.

I made the changes to the file you mentioned and it worked, but a question if you can help me, in the attached print shows that /dev/sda4 is being cloned, only 13.3GB of space was used in the image I made, but apparently it is being cloned the partition in its total size 135.7GB and is taking a long time to finish. Is this right?

[EduardoTSeoane]

@willian
yes its right.

If you read the screen with attention partclone retrieves
Device size (partition size)
Space in use
And
Free space.

[Sebastian Roth]

@willian As well make sure you read all this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

[willian]

Hello @Sebastian-Roth

Yes, I saw it, but since I used sysprep to make the image, I thought that there would not be that problem.

[willian]

Guys, I came back because I think there’s still something wrong with the image capture I’m doing.

Somehow I can now capture the image without appearing the error I posted in the attached image, I commented the lines I had added fog.postinit script (provided by @EduardoTSeoane ) and nothing else, and now the capture normally occurs, but I still see a problem due to the fact that the whole disk is being uploaded instead of just the space that was used. So I read, it could be something related to Fast Boot, Hibernation or BitLocker, but as the image I made is coming from a VM, then I do not see how this could happen, other than that, the image type is as Single Disk - Resizable .
Was there anything else that could cause this?

Thanks.

[Sebastian Roth]

@willian said in The disk contains an unclean file system (0, 0):

So I read, it could be something related to Fast Boot, Hibernation or BitLocker, but as the image I made is coming from a VM,

Why should those not be related in the context of a VM? Please make sure Windows 10 Fast Boot is disabled! As well run manage-bde -status C: (ref) in an admin cmd window to see if BitLocker is enabled. Then use shutdown -s -t 0 (ref) to properly shut down the VM before capture!

[willian]

@Sebastian-Roth but there is no Fast Boot option in the VM, and BitLocker is disabled.

And I think the VM is properly shutdown when I run sysprep.

[Quazz]

@willian Fast Strange, there should be more options in the top left corner for power mangement, something like “Actions to take when closing lid”, thats where fastboot option is located.

[willian]

@Quazz yeah, but as it is a VM, I think there is no such option.

[willian]

I don’t know what happened but now it’s just capturing used space.