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

Error trying to restore GPT partition tables on multiple Dell machines

Scheduled Pinned Locked Moved Solved
FOG Problems
5
43
5.4k
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.
  • G
    george1421 Moderator @vanopy
    last edited by george1421 Mar 1, 2019, 6:32 AM Mar 1, 2019, 12:31 PM

    @vanopy Will you do this for us? On your golden (source system). Schedule a capture/deploy again, but before you schedule the task, check the debug checkbox. Then pxe boot the computer. After a few enter key presses you should be dropped to a linux (FOS) command prompt. At the FOS command prompt key in lsblk and post the results here. Do the same on this target computer that is giving this disk size issue. Post both results here so we can see the disk geometry.

    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!

    V 1 Reply Last reply Mar 1, 2019, 12:41 PM Reply Quote 1
    • V
      vanopy @george1421
      last edited by Mar 1, 2019, 12:41 PM

      @george1421 Of course

      This is from my captured machine:

      Fog Capture.jpg

      This is from my machine I’m trying to deploy:

      fog deploy.jpg

      G 1 Reply Last reply Mar 1, 2019, 12:52 PM Reply Quote 0
      • G
        george1421 Moderator @vanopy
        last edited by george1421 Mar 1, 2019, 6:56 AM Mar 1, 2019, 12:52 PM

        @vanopy Excellent there are two things that jump out at me.

        1. You are going from an nvme disk to a SATA attached disk.
        2. The target computer hard drive is slightly smaller than the source disk.

        Understand this is not an indication of error, only an observation.

        Ok now on your fog server. Login to the linux console then navigate to /images/winv10.3 directory. (Hint: if you use putty (free app) you can copy and paste without pictures if that is easier).

        Key in the following:

        1. cat d1.partitions
        2. cat d1.fixed_size_partitions
        3. cat d1.minimum.partitions
        4. ls -la

        These commands describe the image as it exists on the fog server.

        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!

        V 2 Replies Last reply Mar 1, 2019, 12:58 PM Reply Quote 0
        • V
          vanopy @george1421
          last edited by Mar 1, 2019, 12:58 PM

          @george1421 OK, done:

          Fog Server.jpg

          1 Reply Last reply Reply Quote 0
          • V
            vanopy @george1421
            last edited by Mar 1, 2019, 1:01 PM

            @george1421 Do you need screenshots from all the commands I’ve entered? Or is there anything you want me to show you specifically?

            G 1 Reply Last reply Mar 1, 2019, 1:04 PM Reply Quote 0
            • G
              george1421 Moderator @vanopy
              last edited by Mar 1, 2019, 1:04 PM

              @vanopy We will need a screen shot of the first two commands since they scrolled off the screen in the picture.

              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!

              V 1 Reply Last reply Mar 1, 2019, 1:07 PM Reply Quote 0
              • V
                vanopy @george1421
                last edited by Tom Elliott Mar 1, 2019, 8:40 AM Mar 1, 2019, 1:07 PM

                @george1421 Copied all the commands via Putty as you first recommended:

                [root@BGImage ~]# cd /images/winv10.3
                [root@BGImage winv10.3]# cat d1.partitions

                label: gpt
                label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
                device: /dev/nvme0n1
                unit: sectors
                first-lba: 34
                last-lba: 1000215182
                
                /dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name="EFI system partition", attrs="GUID:63"
                /dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name="Microsoft reserved partition", attrs="GUID:63"
                /dev/nvme0n1p3 : start=      239616, size=   996288512, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name="Basic data partition"
                /dev/nvme0n1p4 : start=   996528128, size=     3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name="Basic data partition", attrs="RequiredPartition GUID:63"
                

                [root@BGImage winv10.3]# cat d1.fixed_size_partitions

                :1:2:4
                

                [root@BGImage winv10.3]# cat d1.minimum.partitions

                label: gpt
                label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
                device: /dev/nvme0n1
                unit: sectors
                first-lba: 34
                last-lba: 1000215182
                
                /dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name="EFI system partition", attrs="GUID:63"
                /dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name="Microsoft reserved partition", attrs="GUID:63"
                /dev/nvme0n1p3 : start=      239616, size=    59116948, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name="Basic data partition"
                /dev/nvme0n1p4 : start=   996528128, size=     3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name="Basic data partition", attrs="RequiredPartition GUID:63"
                

                [root@BGImage winv10.3]# ls -la

                total 13025224
                drwxrwxrwx  2 root root         247 Feb 28 15:13 .
                drwxrwxrwx. 5 fog  root          77 Feb 28 16:53 ..
                -rwxrwxrwx  1 root root           7 Feb 28 15:04 d1.fixed_size_partitions
                -rwxrwxrwx  1 root root     1048576 Feb 28 15:04 d1.mbr
                -rwxrwxrwx  1 root root         886 Feb 28 15:04 d1.minimum.partitions
                -rwxrwxrwx  1 root root          20 Feb 28 15:04 d1.original.fstypes
                -rwxrwxrwx  1 root root           0 Feb 28 15:04 d1.original.swapuuids
                -rwxrwxrwx  1 root root         302 Feb 28 15:04 d1.original.uuids
                -rwxrwxrwx  1 root root    13051888 Feb 28 15:05 d1p1.img
                -rwxrwxrwx  1 root root    16912752 Feb 28 15:05 d1p2.img
                -rwxrwxrwx  1 root root 12698745465 Feb 28 15:13 d1p3.img
                -rwxrwxrwx  1 root root   608040382 Feb 28 15:13 d1p4.img
                -rwxrwxrwx  1 root root         886 Feb 28 15:04 d1.partitions
                

                MOD Edited to put into code blocks for easier visibility.

                G 1 Reply Last reply Mar 1, 2019, 1:18 PM Reply Quote 0
                • G
                  george1421 Moderator @vanopy
                  last edited by george1421 Mar 1, 2019, 7:24 AM Mar 1, 2019, 1:18 PM

                  @vanopy I think we are at a point where we need an @Developers to look at what we’ve collected so far. I suspect I know what the problem is, but I’m wondering if you can test the idea out. I need you to try to find a computer that you can deploy this image to, but the target hard drive needs to be bigger than 477GB (your source disk). Since this is just a disposable test, if you have a spare 800GB or 1TiB hard drive handy, see if you can deploy to it.

                  I want to test 2 things:

                  1. Does size matter?
                  2. Is the disk architecture change impacting imaging?

                  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
                  • T
                    Tom Elliott
                    last edited by Tom Elliott Mar 1, 2019, 7:25 AM Mar 1, 2019, 1:23 PM

                    I know I seem distant and all these days, but this really sounds like a 4K advanced disk problem.

                    What makes me say this?

                    The nvme was a 512gb disk, I assume and it’s just a guesstimate. The sata disk is also a 512gb disk, guesstimate.

                    But look at the layout variances in reported disk size. One shows as about 465GB (sda) while the nvme shows at 477GB (nvme).

                    The oversized for each partition would seem, too me, to come from calculating disk sectors at a larger size than the actual disk can use.

                    I very well could be wrong of course and welcome any suggestions.

                    @sebastian-Roth I think we need to try figuring out a suitable mechanism to upscale to 4K only (less needed as most advanced disks will allow reappropiation of the sectors into 512B) as well as downscale 4K back to 512B. I don’t know of a good approach to do such a thing yet but it seems more and more people are looking to image cross spectrum.

                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    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

                    V 2 Replies Last reply Mar 1, 2019, 1:29 PM Reply Quote 1
                    • V
                      vanopy @Tom Elliott
                      last edited by Mar 1, 2019, 1:29 PM

                      @Tom-Elliott Some more info, just opened the laptop I wanted to deploy to see exactly which disk is inside, it’s a 500 GB SATA Disk. I don’t think I have any larger disks laying around to test with.

                      I’ve also tried to deploy the image on a newer model, which also has an nvme disk, but this was giving the same outcome and error message, like in my original post.

                      1 Reply Last reply Reply Quote 0
                      • V
                        vanopy @Tom Elliott
                        last edited by vanopy Mar 1, 2019, 7:37 AM Mar 1, 2019, 1:36 PM

                        @Tom-Elliott Could it be an idea, that I create a completely new golden image, but this time on the Sata disk? And try to get those deployed to my Sata and nvme disks? Just thinking out loud, will take me some time though.

                        T 1 Reply Last reply Mar 1, 2019, 2:03 PM Reply Quote 0
                        • T
                          Tom Elliott @vanopy
                          last edited by Mar 1, 2019, 2:03 PM

                          @vanopy That could work, yes.

                          Though looking over the files you provided the information appears to be saying the SSD (nvme) is using 512B sectors, so my 4k idea is out the window then. (I wasn’t at a computer when I wrote what I did so didn’t have simple access to view the information and test my thoughts.)

                          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                          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

                          V 1 Reply Last reply Mar 1, 2019, 2:07 PM Reply Quote 0
                          • V
                            vanopy @Tom Elliott
                            last edited by Mar 1, 2019, 2:07 PM

                            @Tom-Elliott Ok, I’ll start making my master image on the Sata disk and will let you know the outcome, will probably be on Monday since I’ll be leaving work in 1 hour. Thanks already.

                            T 1 Reply Last reply Mar 1, 2019, 2:20 PM Reply Quote 0
                            • T
                              Tom Elliott @vanopy
                              last edited by Mar 1, 2019, 2:20 PM

                              @vanopy I think there’s a potential for us to be able to fix this even as is, but it would take a bit of thought first.

                              I wonder if it’s reverse of what I’m thinking?

                              Here’s why:

                              partition 1 = 204800 x 512 = 104,857,600 (100M)
                              partition 2 = 32768 x 512 = 16,777,216 (16M)
                              partition 3 = 996288412 x 512 = 510,099,718,144 (475.1G)
                              partition 4 = 3665920 x 512 = 1,510,359,040 (1.4G) (approximately obviously your screen shows slightly different.)

                              Now put to to a 4k only drive:

                              partition 1 = 204800 x 4096 = 838,860,800 (800M)
                              partition 2 = 32768 x 4096 = 134,217,728 (128M)
                              partition 3 = 996288412 x 4096 = 4,080,797,335,552 (3.7T) (Yes Terabytes)
                              partition 4 = 3665920 x 4096 = 15,015,608,320 (14G)

                              Hopefully this makes sense, and I’m only guessing based on the information.

                              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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                              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
                              • S
                                Sebastian Roth Moderator
                                last edited by Sebastian Roth Mar 1, 2019, 8:24 AM Mar 1, 2019, 2:23 PM

                                @vanopy said in Error trying to restore GPT partition tables on multiple Dell machines:

                                root@BGImage winv10.3]# cat d1.fixed_size_partitions
                                :1:2:4

                                While it could be a 512/4k block size issue as @Tom-Elliott mentioned I see another problem here, a very obvious one. See above, partitions 1, 2 and 4 are marked as fixed (for whatever reason). This prevents from deploying to a disk being just a little smaller…

                                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

                                V T 2 Replies Last reply Mar 1, 2019, 2:27 PM Reply Quote 0
                                • V
                                  vanopy @Sebastian Roth
                                  last edited by Mar 1, 2019, 2:27 PM

                                  @Sebastian-Roth Ok, thanks for having a look. I don’t really have an idea why these partitions are fixed.
                                  Is there an easy way for me to undo this, so I could try to capture/deploy this image again?

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    Tom Elliott @Sebastian Roth
                                    last edited by Tom Elliott Mar 1, 2019, 8:35 AM Mar 1, 2019, 2:30 PM

                                    @Sebastian-Roth I would agree here too. Maybe we can modify part 4 to become part 3?

                                    Changing the file names so d1p4 = d1p3, and d1p3 = d1p4.

                                    mv /images/winv10.3/d1p{4,tmp}.img
                                    mv /images/winv10.3/d1p{3,4}.img
                                    mv /images/winv10.3/d1p{tmp,3}.img
                                    

                                    Then Adjusting the partitions files:

                                    d1.partitions:

                                    label: gpt
                                    label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
                                    device: /dev/nvme0n1
                                    unit: sectors
                                    first-lba: 34
                                    last-lba: 1000215182
                                    
                                    /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name=“EFI system partition”, attrs=“GUID:63”
                                    /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name=“Microsoft reserved partition”, attrs=“GUID:63”
                                    /dev/nvme0n1p3 : start= 239616, size= 3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
                                    /dev/nvme0n1p4 : start= 3905536, size= 996288512, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name=“Basic data partition”
                                    

                                    d1.minimum.partitions to:

                                    label: gpt
                                    label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
                                    device: /dev/nvme0n1
                                    unit: sectors
                                    first-lba: 34
                                    last-lba: 1000215182
                                    
                                    /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name=“EFI system partition”, attrs=“GUID:63”
                                    /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name=“Microsoft reserved partition”, attrs=“GUID:63”
                                    /dev/nvme0n1p3 : start= 239616, size= 3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
                                    /dev/nvme0n1p4 : start= 3905536, size= 59116948, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name=“Basic data partition”
                                    
                                    

                                    And finally d1.fixed_size_partitions to:

                                    :1:2:3
                                    

                                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                    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

                                    V 1 Reply Last reply Mar 1, 2019, 2:33 PM Reply Quote 0
                                    • V
                                      vanopy @Tom Elliott
                                      last edited by Mar 1, 2019, 2:33 PM

                                      @Tom-Elliott @Sebastian-Roth Really appreciate the help. Just let me know if you want me to make any change or if you want to test anything.

                                      T 1 Reply Last reply Mar 1, 2019, 2:38 PM Reply Quote 0
                                      • T
                                        Tom Elliott @vanopy
                                        last edited by Mar 1, 2019, 2:38 PM

                                        @vanopy Would you be willing to try the things I suggested? I might suggest creating a backup of the current image just so you have the original ready to go.

                                        If you need help just let us know and I’m sure we can help.

                                        I’m not sure if this would work, but theoretically it would as it would place your data partition at the end of the disk and in line based on the sizes used.

                                        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                        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

                                        V 1 Reply Last reply Mar 1, 2019, 3:09 PM Reply Quote 0
                                        • V
                                          vanopy @Tom Elliott
                                          last edited by Mar 1, 2019, 3:09 PM

                                          @Tom-Elliott Just made the changes as requested, but I’m still getting the same GPT error when trying to deploy unfortunately. Any other ideas/suggestions?

                                          T 1 Reply Last reply Mar 1, 2019, 3:15 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 3 / 3
                                          3 / 3
                                          • First post
                                            17/43
                                            Last post

                                          253

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project