Error trying to restore GPT partition when deploying Image to smaller drive, Error Return Code: 4

[Sebastian Roth]

@drumnj I have to say sorry! Have been flat out jumping between jobs and not following this to the point.

Sure collecting the data could be helpful, if we know for sure this data (d1 files) is actually providing all we need to know. As well someone needs to sit down and sort through all the data and find a solution and I can’t see me doing this these days. While FOG Project is not just me, I have to say that the dev team is very small at the moment as very little people join in to work on this project. We can only do as much as time provides.

Be assured this topic is present and we are discussing things already. Though I can’t promise you a quick solution yet.

[drumnj]

@Sebastian-Roth Overall the current solution isn’t bad, so no real rush to figure out. I just think it isn’t the best solution. I suppose another option for people is to always make a golden image on a drive smaller than any other drive they plan to deploy to. Doing this I have found does allow the recovery partition to be used (did this with 2004 to make a clean OOBE Win10 image…with Chrome included).

[Quazz]

@drumnj said in Error trying to restore GPT partition when deploying Image to smaller drive, Error Return Code: 4:

@Sebastian-Roth Overall the current solution isn’t bad, so no real rush to figure out. I just think it isn’t the best solution. I suppose another option for people is to always make a golden image on a drive smaller than any other drive they plan to deploy to. Doing this I have found does allow the recovery partition to be used (did this with 2004 to make a clean OOBE Win10 image…with Chrome included).

That works, but I believe you run into the problem of being unable to expand the size of the Windows partition itself since the recovery partition is blocking it.

I’m not sure how to resolve this at the moment, personally I don’t use recovery partitions, they don’t really offer that much in my experience, though of course in some environments they may be desired or needed, so a solution would be ideal.

[Sebastian Roth]

@drumnj I know it’s been a long time but have not found enough time to work on this earlier. We now have a first version of init.xz capable of capturing and deploying a Windows 10 2004 UEFI/GPT install with recovery partition at the end. Would you give that a try.

Please be aware this is still in kind of a pre-release phase. Make sure you have a backup of your original image as well as the machine you pull the master from, just in case!!

[Brendan Clemente]

@sebastian-roth Sebastian, I’m having this same issue and would like to try with the init.xz. How would I go about doing so?

[Sebastian Roth]

@Brendan-Clemente Here are the steps I recommend when testing with this:

1. Make sure you have a working backup copy of your master (just in case something goes wrong when capturing) or deploy your current image to an identical machine and use that as a test capture machine for this.
2. Download the init file and put that in /var/www/html/fog/service/ipxe/ on your FOG server.
3. Create a new image definition for testing
4. Decide which hosts you use for testing capture and deploy with this new init, edit their hosts settings in the FOG web UI and set **Host Init" to init-201114.xz as well as the newly created image.
5. Schedule a capture task and pay attention to the boot process where it says bzImage..ok and init-201114.xz..ok to make sure it actually uses the new init file.
6. Schedule a deploy task for a machine with a smaller size disk and deploy to it. Again make sure it says init-201114.xz..ok when booting.

[Brendan Clemente]

@sebastian-roth Great, that seemed to have worked perfectly. I was able to capture and deploy my image now and confirmed that it used the new init-201114.xz. Thank you very much.

[Sebastian Roth]

@Brendan-Clemente So were you able to capture from a larger disk and deploy to a smaller size disk? Is it Windows 10 2004 you use?

[Brendan Clemente]

@sebastian-roth Yes, I was able to capture and deploy to a smaller disk but it was Windows 10 20H2, the newest version, that I used.

I am currently building a 2004 master machine though as we are having issues with our exchange server on the new 20H2 build. I will be capturing and deploying that image today. I’ll let you know the results.

[UWPVIOLATOR]

@drumnj said in Error trying to restore GPT partition when deploying Image to smaller drive, Error Return Code: 4:

Current disk size doesn’t match that of the backup!

Was this issue ever fixed? I am having the same issue with 20H2. I don’t want to have to delete the recovery partition.

[Sebastian Roth]

@UWPVIOLATOR Please open a new topic and post all your details there. FOG version currently used, contents of partition layout files as seen in the Initial post, installation of the client being UEFI or legacy BIOS?
I think we might have a solution for you but want to make sure it suites you.

[UWPVIOLATOR]

@sebastian-roth I missed the part where I had to reupload the image after updating the Init file. I am good now.

[lsdo]

Hello there, any news about this problem ?

[Sebastian Roth]

@lsdo I may also ask you to open a new topic and post your own details there!

You might also read this topic, possibly answers your question as well: https://forums.fogproject.org/topic/15025/move-partitions-on-gpt-layouts-need-people-to-test