1.5.6 : Small local disk and the rest unallocated



  • Hi

    Following this post : https://forums.fogproject.org/topic/13260/small-local-disk-and-the-rest-unallocated/6

    Since FOG upgrade 1.5.4 to 1.5.6 the partitions are randomly often badly resized.
    Gparted.jpg

    We have test with the new init.xz and init_32.xz and the FOG settings (FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000) with no change.

    We have rollback to 1.5.4, it’s working.

    d1.partitions

    label: gpt
    label-id: 342E0E46-FCE0-493B-B86B-CCD863B21A14
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 134217694
    
    /dev/sda1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=5219620A-6815-455F-B2AC-90053839B61B, name="Basic data partition", attrs="RequiredPartition GUID:63"
    /dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CCB33AC5-D395-4B86-9429-FC1DF03DA6DF, name="EFI system partition", attrs="GUID:63"
    /dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E12B2745-C17B-4AFD-AF85-EC7B8024826E, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda4 : start=     1261568, size=   132954112, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=51D443EE-8D96-4A4C-99A1-36F5B34FD10E, name="Basic data partition"
    

    d1.minimum.partitions

    label: gpt
    label-id: 342E0E46-FCE0-493B-B86B-CCD863B21A14
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 134217694
    
    /dev/sda1 : start=        2048, size=       26234, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=5219620A-6815-455F-B2AC-90053839B61B, name="Basic data partition", attrs="RequiredPartition GUID:63"
    /dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CCB33AC5-D395-4B86-9429-FC1DF03DA6DF, name="EFI system partition", attrs="GUID:63"
    /dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E12B2745-C17B-4AFD-AF85-EC7B8024826E, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda4 : start=     1261568, size=    50129436, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=51D443EE-8D96-4A4C-99A1-36F5B34FD10E, name="Basic data partition"
    

    d1.fixed_size_partitions

    :2:3
    

  • Developer

    @marcolefo New inits are ready for testing. Download 64 Bit and 32 Bit and put those in /var/www/html/fog/service/ipxe/ dir on your FOG server. Probably good to rename the original ones instead of overwriting.

    As well you need to check the RAM SIZE option in FOG configuration, FOG settings. Need to be 275000 with the newer inits.


  • Developer

    @marcolefo Probably caused by the same issue we are tracking down here: https://forums.fogproject.org/topic/13440/fog-1-5-6-auto-resize-is-unpredictable

    I will port here as soon as we have fixed this.


  • Developer

    @marcolefo Can you give us more information on this?


  • Developer

    @marcolefo said in 1.5.6 : Small local disk and the rest unallocated:

    Since FOG upgrade 1.5.4 to 1.5.6 the partitions are randomly often badly resized.

    Ok, back from a holiday. Let’s see if we can address this one. So what I am wondering about is that you say “randomly”. Does the same image resize properly on one deploy but not if you deploy it a second time?? Or is it more like it resizes properly when deployed to some hosts (e.g. models with a particular disk size) but not on others?


  • Moderator

    @Sebastian-Roth Don’t really know about why it wouldn’t expand. Altough, might be interesting to see if this problem occurs on GPT installations only or also on MBR installations.

    Recapturing the original image should fix the fixed partition thing at least so partition 1 is also included in it.


  • Developer

    @marcolefo It’s very strange it does not expand. The latest issue we had (and fixed in the inits) did only occour when the images was captured from NVMe drives. So shouldn’t be an issue in your case anyway.

    Between 1.5.4 and 1.5.6 we changes the way FOG discovers fixed size partitions. So it’s probably an issue with that in your particular case.

    Looking at the partition layout information you posted I don’t see anything that could go wrong with that. So I am wondering if those came from when you captured the image with 1.5.4 or 1.5.6??

    @Quazz Would you find the time to have a look at this as well?


Log in to reply
 

453
Online

5.9k
Users

13.3k
Topics

125.1k
Posts