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

partition shrink, no margin on C: after deploy

Scheduled Pinned Locked Moved Solved
FOG Problems
2
3
200
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.
  • L
    lebrun78
    last edited by Nov 25, 2019, 2:53 PM

    Hello,
    Working on 1.5.7.55 version, I have a problem using single disk -resible image.
    Working from a 250Go master with 34.1Go πŸ˜„ partition.
    Deploying on a 55Go VM for test, I get a full πŸ˜„ partition on deploy.
    I di not see any error during capturing and deploying

    Here are the defintion files of the image :

    cat win10light-1903/d1.fixed_size_partitions
    1
    
    cat win10light-1903/d1.minimum.partitions 
    label: dos
    label-id: 0x17fda016
    device: /dev/sda
    unit: sectors
    
    /dev/sda1 : start=        2048, size=     1021952, type=7, bootable
    /dev/sda2 : start=     1024000, size=    34329556, type=7
    /dev/sda3 : start=    76800000, size=      112166, type=7
    
     cat win10light-1903/d1.original.fstypes 
    /dev/sda2 ntfs
    /dev/sda3 ntfs
    
    cat win10light-1903/d1.partitions 
    label: dos
    label-id: 0x17fda016
    device: /dev/sda
    unit: sectors
    
    /dev/sda1 : start=        2048, size=     1021952, type=7, bootable
    /dev/sda2 : start=     1024000, size=    71680000, type=7
    /dev/sda3 : start=    76800000, size=    38541312, type=7
    

    Fog Version: Fog 1.5.10
    Server OS: AlmaLinux release 8.8

    1 Reply Last reply Reply Quote 0
    • Q
      Quazz Moderator
      last edited by Nov 25, 2019, 3:37 PM

      You have 2 resizable partitions.

      FOG attempts to maintain the percentage that those partitions take up for its resize logic.

      So, because your 2nd partition is approx 53% of πŸ˜„ it will attempt to organize the partitions as such on deployment too.

      But since your πŸ˜„ partition needs a minimum of 34GB of 55GB to function, that means that approx 62% is already taken up, forcing the system to allocate whatever remains to the other partition (D: presumably) to make sure it’s more or less the expected outcome.

      In other words; you need to either make the 2nd partition smaller before capture or deploy to a larger disk.

      L 1 Reply Last reply Nov 26, 2019, 7:38 AM Reply Quote 0
      • L
        lebrun78 @Quazz
        last edited by Nov 26, 2019, 7:38 AM

        @Quazz
        Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
        It’s clear for me now

        Fog Version: Fog 1.5.10
        Server OS: AlmaLinux release 8.8

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        1 / 1
        • First post
          3/3
          Last post

        194

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright Β© 2012-2024 FOG Project