Error trying to restore GPT partition tables. Exit returned code 4



  • CentOS Linux 7.7.1908
    FOG 1.5.6

    20200508_134622.jpg

    Sorry to make another post about this but I did not see resolutions from the other ones. We just got new devices in Optiplex 3070 that cant legacy boot Windows anymore so we have to create a UEFI image. While trying to do this I am getting Error trying to restore GPT partition tables. Exit returned code 4.

    How do I fix this issue or what am I doing wrong? Note, my virtual machine HD is 250GB but the image is only 23GBish. (I have the larger HD as I use this base image to create other images that are much larger) I did this for my MBR image and that was just fine only the GPT UEFI image is giving me grief.

    Also I cant get VMware Workstation to upload via UEFI so I have to change it to BIOS and PXE boot it in legacy mode to capture image.

    I am going to assume I have to upgrade FOG?


  • Developer

    @UWPVIOLATOR said in Error trying to restore GPT partition tables. Exit returned code 4:

    I uploaded it again and I didn’t do anything different and it worked.

    It’s very strange you don’t seem to get consistent results with this. I have seen converted MBR/GPT partition layouts that caused such an issue but those didn’t fix themselves!

    Could it be something with FOG running into issues capturing?

    Do you see any errors when capturing? May I ask you to rename the /images/000-1909UEFI/ folder to /images/000-1909UEFI_bak1/ and re-capture again. See if it deploys properly or fails. Try go get two image directories, one that is causing the deploy error and one that doesn’t. Then grab all the files from both image directories except the large d1pX.img files, ZIP them up, upload to a fileshare and post a link here! I will take a look.

    I saw in update notes that there has been some error checking added. Is that possibly the issue?

    Can you be more precise on what you saw and where? There have been hundreds of changes since FOG 1.5.6 and I am not sure what you mean.



  • @Sebastian-Roth

    I uploaded it again and I didn’t do anything different and it worked. Could it be something with FOG running into issues capturing? I saw in update notes that there has been some error checking added. Is that possibly the issue?



  • @Sebastian-Roth

    Destination Disk is 128GB SSD capture VM is 250GB.

    Image is Single Disk - Resizable

    I did test a MS Tools convert as I tried to convert my current image to UEFI to save time but got the same error. Then I made a brand new image UEFI image and captured it and got the error above. Then captured ita again and it worked. Then captured again and got the error. Its just not consistent.

    chrome_gxGMpjbkrx.jpg


  • Developer

    @UWPVIOLATOR What size is the destination disk? Would you be able to capture the image as non-resizable? Just as a quick test. For this I’d suggest you just create a new image definition in the web UI, set it to non-resizable, capture from the VM and try to deploy to the PC.

    To dig into this issue further I would ask you to create a debug deploy task using the resizeable image. Schedule a deploy task as normal but just before you hit the button to create the task there is a checkbox for debug mode. Boot the PC and hit ENTER twice to get to a shell. Run the command fog to start the deploy and step through it (ENTER, ENTER, …) till you hit the error. Then you get back to the shell and run that last command manually:

    sgdisk -gl /images/000-1909UEFI/d1.mbr /dev/sda
    

    Take a picture of the error screen and post here.

    By the way, did you use the MS tools to convert the MBR disk layout to GPT??


Log in to reply
 

275
Online

7.0k
Users

14.2k
Topics

134.4k
Posts