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

    Deployement failed on smaller drive (message "Target partition size smaller")

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    19
    4.1k
    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.
    • Matthieu JacquartM
      Matthieu Jacquart @Quazz
      last edited by

      @Quazz No I didn’t see that, it appears on partclone screen during capture ?

      Fog 1.5.9.138
      Debian 11
      Vmware ESXi

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

        @Matthieu-Jacquart It should occur before and after capture, it’s just some text, but it should take some time, even on an SSD it will stay for a few seconds.

        What do the partition labels look like? I know FOG ignores partitions with certain labels (to avoid resizing the partition with the boot information on)

        And you’re sure the image type is resizable, yes?

        Matthieu JacquartM 1 Reply Last reply Reply Quote 0
        • Matthieu JacquartM
          Matthieu Jacquart @Quazz
          last edited by

          @Quazz I’m sure image type is single disk resizable, I’ve just check in fog.

          Here is a capture on PC with SSD 128GB (in french, sorry ;))

          0_1499087426298_fog.JPG

          I will try to look during capture if I saw text about resizing

          Fog 1.5.9.138
          Debian 11
          Vmware ESXi

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

            @Matthieu-Jacquart Your issue may be related to https://forums.fogproject.org/topic/10306/windows-10-resizable-image-system-partition-issue/13

            At the very least it needs to be addressed since your system reserved partition seems to be getting resized currently, which should never happen. This might potentially (but I don’t think so) cause the second partition to not get resized, but I’m not sure about that.

            Matthieu JacquartM 1 Reply Last reply Reply Quote 0
            • Matthieu JacquartM
              Matthieu Jacquart @Quazz
              last edited by

              @Quazz Ok I’ll take a look to this topic.
              But you’re right about resizing, usually I saw “resizing /sda2” (or something like that…) during few second just before partclone capture image, but on this image I don’t see this line, it’s too quick…

              Fog 1.5.9.138
              Debian 11
              Vmware ESXi

              1 Reply Last reply Reply Quote 0
              • Matthieu JacquartM
                Matthieu Jacquart
                last edited by

                No way, I create new image but once again sda2 is not resized… It’s a big problem for me, 3 pc of direction failed with deployment and people can’t work 😞

                Fog 1.5.9.138
                Debian 11
                Vmware ESXi

                1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott
                  last edited by

                  Why is the “main” partition reserved?

                  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

                  Matthieu JacquartM 1 Reply Last reply Reply Quote 0
                  • Matthieu JacquartM
                    Matthieu Jacquart @Tom Elliott
                    last edited by

                    @Tom-Elliott I don’t know, it’s the 500 MB parttion created by windows at installation 😉 There’s the same on my own computer.
                    But I think I understood what happened : it’s directly related to my previous problem with this image : https://forums.fogproject.org/topic/10313/error-capture-windows-10-creator-update-sysprep-could-not-open-inode-xxxxxx-through-the-library
                    I have 3 image Win10, for 2 of them after upgrade to 1703 no problem, but for the one which give me some trouble, I already have problem to capture image due to “inode” errror message precisely when resizing sda2…
                    But no solution fot the moment 😞

                    Fog 1.5.9.138
                    Debian 11
                    Vmware ESXi

                    1 Reply Last reply Reply Quote 0
                    • Matthieu JacquartM
                      Matthieu Jacquart
                      last edited by Matthieu Jacquart

                      Ok so I restart my image from scratch with usb installation key containing creators update and no problem to capture image with sysprep, resizing works fine and I can deploy on smaller SSD 😉
                      So it was certainly a bug in my previous image, thanks for your help

                      Fog 1.5.9.138
                      Debian 11
                      Vmware ESXi

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

                        @Matthieu-Jacquart I find that Windows 10 upgrades mess up sysprep, I’ve made it a habit to just start over every time.

                        Matthieu JacquartM george1421G 2 Replies Last reply Reply Quote 1
                        • Matthieu JacquartM
                          Matthieu Jacquart @Quazz
                          last edited by

                          @Quazz Yes, but this time I was lucky it was my smallest image with few software ! But it will be problematic for other images with dizains of software… Can you close the topic ? Thanks

                          Fog 1.5.9.138
                          Debian 11
                          Vmware ESXi

                          1 Reply Last reply Reply Quote 0
                          • george1421G
                            george1421 Moderator @Quazz
                            last edited by

                            @Quazz said in Deployement failed on smaller drive (message "Target partition size smaller"):

                            I’ve made it a habit to just start over every time.

                            We also find the same thing and create new every time.
                            FWIW: We use MDT to build the reference image, that way we have a consistent way to “start over every time”.

                            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!

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

                            190

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project