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

Manipulating Partition Sizes of Captured Image For Deployment

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
11
3.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.
  • S
    sudburr
    last edited by sudburr Oct 11, 2016, 2:39 PM Oct 11, 2016, 8:26 PM

    Server
    • FOG Version: RC10 or higher
    • OS: CentOS_7.2.1511
    Client
    • Service Version: n/a
    • OS: any Windows 10 version
    Description

    An original Windows 10 installation with a WinRE partition is on a 256 GB HDD consisting of 3 partitions

    1= 260 MiB (EFI System Partition)
    2= 236 GiB NTFS (Boot, Page File, Crash Dump, Primary Partition)
    3= 1000 MiB (Recovery Partition)

    Without rebuilding the install is there a way to massage the captured image files to be able to deploy onto a different size HDD (eg: a smaller 128 GB) that maintains the sizes of partitions 1 and 3, but resizes partition 2 to fill the available remaining (larger or smaller) space?

    The original was captured as Single Disk Resizable.

    [ Standing in between extinction in the cold and explosive radiating growth ]

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Oct 11, 2016, 9:14 PM

      Is partition 2 not already resized?

      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
        sudburr
        last edited by Oct 12, 2016, 5:18 PM

        Partition 2 resizes, but so does Partition 3. I don’t want Partition 3 to resize, only Partition 2.

        Correct me if I’m wrong, but as I understand the Windows 10 Recovery Environment partition as the operating system receives major updates, it also updates the Recovery Partition.

        When FOG deploys the image it resizes partition 3 unacceptably smaller. I want to maintain the original size of the WinRE partition.

        [ Standing in between extinction in the cold and explosive radiating growth ]

        T 1 Reply Last reply Oct 12, 2016, 5:25 PM Reply Quote 0
        • T
          Tom Elliott @sudburr
          last edited by Oct 12, 2016, 5:25 PM

          @sudburr We don’t know what partition will become the recovery partition, not in the least.

          That said, if you alter the d1.fixed_size_partitions file and add the partition number you need to be fixed, (additionals are separated by colons) you should be good.

          For example:

          d1.fixed_size_partitions might have: 1:3 meaning partitions 1 and 3 must be of a “fixed” size.

          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
            sudburr
            last edited by sudburr Oct 12, 2016, 12:06 PM Oct 12, 2016, 6:05 PM

            Interestingly, the d1.fixed_size_partitions file contains:

            1:2:1

            A second :1 ?

            Looking closer at the original drive, there are actually 4 partitions.

            1 System 260 MB
            2 Reserved 16 MB
            3 Primary 240 GB
            4 Recover 1000 MB

            Hmm.

            For now I will try a deployment with 1:2:1:4 and see what happens; while I furrow my brow at that mystery `Reserved’ partition.

            [ Standing in between extinction in the cold and explosive radiating growth ]

            T 1 Reply Last reply Oct 12, 2016, 6:12 PM Reply Quote 0
            • T
              Tom Elliott @sudburr
              last edited by Oct 12, 2016, 6:12 PM

              @sudburr You can remove one of the 1’s. This image was likely created semi-fairly in the past?

              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
                sudburr
                last edited by Oct 12, 2016, 6:14 PM

                The image was created September 28th with RC10.

                [ Standing in between extinction in the cold and explosive radiating growth ]

                1 Reply Last reply Reply Quote 0
                • S
                  sudburr
                  last edited by Oct 12, 2016, 6:33 PM

                  How does FOG determine if a partition is resizable when it is capturing? Is it strictly a file system match or does it look at the partition’s flag or type?

                  [ Standing in between extinction in the cold and explosive radiating growth ]

                  1 Reply Last reply Reply Quote 0
                  • S
                    sudburr
                    last edited by sudburr Oct 12, 2016, 12:36 PM Oct 12, 2016, 6:35 PM

                    I just captured the original drive with RC13 and it again generates a d1.fixed_size_partitions with:

                    :1:2:1

                    [ Standing in between extinction in the cold and explosive radiating growth ]

                    T 1 Reply Last reply Oct 12, 2016, 6:36 PM Reply Quote 0
                    • T
                      Tom Elliott @sudburr
                      last edited by Oct 12, 2016, 6:36 PM

                      @sudburr That’s not the end of the world.

                      Basically anything before the “main” partition is calculated as fixed. Also, an partition that is not of a resizable type (ext or ntfs) will be listed in there.

                      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
                        sudburr
                        last edited by sudburr Oct 12, 2016, 1:38 PM Oct 12, 2016, 7:29 PM

                        The original HDD as reported by Gnome Partition Editor 0.26.1-5:

                        Partition | Name | Label | File System | Flags
                        /dev/sda1 | EFI system partition |  | fat32 | boot, hidden, esp
                        /dev/sda2 | Microsoft reserved partition |  | unknown | msftres
                        /dev/sda3 | Basic data partition | Windows |ntfs | msftdata
                        /dev/sda4 | Basic data partition | WinRE_DRV |ntfs | hidden, diag
                        

                        Editing d1.fixed_size_partitions of the captured image to be:

                        :1:2:4
                        

                        … then deploying the image to a smaller HDD results in this:

                        * Attempting to expand/fill partitions ... Done
                        * Seems like you are trying to restore to an empty disk.  Be aware this will most probably cause trouble.
                        
                        Attempting to deploy image
                        Using Partclone
                        
                        An error has been detected!
                        
                        No image file(s) found that would match the partition(s) to be restored (performRestore>
                        Args Passed: /dev/sda /images/test all
                        
                        Computer will reboot in 1 minute
                        

                        Deploying the same image to a larger (500 GB) HDD results in:

                        Partition | Name | Label | File System | Flags
                        /dev/sda1 | EFI system partition |  | fat32 | boot, esp
                        /dev/sda2 | Microsoft reserved partition |  | unknown | msftres
                        /dev/sda3 | Basic data partition | Windows | ntfs | msftdata (still shrunk at 25.4 GB)
                        unallocated (211.82 GB)
                        /dev/sda4 | Basic data partition | WinRE_DRV | ntfs | hidden, diag (correctly sized to 1000 MB)
                        unallocated (227.29 GB)
                        

                        GParted initially launches with this error:

                        Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 2014 blocks) or continue with the current setting?
                        

                        Selecting FIX or IGNORE doesn’t change the partitions.

                        So it more or less mirrored the original 256 GB HDD layout onto the 500 GB HDD leaving the extra space after sda4 empty, instead of dumping sda4 onto the end of the space, then expanding sda3 into the donut hole.

                        [ Standing in between extinction in the cold and explosive radiating growth ]

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        1 / 1
                        • First post
                          9/11
                          Last post

                        197

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project