error trying to restore gpt partitions tables
-
Hi,
I create an image with one of my computer, it’s a HP ProDesk 4000 G2 MT with windows 10. On this computer i can capture and deploy my image with no problem but when i want to deploy this image on the others computer (same model) i have the error "error trying to restore gpt partitions tables (restorePartitionTableAndBootLoader)
I try with two type of image Single Disk rezizable and Multi partition - single disk not rezizable and the error is the same, i try to fix with the other post who have the same error on the forum but nothing could help me.
here the error screen :
https://cloud.fairy-family.fr/index.php/s/EbWCzy3LLdtsRW7Thank for reading, sorry for the english is not my language and i have some difficulties with it.
fog version : 1.5.9
-
@btoffolon Is the disk of the deploy machine smaller than the disk you capture the image from?
Please post the contents of the text files
d1.partitions
(andd1.minimum.partitions
if the image is set to resizable) of this image here in the forum. You find those file(s) in/images/salletechno/
on your FOG server. -
@sebastian-roth Hi Thanks for the reply.
no the disk is not smaller it’s why i would create a rezizable image i thought it was a good way but maybe i’m wrong ?
i post the contents here :
salle techno(not rezizable image) d1.partitions :
label: gpt label-id: 79FE4766-EDD2-4DD0-826C-6DD816A2E7C6 device: /dev/sda unit: sectors first-lba: 34 last-lba: 976773134 sector-size: 512 /dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5217DE87-4A45-4AC4-A4DD-0C8EB1C5CF5B, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=15C5E73F-7855-4DA4-A464-4694B0E56628, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 239616, size= 975486976, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=E130C384-3F46-4D8F-AD25-B85FDB0127CD, name="Basic data partition" /dev/sda4 : start= 975726592, size= 1046528, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D3FA37D6-10A7-4303-976C-6D8F23C4258F, name="attrs=\x22RequiredPartition GUID:63", attrs="RequiredPartition GUID:63"
Salle-Technologie (rezizable image) d1.partition :
label: gpt label-id: 79FE4766-EDD2-4DD0-826C-6DD816A2E7C6 device: /dev/sda unit: sectors first-lba: 34 last-lba: 976773134 sector-size: 512 /dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5217DE87-4A45-4AC4-A4DD-0C8EB1C5CF5B, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=15C5E73F-7855-4DA4-A464-4694B0E56628, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 239616, size= 975486976, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=E130C384-3F46-4D8F-AD25-B85FDB0127CD, name="Basic data partition" /dev/sda4 : start= 975726592, size= 1046528, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D3FA37D6-10A7-4303-976C-6D8F23C4258F, name="attrs=\x22RequiredPartition GUID:63", attrs="RequiredPartition GUID:63"
Salle-Technologie (rezizable image) d1.minimum.partition :
label: gpt label-id: 79FE4766-EDD2-4DD0-826C-6DD816A2E7C6 device: /dev/sda unit: sectors first-lba: 34 last-lba: 976773134 sector-size: 512 /dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5217DE87-4A45-4AC4-A4DD-0C8EB1C5CF5B, name="EFI system partition", attrs="GUID:63" /dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=15C5E73F-7855-4DA4-A464-4694B0E56628, name="Microsoft reserved partition", attrs="GUID:63" /dev/sda3 : start= 239616, size= 72062114, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=E130C384-3F46-4D8F-AD25-B85FDB0127CD, name="Basic data partition" /dev/sda4 : start= 975726592, size= 1046528, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=D3FA37D6-10A7-4303-976C-6D8F23C4258F, name="attrs=\x22RequiredPartition GUID:63", attrs="RequiredPartition GUID:63"
-
@btoffolon The partition layout looks like it’s Win 10 2004 where Microsoft decided to change the layout and put a smaller partition (/dev/sda4) after the actual system drive (/dev/sda3 or C:\ in the Windows world) that you want to be resized.
For historical reasons (MBR layout and fixed boot sectors) FOG did not move partitions and so you see even when sda3 is being shrunk in size (72062114 sectors instead of 975486976) FOG does not move sda4 forward to make up for the gap.
We are working on this part of FOG currently and you are welcome to test a alpha version of this. Read through this topic and see if you want to give it a try: https://forums.fogproject.org/topic/15025/move-partition-in-gpt-layout-need-people-to-test
Be aware you should have a backup copy of your image and master machine as this is not officially part of FOG yet and not tested enough to be sure.
-
@sebastian-roth Thanks for your reply, we will try the alpha version.
My teammate ask me to say a big thank you because since 2008 we use fog and we see you’r answer are very quick and we are very happy to use fog.
did i need to do something to indicate the post as resolved ?