Partition Resizing (expanding) not working. Windows Server 2019 Single Disk (Resizable)


  • Using FOG 1.5.9 on CentOS 7

    I’m deploying my Image to a machine (UEFI) and the image has these values:

    [root@FOG Win2019_conPlesk_GPT]# cat d1.fixed_size_partitions
    :1:2:3
    [root@FOG Win2019_conPlesk_GPT]# 
    [root@FOG Win2019_conPlesk_GPT]# cat d1.partitions
    label: gpt
    label-id: 9031635A-A599-4883-8E82-3E44BBC3A246
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 3749445598
    sector-size: 512
    
    /dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0D6025D8-9A8B-40A8-B21A-38499EBD6B4F, name="EFI system partition", attrs="GUID:63"
    /dev/sda2 : start=      206848, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=72F3757F-2953-4DCA-98F0-58C5C4853FAD, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda3 : start=     1126400, size=   209715200, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=4ECAB7CD-2962-4E15-9720-C5CF9AC47BCD
    /dev/sda4 : start=   210841600, size=  3538601984, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=48DFEE94-AF28-4F5D-84F8-85B96AFD5888
    [root@FOG Win2019_conPlesk_GPT]# 
    [root@FOG Win2019_conPlesk_GPT]# 
    [root@FOG Win2019_conPlesk_GPT]# 
    [root@FOG Win2019_conPlesk_GPT]# cat d1.minimum.partitions
    label: gpt
    label-id: 9031635A-A599-4883-8E82-3E44BBC3A246
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 3749445598
    sector-size: 512
    
    /dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0D6025D8-9A8B-40A8-B21A-38499EBD6B4F, name="EFI system partition", attrs="GUID:63"
    /dev/sda2 : start=      206848, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=72F3757F-2953-4DCA-98F0-58C5C4853FAD, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda3 : start=     1126400, size=   209715200, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=4ECAB7CD-2962-4E15-9720-C5CF9AC47BCD
    /dev/sda4 : start=   210841600, size=    10240000, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=48DFEE94-AF28-4F5D-84F8-85B96AFD5888
    [root@FOG Win2019_conPlesk_GPT]# 
    

    When the server restarts and I have the following problem

    7a975780-7f87-4276-b742-8dc2c67ad550-image.png

    aeba76c2-0b87-4a98-821f-95c0f3bc35c0-image.png

    e95406ce-d173-4db6-aefa-ddef8deb6489-image.png

    On disk management the partitioning is correct but it is not

    Any advice on how to solve this problem?

  • Senior Developer

    @gfrancesco84 Any news on this?

  • Moderator

    @gfrancesco84 What is the output of list vol in diskpart?


  • @sebastian-roth

    if you need my image this is not a problem for me.
    tell me where can I upload it

    thank you very much for your availability

  • Senior Developer

    @gfrancesco84 The output of ntfsresize on the host before capturing looks ok. Does it show the full size of 100 GB for partition #3 in Windows as well??

    I am not sure this is something we can figure out by trying to replicate the issue. The partitioning looks all good and it seems like this is something partclone is doing wrong when writing the data to disk. As this is not a general issue I would need to get your image data to be able to find out why this is happening. Probably not possible.

    Will do some research to see if we find other users reporting this kind of thing. I don’t remember having see this before. @george1421 @Wayne-Workman @Tom-Elliott ?


  • it would seem that there are no problems before capturing the image with fog

    0057aff4-72d8-4182-897b-991d6b2644fd-image.png


  • @sebastian-roth thanks in advance for your advice

    This problem occurs on first boot.

    a4b27e72-e111-4d9f-a505-b4dd538dacd0-image.png

    with the command you gave me I solved the problem

    ntfsresize -b /dev/sda3
    

    9263bef5-ce8a-4aea-b342-81d755177028-image.png

    What could be the best solution to solve the problem at source?

  • Senior Developer

    @gfrancesco84 There might be an “ugly” quick fix by running ntfsresize manually (or via post deploy scripts) until we figure out what’s wrong.

    So while you are in debug mode anyway you might try this command:

    ntfsresize -b /dev/sda3
    

    Now that I think of it again I can see it being an issue on the source machine already. Please boot up the host you capture the image from and check if that has sda3 resized to 30 GB already?!

  • Senior Developer

    @gfrancesco84 Pretty strange that sda3/Partition 3 is shown as 100 GB in diskpart and diskmgmt matching the values we see in the partition table lists as well but Windows Explorer thinks it’s just 30 GB in size. I have never seen this before. It seems like the partition itself is 100 GB but the filesystem within the partition is 30 GB. I could see this happen if sda3 was being resized and something went wrong. But partclone should just deploy that sda3 image to the partition and not do any resize operations on it.

    Please do me a favor: Schedule another deploy task for this host but make sure you enable the checkbox for debug before you create the task in the web UI. Start it up as usual and hit ENTER twice to get to a shell. Now run sfdisk -d /dev/sda, take a picture of the output and post that here.

    When the server restarts and I have the following problem

    Just so we get the full picture here, does this mean you see the smaller C: drive on the first startup of your server already or only after it was restarted/rebooted the first time?

346
Online

8.8k
Users

15.5k
Topics

144.5k
Posts