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

    SSD fails at Restoring Partition Tables (GPT) with error code 4

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    19
    1.5k
    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.
    • R
      rwilsonadvantage @george1421
      last edited by george1421

      @george1421

      [root@serv-mitch-fog Win10HP]# ls -la
      total 44958000
      drwxrwxrwx. 2 fogproject root         238 Nov  8 08:52 .
      drwxrwxrwx. 5 fogproject root          76 Sep 19 16:11 ..
      -rwxrwxrwx. 1 fogproject root           9 Sep 19 15:54 d1.fixed_size_partitions
      -rwxrwxrwx. 1 fogproject root     1048576 Nov  8 08:51 d1.mbr
      -rwxrwxrwx. 1 fogproject root        1082 Sep 19 15:54 d1.minimum.partitions
      -rwxrwxrwx. 1 fogproject root          60 Sep 19 15:54 d1.original.fstypes
      -rwxrwxrwx. 1 fogproject root           0 Sep 19 15:54 d1.original.swapuuids
      -rwxrwxrwx. 1 fogproject root    31647083 Sep 19 15:54 d1p1.img
      -rwxrwxrwx. 1 fogproject root   113433917 Sep 19 15:54 d1p2.img
      -rwxrwxrwx. 1 fogproject root 28878471852 Sep 19 16:07 d1p3.img
      -rwxrwxrwx. 1 fogproject root   689768015 Sep 19 16:07 d1p4.img
      -rwxrwxrwx. 1 fogproject root 16322594957 Sep 19 16:11 d1p5.img
      -rwxrwxrwx. 1 fogproject root        1082 Sep 19 15:54 d1.partitions
      [root@serv-mitch-fog Win10HP]#
      
      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @rwilsonadvantage
        last edited by

        @rwilsonadvantage I think you missed a step in Sebastian’s’ instructions. At the FOS Linux command prompt you needed to key in fog and then single step through the deployment until you see the error then exit by hitting ctrl-C to exit the script before the system reboots.

        The file not found message was because the target computer hadn’t connected back to the fog server until the error is thrown. You can confirm that the target computer is connected back to the fog server by (on the fos linux target computer) keying in the same ls -la /images If the directory isn’t found or is blank then the fog server isn’t connected. If it returns values then you are at the point where you can run the sgdisk command. You will need to take a screen shot of that error.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        R 1 Reply Last reply Reply Quote 0
        • R
          rwilsonadvantage @george1421
          last edited by

          @george1421
          You are completely correct. I missed that completely. I am attaching both outputs here. I am also attaching the output for the image in fog itself, that way you can see it also.image1.png image3.PNG image2.png

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @rwilsonadvantage
            last edited by

            @rwilsonadvantage The second picture explains what is wrong. Basically the captured image is to big to fit onto the 250GB disk by 8,000,000 blocks.

            So what size was the disk on the source computer (i.e. where the image was captured from)? The thing you have to keep in mind is that a 250GB disk is not exactly 250GB in size.

            When Sebastian gets back on line he may ask you to cat the files d1.fixed_size_partitions, d1.partitions and d1.minimum.partitions from /images/Win10HP on the fog server. These files tell a bit more about the geometry of the source system.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            R 2 Replies Last reply Reply Quote 0
            • R
              rwilsonadvantage @george1421
              last edited by

              @george1421
              Ok, quick question, with it “resizable” shouldn’t that correct the issue? The image is only 60gb or so, and the ssd is 250. The source should have been a 256 ssd. but i am pulling to confirm.

              1 Reply Last reply Reply Quote 0
              • R
                rwilsonadvantage @george1421
                last edited by

                @george1421
                So i double checked the source, and it was pulled from a 256 sdd, but in looking at the dis structure, i found 2 “OEM” Partitions that were located at the end of the drive. I have deleted those, and am pulling an image now. I hope that solves the issue. I will keep everyone posted.

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

                  @rwilsonadvantage said in SSD fails at Restoring Partition Tables (GPT) with error code 4:

                  i found 2 “OEM” Partitions that were located at the end of the drive. I have deleted those, and am pulling an image now. I hope that solves the issue.

                  Right there! I am fairly sure that will help.

                  FOG doesn’t want to move those partitions because some of the OEM recovery partitions need to stay on the same sector or wouldn’t work.

                  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

                  R 2 Replies Last reply Reply Quote 0
                  • R
                    rwilsonadvantage @Sebastian Roth
                    last edited by

                    @Sebastian-Roth
                    Since we aren’t using them, we are “hoping” they aren’t needed. Fingers crossed, last set of updates before the new image pull.

                    george1421G 1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator @rwilsonadvantage
                      last edited by

                      @rwilsonadvantage In the FWIW bucket, when we build our golden image (using MDT), we configure MDT to not create the recover partition so we don’t have that non-movable partition a the end of the disk, leaving the 😄 drive the ability to expand or shrink to the size of the destination media as its the last partition on the disk.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      1 Reply Last reply Reply Quote 0
                      • R
                        rwilsonadvantage @Sebastian Roth
                        last edited by

                        @Sebastian-Roth
                        HUZZAH!!! A man of Quality!! the image was able to pull once i was able to remove the old partitions. You guys are awesome!!! How do i mark this as solved?

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

                          @rwilsonadvantage You are welcome! I just marked it as solved (Topic Tools -> Mark as solved, not sure if you have access to this).

                          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 / 1
                          • First post
                            Last post

                          199

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.3k

                          Posts
                          Copyright © 2012-2024 FOG Project