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

    Partition Resizing

    Scheduled Pinned Locked Moved
    General Problems
    3
    11
    1.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.
    • imagingmaster21I
      imagingmaster21
      last edited by

      So we just noticed an issue with our FOG imaging regarding the partitions being resized. This is occurring on two Windows 10 images, one is Professional and one is Enterprise. Both images were sysprepped with copy profile from the local admin account.

      • Windows 10 Enterprise 1809 image was built on 237gb Samsung SSD

      • Windows 10 Professional 1809 image was built on 110gb NVME drive.

      When you image machines that have larger disk space it does not resize to the larger size. So for instance if you image a 500gb drive to te enterprise image it will say the C:\ drive has 237gb and the missing amount will be unallocated. Luckily you are able to easily expand it in Disk Manager so it shows the correct amount. I am wondering why the imaging is not properly resizing even thought I have single disk resizable selected.

      Below are the screenshots of both images that have the same issue.
      student.PNG

      standard.PNG

      It is possible we may have had this issue longer and did not notice it since most of our machines are SSDs and are not very large size drives. We are running 1.5.2 right now but would like to avoid updating to fix this issue if at all possible. Any suggestions?

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @imagingmaster21 Please post the following three files for both the images you see this issue with: d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions

        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
        • imagingmaster21I
          imagingmaster21
          last edited by

          @Sebastian-Roth

          Here is for the Enterprise Win 10 1809 Image:
          d1.partitions

          label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3366A936-7B65-43E1-AFDF-9DE4F8FE13A7, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0DBFD8B3-44AC-4600-926D-FDFB469EFF2A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=BC00D195-83B5-4B15-BFF8-DDCEC9B3ADFF, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   498855936, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=890554EA-E1AB-4D7F-8C9D-7F8C83FA2A62, name="Basic data partition"

          d1.minimum.partitions

          label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3366A936-7B65-43E1-AFDF-9DE4F8FE13A7, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0DBFD8B3-44AC-4600-926D-FDFB469EFF2A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=BC00D195-83B5-4B15-BFF8-DDCEC9B3ADFF, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=    79997904, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=890554EA-E1AB-4D7F-8C9D-7F8C83FA2A62, name="Basic data partition"

          d1.fixed_size_partitions

          :2:3:1

          Then here is the files for the 1809 Win 10 Pro image

          d1.partitions

          label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=13FC5702-27F9-49D6-8A69-F39933A23D1D, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=12D97EEC-C05D-4AB2-85FC-E279C488B16C, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=7DEE0FD7-4583-417C-9FCE-58C0396BD356, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   248807936, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CB038B33-4E54-441D-80A5-6F8614224912, name="Basic data partition"

          d1.minimum.partitions

          label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=13FC5702-27F9-49D6-8A69-F39933A23D1D, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=12D97EEC-C05D-4AB2-85FC-E279C488B16C, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=7DEE0FD7-4583-417C-9FCE-58C0396BD356, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=    67678380, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CB038B33-4E54-441D-80A5-6F8614224912, name="Basic data partition"

          d1.fixed_size_partitions

          :2:3:1

          I think these are mainly the same, let me know what we should changed? Maybe the 2:3:1?

          1 Reply Last reply Reply Quote 0
          • fry_pF
            fry_p Moderator
            last edited by

            @Sebastian-Roth I want to chime in that I just had an issue with expansion as well. I don’t have the specific partition info at the moment, but I can tell you that I have FOG 1.5.6, the image (win10 x64 1903) was built on a 128 GB drive and deployed to a 256 GB drive. It followed the same pattern as the OP, the drive did not expand at all. I can make a new topic if you would like and I can do some testing later

            Like open source community computing? Why not do it for a good cause?
            Use your computer/server for humanitarian projects when it is idle!
            https://join.worldcommunitygrid.org?recruiterId=1026912

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @fry_p We definitely need the exact partition info from your particular image. Please open a new topic on that one.

              @imagingmaster21 I have not had the time to try and replicate the issue with the information you gave me. Will try to do so tomorrow. But as a first quick shot you can try updating the init files as I have fixed an issue that only came along when using FOG with NVMe drives. Could be the problem in your case.

              You can download the new inits here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/88/artifacts/

              As well you need to adjust a setting as the new inits use a larger root filesystem. Please go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

              There should be no need to re-capture the image. Just put the new inits in place and try deploying the image again.

              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

              fry_pF imagingmaster21I 3 Replies Last reply Reply Quote 0
              • fry_pF
                fry_p Moderator @Sebastian Roth
                last edited by

                @Sebastian-Roth my issue may have been a fluke. I sat down and set up the same scenario as in my first reply twice and the image expanded perfectly. I will certainly make a new post if it happens again, but it did happen on a production machine so it was corrected manually so the user could utilize all of the space. I also was not the one working on it. I will pay closer attention if it happens again.

                Like open source community computing? Why not do it for a good cause?
                Use your computer/server for humanitarian projects when it is idle!
                https://join.worldcommunitygrid.org?recruiterId=1026912

                imagingmaster21I 1 Reply Last reply Reply Quote 0
                • imagingmaster21I
                  imagingmaster21 @fry_p
                  last edited by

                  @fry_p @Sebastian-Roth

                  Do you think something needs changed in my d1.fixed_size_partitions file?

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by

                    @imagingmaster21 Please see my last post! Update the inits and see if that makes a difference…

                    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
                    • imagingmaster21I
                      imagingmaster21 @Sebastian Roth
                      last edited by

                      @Sebastian-Roth
                      So when I download the inits where do I put them at specifically on the FOG Server?

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @imagingmaster21 Put those in /var/www/html/fog/service/ipxe/ and I’d suggest you rename the original ones beforehand just so you have a backup copy of those in case something goes wrong with the new ones.

                        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
                        • imagingmaster21I
                          imagingmaster21 @Sebastian Roth
                          last edited by

                          @Sebastian-Roth

                          It looks like these files fixed the issue. 🙂

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

                          188

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.1k

                          Posts
                          Copyright © 2012-2024 FOG Project