@george1421

I did it !!

So I basically made a Frankenstein’s monster version of my image.

As I’ve stated in my last comment, I had an issue where the windows drive did not have the same partition number.

I created a new legacy windows 10 VM, with a smaller C Drive than I created the very first time I worked on that image. I converted that installation into UEFI.
So now my newly installed win10 and my oversized image have the exact same disk structure.

I deployed the partition containing all my data onto the new VM, and I had an issue where the UEFI boot was broken.

I used the tools in the installation media to repair the EFI partition. I used diskpart to assign a letter to the EFI partition, exited diskpart and ran this command :

bcdboot C:\Windows fr-fr /s B: /f

Windows booted.
Now I’m capturing the image and I’ll deploy it to make sure it’s working fine
Thanks for all the help and ideas!!

Regards,
Dan

@george1421

I did it !!

So I basically made a Frankenstein’s monster version of my image.

As I’ve stated in my last comment, I had an issue where the windows drive did not have the same partition number.

I created a new legacy windows 10 VM, with a smaller C Drive than I created the very first time I worked on that image. I converted that installation into UEFI.
So now my newly installed win10 and my oversized image have the exact same disk structure.

I deployed the partition containing all my data onto the new VM, and I had an issue where the UEFI boot was broken.

I used the tools in the installation media to repair the EFI partition. I used diskpart to assign a letter to the EFI partition, exited diskpart and ran this command :

bcdboot C:\Windows fr-fr /s B: /f

Windows booted.
Now I’m capturing the image and I’ll deploy it to make sure it’s working fine
Thanks for all the help and ideas!!

Regards,
Dan

@george1421

There’s an issue when deploying.

First, I’ll tel you what I’ve done exactly :

1. I capture the specific partition containing the fully installed windows 10 (it was on /dev/sda2). I used the option Single Disk - Resizable, Partition 2 only

2. I installed a brand new virtual machine in UEFI from the get go to get a proper disk structure, I remove the last partition

3. I created the deploy task, and that’s when the problom occurs : since the partition captured wad /dev/sda2 , the task is trying to deploy over the /dev/sda2 of the new installation, and if I change the partition number in the web GUI for the image, I have an other error message telling me that there is not partition with that number to deploy in the image.

Is there a way to tell fog to deploy a partition that was /dev/sda2 over a new one that is /dev/sda3 ?

Regards,
Dan

@george1421

Thank you for taking the time to make this a bit clearer to me.

I’m trying this right now.
I just hope the fact that the C Drive partition will not have the same number won’t be an issue (it was /dev/sda2 on the completed install, and will be /dev/sda3 on the new one if all goes well)

It really feels like surgery

I’ll keep you updated on how it will go (you’ll probably here from me tomorrow)

Regards,
Dan

@george1421

If I understand you correctly :

1. I create a new VM with a brand new Win10 install for the disk structure.
2. I remove the last partition, and it should normally be the recovery
3. I capture the C Drive partition where I have installed everything I need (I capture this specific partition)
4. I deploy that partition on the brand new install of Win10, writing over the empty C Drive

I’m not sure that’s exactly what you said, hence my question to confirm the steps

@george1421 yeah I know, I believe it’s because the image was originally in Legacy mode, and I converted it to UEFI (using mbr2pgt), so the EFI partition was created last.

@george1421 the partition causing all the trouble is the EFI system one
If i remove it entirely, my OS won’t boot at all, will it ?

@george1421

OK thanks for your anwser.
I’ll get working on a new image then since time is of the essence here.

I’ll keep an eye on this thread and try out ideas thrown here.
If my problem can be used as a template on how to resolve this issue, it might help others as well.

Regards,
Dan

@Sebastian-Roth @george1421

Do I just need to change the start value in both files (d1.partitions and d1.minimum.partitions) for /dev/sda3, and the size value of /dev/sda2 in d1.partitions ?

Regards,
Dan

@Sebastian-Roth

Here’s the content of the d1.minimum :

label: gpt
label-id: 38CF0A2B-CD00-11EA-B7E0-000C29541530
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 536870878
sector-size: 512

/dev/sda1 : start=        2048, size=     1185792, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=38CF0A28-CD00-11EA-B7E0-000C29541530, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda2 : start=     1187840, size=   282008362, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=38CF0A29-CD00-11EA-B7E0-000C29541530
/dev/sda3 : start=   536662016, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=38CF0A2A-CD00-11EA-B7E0-000C29541530, name="attrs=\x22GUID:63"

EDIT: bad copy paste, sorry

@george1421

There it is :

d1.fixed_size_partitions :

1:3

d1.partitions :

label: gpt
label-id: 38CF0A2B-CD00-11EA-B7E0-000C29541530
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 536870878
sector-size: 512

/dev/sda1 : start=        2048, size=     1185792, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=38CF0A28-CD00-11EA-B7E0-000C29541530, attrs="RequiredPartition GUID:63"
/dev/sda2 : start=     1187840, size=   535474176, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=38CF0A29-CD00-11EA-B7E0-000C29541530
/dev/sda3 : start=   536662016, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=38CF0A2A-CD00-11EA-B7E0-000C29541530, attrs="GUID:63"