@browlry Looking at the information provided I also find it surprising that you seem to be left with an MBR partition layout on the destinations machines! FOG uses the information in d1.partitions
, d1.minimum.partitions
(only when image is of type resizable) and d1.mbr
file to re-create and adjust the partition layout. The contents of d1.partitions
you posted clearly show a GPT style partition layout and I suspect d1.minimum.partitions
to be the same! I reckon the d1.mbr
file to still have some old style MBR information in it that is confusing FOS.
Possibly it’s those commands from your scripts that create the “mess” but I am not sure.
select disk 0
clean
convert gpt
Why do you actually need to convert to GPT at all I wonder? Make sure the disk is being properly cleaned (I don’t know if MS diskpart is doing a good job) and create a fresh new GPT partition layout from scratch. George is right about the first partition being “abnormal”. I would not think this is causing the issue as described but that’s just me guessing.
If you don’t want to mess with your master image we can still take a look at the d1.mbr
file (it’s binary, upload to a file share and post a link here) and see if we can help you fixing it.