Help with GPT partitioning

[scosta]

Hello guys, and sorry if this is the wrong place for this kind of question. I’ve been working on a Windows 10 Golden Image on a VM with a 200Gb HD, one partition for the SO and another for Data. As soon I finished building it, I did the capture with FOG, version 1.5.5.

Now I’m in the phase of deploying and testing the image against our hardwares, and one of them has a hd of 120Gb, wich is presenting problem on deploy, some error in the moment of restoring the GPT table.

My guess the problem involes the GPT partition being in the end of the disk, but I would like an insight from you guys, and if there’s any ways of making this work without restart building my image from scratch. Here follows the infos on the capture files and the error screen.

d1.partitions:

label: gpt
label-id: 594FBEB8-B041-4144-93F7-E40896645CC8
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 419430366

/dev/sda1 : start=        2048, size=   218431488, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CA86F564-26DF-4F24-892B-8D895CA56995, name="Basic data partition"
/dev/sda2 : start=   218433536, size=   200585216, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=734653A0-99BF-4CE4-B30C-B56E2C63F1BF, name="Basic data partition"
/dev/sda3 : start=   419018752, size=      409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B808A8E-70C8-4555-B027-31D0FAED65F8, name="EFI system partition", attrs="GUID:63"

d1.minimum.partitions

label: gpt
label-id: 594FBEB8-B041-4144-93F7-E40896645CC8
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 419430366

/dev/sda1 : start=        2048, size=    40209666, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CA86F564-26DF-4F24-892B-8D895CA56995, name="Basic data partition"
/dev/sda2 : start=   218433536, size=     4442810, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=734653A0-99BF-4CE4-B30C-B56E2C63F1BF, name="Basic data partition"
/dev/sda3 : start=   419018752, size=      409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B808A8E-70C8-4555-B027-31D0FAED65F8, name="EFI system partition", attrs="GUID:63"

d1.fixed_size_partitions

:3

d1.original.fstypes

/dev/sda1 ntfs
/dev/sda2 ntfs

Any insights if my conjectures are right, and if theres any way to fix it, would be very welcome
Thanks again in advance

[Sebastian Roth]

@scosta said in Help with GPT partitioning:

I’m in the phase of deploying and testing the image against our hardwares, and one of them has a hd of 120Gb, wich is presenting problem on deploy

The start sector of your third partition is 419018752 as we see in the partition layout files. This means that you can deploy this particular image only to disks being larger than 200 GB (419018752 blocks * 512 bytes blocksize / 1024 / 1024 / 1024).

Why is you EFI boot partition (type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B) at the end of the disk? It’s quite strange. Did you do this install yourself?

[scosta]

@Sebastian-Roth said in Help with GPT partitioning:

Why is you EFI boot partition (type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B) at the end of the disk? It’s quite strange. Did you do this install yourself?

I did not. Unfortunally I got a base image to work with from higher ranks of my organization to work with. If it was all my work from scratch, I would never do this nosense. Do you think is there any way to move the EFI boot partition to the beggining of the disk without compromising the entire system or I’m doomed to restart from scratch?

[Quazz]

@scosta You can rearrange partitions. I would use something like macrium reflect to create a clone to an identical disk where I manually arrange the partitions, you can then use that disk for capture in FOG, once that is done, you can deploy it to the original disk and see if everything works.

There’s probably other ways or even faster ways, but messing with partition tables can be scary.