• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Error trying to restore GPT partition tables

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    gpt error restore
    5
    21
    8.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aephk @Quazz
      last edited by

      @Quazz Will attempt recapture now.

      Checking in Windows on the source drive it only shows 3 partitions, however, FOG seems to be picking it up as having 4 which is odd…

      @Sebastian-Roth I have the client in question using the 4.19.64 kernel, and had changed the ramdisk size when troubleshooting the issue initially.

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @aephk said in Error trying to restore GPT partition tables:

        Having a look at the image’s files on the server, all partitions are marked as fixed in d1.fixed_size_partitions,

        Re-reading the post I just saw this. So this seems to be a different issue to what we have fixed in the latest inits. No wonder updating those doesn’t help.

        Please schedule a debug capture task on the source machine, boot it up to the shell and run parted -l (l as in lion!) Post a picture of the output here.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        A 1 Reply Last reply Reply Quote 0
        • A
          aephk @Sebastian Roth
          last edited by

          @Sebastian-Roth I’m just re-running a capture with the new inits. It will take quite a bit as it’s around 170GB in size. I’ll give this a go as soon as I can.

          1 Reply Last reply Reply Quote 0
          • A
            aephk
            last edited by

            @Quazz I’ve rerun the capture with the new inits but the same issue is present.

            @Sebastian-Roth Here is the output of parted -l from a debug capture of the image:
            alt text

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @aephk From the picture you posted the partition layout looks fine. Not saying that there can’t be another issue but it’s good to know this part seems ok as a start.

              Having a look at the image’s files on the server, all partitions are marked as fixed in d1.fixed_size_partitions

              I guess we need the details to be able to help. Please post the full contents of the file d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions here.

              Checking in Windows on the source drive it only shows 3 partitions, however, FOG seems to be picking it up as having 4 which is odd…

              This is ok because Windows disk management doesn’t show partitions marked as hidden.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              A 1 Reply Last reply Reply Quote 0
              • A
                aephk @Sebastian Roth
                last edited by

                @Sebastian-Roth Here is the contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions:

                d1.partitions:
                label: gpt
                label-id: 02B6114B-E445-46A0-B7A7-8C38BA5BB203
                device: /dev/sda
                unit: sectors
                first-lba: 34
                last-lba: 468877278

                /dev/sda1 : start= 2048, size= 1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=C744BEC7-CF95-4626-A819-48285257F9A9, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
                /dev/sda2 : start= 1024000, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=8546EE7F-82E0-447F-913A-C13E109A61FF, name=“EFI system partition”, attrs=“GUID:63”
                /dev/sda3 : start= 1228800, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=C2B8A2B0-B751-402C-BCA3-D19E134D3CD1, name=“Microsoft reserved partition”, attrs=“GUID:63”
                /dev/sda4 : start= 1261568, size= 467615232, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=285E434A-1556-455C-B60A-E65C92C9DDAC, name=“Basic data partition”

                d1.minimum.partitions:
                label: gpt
                label-id: 02B6114B-E445-46A0-B7A7-8C38BA5BB203
                device: /dev/sda
                unit: sectors
                first-lba: 34
                last-lba: 468877278

                /dev/sda1 : start= 2048, size= 1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=C744BEC7-CF95-4626-A819-48285257F9A9, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
                /dev/sda2 : start= 1024000, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=8546EE7F-82E0-447F-913A-C13E109A61FF, name=“EFI system partition”, attrs=“GUID:63”
                /dev/sda3 : start= 1228800, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=C2B8A2B0-B751-402C-BCA3-D19E134D3CD1, name=“Microsoft reserved partition”, attrs=“GUID:63”
                /dev/sda4 : start= 1261568, size= 467615232, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=285E434A-1556-455C-B60A-E65C92C9DDAC, name=“Basic data partition”

                d1.fixed_size_partitions:
                1:2:3:4

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by

                  @aephk Ok, the files show that FOS (FOG OS) does not seem to shrink the fourth partition before capturing. Both, d1.partitions and d1.minimum.partitions are identical which should not be the case.

                  image “On client” size is showing at around 223GB

                  How much space is actually used on the disk when you boot up Windows and have a look? Possibly bitlocker is somehow enabled here? Open a cmd shell as administrator and run

                  manage-bde -status C:
manage-bde -off C:
manage-bde -status C:

                  Other than that there is no other way than you scheduling a debug capture task for this machine. Boot it up, hit ENTER till you get to the shell and run fog command to start the process. Now step through it and take pictures of it all. Post the pictures here.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    aephk @Sebastian Roth
                    last edited by aephk

                    @Sebastian-Roth Hi, here are the photos of the debug capture. After this it just goes on to capture as normal.

                    alt text
                    alt text
                    alt text
                    alt text
                    alt text
                    alt text

                    EDIT: If I manually shrink the 4th partition in Windows, run a capture then try to deploy to one of the drives that fails it works fine.

                    EduardoTSeoaneE 1 Reply Last reply Reply Quote 0
                    • EduardoTSeoaneE
                      EduardoTSeoane @aephk
                      last edited by

                      @aephk
                      This is not a solution, but maybe can help you.

                      All our images on the Images store are manually shrinked, we adjust the final size of the partitions from the postdownload script with our own criteria.

                      We are doing this from fog1.3.2, we are currently on FOG1.5.6.

                      1 Reply Last reply Reply Quote 0
                      • A
                        aephk
                        last edited by

                        I may have found the issue here.

                        I was curious as to why FOG was refusing to resize the disk, so I thought I’d try a manual resize in linux/gparted. Booting in to the gparted live cd, gparted could see the drive and all of the partitions but it was failing to read the contents of partition 4.

                        I Googled this and it looks like it may have been caused by bad sectors and running chkdsk /f had fixed it for others so I tried that, went back in to gparted and now everything looked fine. So I’ve run a new capture and it appears to have shrunk the 4th partition as expected. I’m currently deploying it to one of the drives that was failing and all is looking good so far.

                        I’m not sure what caused the issue in the first place, I hadn’t modified the partition table at all, I had just installed an admittedly fairly large number of programs to an existing image and tried to recapture it.

                        @Quazz @Sebastian-Roth @EduardoTSeoane Thanks for your help on this folks!

                        1 Reply Last reply Reply Quote 3
                        • P
                          phm2000
                          last edited by

                          hi

                          I have same problem with fog 1.5.7, is there a solution ?

                          Thanks

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by

                            @phm2000 said in Error trying to restore GPT partition tables:

                            I have same problem with fog 1.5.7, is there a solution ?

                            Sorry but with this kind of problem there is no general solution that works for everyone. Please open your own topic in the forums and post all your own details: full contents of the file d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions.

                            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                            1 Reply Last reply Reply Quote 0
                            • 1
                            • 2
                            • 1 / 2
                            • First post
                              Last post

                            191

                            Online

                            11.6k

                            Users

                            17.1k

                            Topics

                            154.6k

                            Posts
                            Copyright © 2012-2024 FOG Project