Image capture size mismatch
-
Hiyall,
I have 15 machines - same model, SSD brand etc.- which I have started imaging. Drives are all 120GB, and halfway through there is one host that is imaging 119GB - the rest are all 20GB. I can find nothing abnormal with this system, but am unsure what to look for that would explain this. Have retried the capture and same result - just this system.
-
@Corrco said in Image capture size mismatch:
Drives are all 120GB, and halfway through there is one host that is imaging 119GB - the rest are all 20GB.
This doesn’t make sense to me. Can you please explain what you mean by these numbers? Maybe post pictures and screenshots of the sizes!
-
I have 15 identical systems. All have the same size 120GB SSD drives and only one partition. All have the same W10 build. I have imaged roughly half of them, and the size of the image is always under 20GB. One of the systems is imaging at 119GB. I am doing the same steps each time. Don’t know what’s wrong with this one station!
I have tried to upload a picture and I get “sharp” errors.
-
@Corrco Sorry this topic has been kind of lost probably when we had some issues with the forums not long ago.
The only thing I can imagine is the partition cannot be detected and captured as NTFS. In this case FOG uses RAW mode which will result in a much larger image file. This could happen if the drive is encrypted with Bitlocker or some other forms of disk encryption. Though we added a check for Bitlocker a fair while ago and it should print a message and bail out.
Please post your FOG version and let us know if you need further help.