Move partitions on GPT layouts - need people to test

  • Testers

    @sebastian-roth I’m doing tests using just vms, so it’s possible that physical hardware could respond differently.
    Here are my results.

    I created an image successfully from a 128 GB VM, it was 10 GB in size after being resized (all I did was enter audit mode after installing windows and then captured)

    I deployed it to a VM with a 60GB drive and had no issues.

    I did confirm that the new init was used at boot for both. There was a bunch of extra output that happened to fast to catch on the capture before the gparted screens showed up, but everything worked fine.

    Here is my d1.partitions

    label: gpt
    label-id: 68156B04-B4FE-40EF-96CC-747C33F75E54
    device: /dev/nvme0n1
    unit: sectors
    first-lba: 34
    last-lba: 268435422
    sector-size: 512
    
    /dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=2C465DF5-10FD-4883-B323-423E3D10FB2E, name="EFI system partition", attrs="GUID:63"
    /dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=7AFE394E-47A0-43FE-A06E-7AFD7286E200, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/nvme0n1p3 : start=      239616, size=   267168294, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=4A0FF43A-6E31-4AC9-8446-073E07C63AA8, name="Basic data partition"
    /dev/nvme0n1p4 : start=   267409408, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=AEF97419-7B7D-4EC5-8C19-FF8C0217A965, attrs="RequiredPartition GUID:63"
    

    Just to be safe, I will also test this in reverse with the init, Going to capture the 60 GB image and deploy it to the 128 GB VM, especially since that’s what I usually do.

    Also, just for reference, here is the d1.partitions from our 1909 image. It looks like windows started putting the data partition at partition 3 instead of 4, kinda weird, that would make expanding disks for the main data drive more difficult, I wonder what the reasoning for that is.

    [root@arrowfog Base-Stable]# cat d1.partitions
    label: gpt
    label-id: 68156B04-B4FE-40EF-96CC-747C33F75E54
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 134217694
    sector-size: 512
    
    /dev/sda1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=75A55945-9352-4F30-A330-67878EC28FA1, name="Basic data partition", attrs="RequiredPartition GUID:63"
    /dev/sda2 : start=     1085440, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=D1336408-C5B3-446F-BE78-725587F7224D, name="EFI system partition", attrs="GUID:63"
    /dev/sda3 : start=     1288192, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=C9F8E03C-928A-4233-9837-49CE510E39B0, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda4 : start=     1320960, size=   132894720, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=D7729B0D-A7B4-4E1F-A9F5-F06FAAAE6141, name="Basic data partition"
    
  • Senior Developer

    @jj-fullmer said in Move partition in GPT layout - need people to test:

    So just to be clear, I need to create the image from a new VM or physical machine that has a larger drive? i.e. expand the drive to something like 256 or 512 and then capture (where it will resize down to the usual 20ish GB or probably less for this test cause I’ll just install windows and that’s it) and then deploy to something with a 64 or 128 sized drive where it will resize.

    That sounds like a reasonable test to me!

    Why are people creating images from things with drives larger than what they are deploying to?

    Probably because they use some hardware machine they have as master but don’t think about the disk size making a difference.

  • Testers

    @Sebastian-Roth I just re-read through this as I’m starting work on our 20H2 image.
    We actually purposely make our base image from a smaller disk already of around 64 GB and it usually shrinks down to around 20 GB when captured. Then we deploy to things with larger drives.

    So just to be clear, I need to create the image from a new VM or physical machine that has a larger drive? i.e. expand the drive to something like 256 or 512 and then capture (where it will resize down to the usual 20ish GB or probably less for this test cause I’ll just install windows and that’s it) and then deploy to something with a 64 or 128 sized drive where it will resize.

    Why are people creating images from things with drives larger than what they are deploying to?

    Or is this testing a different type of image?

  • Testers

    @sebastian-roth I hope to be building our 20H2 image the start of next year. So I can do some testing along with that for sure on this then.

  • Senior Developer

    @testers Anyone of you still active in the forums?

334
Online

8.0k
Users

14.9k
Topics

140.7k
Posts