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

    Customized image of Windows10 1803 RS4, partition resize issue

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    3
    13
    1.0k
    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.
    • R
      Rayco
      last edited by

      For more details, I attached some SS.

      Template image:
      0_1533630236117_44.JPG

      Source master image in ssd 30Gb:
      0_1533629107224_22.PNG

      Deployed to HDD 1Tb:
      0_1533629187129_33.PNG

      I tryed to swap system partition with recovery, with the same issue, deployed:
      0_1533630100644_1.PNG

      0_1533630123892_333.PNG

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

        @Rayco Can you please post the contents of d1.fixed_size_partitions, d1.minimum.partitions and d1.partitions which you find in the image directory on your FOG server (/images/Win10ProfeQi1803/...).

        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

        R 1 Reply Last reply Reply Quote 0
        • R
          Rayco @Sebastian Roth
          last edited by Rayco

          @sebastian-roth Thanks for response.

          d1.fixed_size_partitions

          :1:2:4
          

          d1.minimum.partitions

          label: gpt
          label-id: FAD8F34F-08FC-4068-8435-9AFFAAA13980
          device: /dev/sda
          unit: sectors
          first-lba: 34
          last-lba: 60460795
          
          /dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CFDA3487-867C-48F9-8177-810EF4EB6F0C, name="EFI system partition", attrs="GUID:63"
          /dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=24E9E9B1-D1A8-4FED-818C-60FF804F64E7, name="Microsoft reserved partition", attrs="GUID:63"
          /dev/sda3 : start=      239616, size=    27075584, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7359A249-2F8A-42E8-AFDB-48FD43250DC5, name="Basic data partition"
          /dev/sda4 : start=    58615808, size=     1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=68BF7C08-141B-4607-BC65-A537B0ECDC5E, name="Basic data partition", attrs="RequiredPartition GUID:63"
          
          

          d1.partitions

          label: gpt
          label-id: FAD8F34F-08FC-4068-8435-9AFFAAA13980
          device: /dev/sda
          unit: sectors
          first-lba: 34
          last-lba: 60460795
          
          /dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CFDA3487-867C-48F9-8177-810EF4EB6F0C, name="EFI system partition", attrs="GUID:63"
          /dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=24E9E9B1-D1A8-4FED-818C-60FF804F64E7, name="Microsoft reserved partition", attrs="GUID:63"
          /dev/sda3 : start=      239616, size=    58376192, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7359A249-2F8A-42E8-AFDB-48FD43250DC5, name="Basic data partition"
          /dev/sda4 : start=    58615808, size=     1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=68BF7C08-141B-4607-BC65-A537B0ECDC5E, name="Basic data partition", attrs="RequiredPartition GUID:63"
          
          
          1 Reply Last reply Reply Quote 0
          • Q
            Quazz Moderator
            last edited by

            That’s strange, it claims there’s a 4th partition, but I don’t see it in your disk management screenshot.

            R 1 Reply Last reply Reply Quote 0
            • R
              Rayco @Quazz
              last edited by

              @quazz I deployed on a 500gb hard drive in search of patterns, with the same result.

              0_1534159668968_Captura.PNG

              Q 1 Reply Last reply Reply Quote 0
              • Q
                Quazz Moderator @Rayco
                last edited by

                @rayco Yes, but FOG records the partitions from the source system, which only has 3 partitions, so I don’t know why it thinks there are 4?

                Are you 100% sure this is the correct image? When was it last captured?

                R 1 Reply Last reply Reply Quote 0
                • R
                  Rayco @Quazz
                  last edited by

                  @quazz The weekend I deleted all images I had created in 1803, and today to pass you the logs of the partitions I did the whole process of capture and deploy again.

                  Could it be because the recovery partition is hidden?

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

                    @rayco Ok, let me try to interpret your partition table:

                    sda1 - type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B: EFI boot partition, size matches the 100 MB seen in disk management picture
                    sda2 - type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE: Microsoft Reserved Partition, only about 32 kilobytes in size. Not sure but partition flags might hide this one from disk management.
                    sda3 - type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7: That’s your windows system partition. This is the only partition FOG is able and willing to resize.
                    sda4 - type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC: Windows Recovery Environment partition. This partition is hindering FOG from expanding your main system partition as it cannot move the start of this one without breaking the recovery option.

                    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

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      Rayco @Sebastian Roth
                      last edited by

                      @sebastian-roth correctly, I’m sure the problem is recovery partition.

                      I’m traying diferents methods but with unlucky results.

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

                        @rayco said in Customized image of Windows10 1803 RS4, partition resize issue:

                        I’m traying diferents methods but with unlucky results.

                        What exactly have you tried and which errors occurred? We can’t help without knowing more details from you.

                        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

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          Rayco @Sebastian Roth
                          last edited by

                          @sebastian-roth I have changed the partition part of recovery using partedmagic, placing the recovery before the partition of the system, with an identical result, but with great detail, once the deploy is done I can extend the partition of the system from within the windows itself, using the graphic environment in disk manager, extend partition. But the recovery stops working. I understand that this happens because the partition is not where the system points.

                          I am thinking that an easy solution would be to find in the bowels of Microsoft EDT the way in which it creates the partitions automatically and force it to place the partition originally before the one of the system.

                          1 Reply Last reply Reply Quote 0
                          • R
                            Rayco
                            last edited by

                            Finally, I had to reinstall FOG and everything was fixed.

                            Thanks guys for the answers.

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

                            161

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project