Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders) on different sized drives

[Yeet]

I built a Win10 Image on a 256 GB NVMe drive. Didn’t have any issues deploying images until recently. We had a mixup when ordering drives, and we ordered 250 GB drives instead. When I try pulling it down to one of our machines of the same model with a 250 GB NVMe drive, it gives me the following error:

Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders)

Is this due to the drive being 6gb smaller than the one the image was built on? Is there a setting I’m missing? I have the image set to single disk, resizable.

[Sebastian Roth]

@yeet said in Error trying to restore GPT Partition tables (restorepartitionTablesAndBootLoaders) on different sized drives:

Is this due to the drive being 6gb smaller than the one the image was built on?

Yes, if your Windows 10 is 2004 or a newer build and your are using FOG 1.5.9 or older. That’s because with those versions of Win 10 they put a new recovery partition at the end of the disk and we have updated inits that can handle this in the latest dev-branch version.

Is there a setting I’m missing? I have the image set to single disk, resizable.

That setting is correct but as mentioned above you need the latest inits. Manually download inits (64 bit and 32 bit) and put into /var/www/html/fog/service/ipxe/ on your FOG server. Rename the existing files as backup instead of overwriting!

Now you need to re-capture the image. Maybe even create a new image definition for this to not overwrite your existing image files as a backup. Assign the new image to the host you capture from and schedule the task.

This image captured with the new inits should deploy to devices with smaller disk fine. If not, let us know here.