You all must remember. I’ve added support for GPT and MBR since the release of 1.0.0. 0.32 and below only allowed MBR style disks to be imaged. Many times, I’ve seen now, that FOG is actually trying to create non-existent image files because the disk is setup in a particular manner but the partition table doesn’t match up. Meaning it’s creating non-existent partition where there really shouldn’t be any partitions. Because of this, fog can’t find the partition or write to it so it skips that partition and continue’s on in the process. In the case of GPT when expecting MBR, the data never has a place to be written to so it just “complete’s” while no information has actually been written. Please verify this by running a debug task and checking your system against fixparts, or in the case you intend to maintain GPT tables, make sure the data is where it is expected to be.
