• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • 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.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.
  • M
    Matthieu Jacquart
    last edited by Jul 3, 2017, 9:59 AM

    Server
    • FOG Version: 1.4.4
    • OS: Debian 8
    Client
    • Service Version: 0.11.12
    • OS: Win10
    Description

    Hi,

    I have an image made on PC with SSD 128GB, I need to depoy this image on 2 laptop with SSD 60GB, and partclone give me error “Target partition size is smaller than source”

    0_1499075922334_WP_20170703_11_52_14_Pro.jpg

    d1.fixed_size_partitions
    :2

    d1.minimum.partitions :
    label: dos
    label-id: 0x86308630
    device: /dev/sda
    unit: sectors
    /dev/sda1 : start= 2048, size= 63840, type=7, bootable
    /dev/sda2 : start= 1094144, size= 248975360, type=7

    d1.partitions :
    label: dos
    label-id: 0x86308630
    device: /dev/sda
    unit: sectors
    /dev/sda1 : start= 2048, size= 1092096, type=7, bootable
    /dev/sda2 : start= 1094144, size= 248975360, type=7

    Thanks for your help !
    Matthieu

    Fog 1.5.9.138
    Debian 11
    Vmware ESXi

    1 Reply Last reply Reply Quote 0
    • M
      Matthieu Jacquart
      last edited by Matthieu Jacquart Jul 5, 2017, 1:32 AM Jul 5, 2017, 7:32 AM

      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 Jul 5, 2017, 7:57 AM Reply Quote 0
      • Q
        Quazz Moderator
        last edited by Quazz Jul 3, 2017, 4:07 AM Jul 3, 2017, 10:05 AM

        Looks like it put your second partition as non-resizable, but your first as resizable.

        I’m guessing that should be the other way around, so edit d1.fixed_size_partitions and change 2 to 1

        Though I’ll be interested in knowing how this happened.

        edit: Looking at it, this probably won’t work due to the minimum size specified in d1.minimum.partitions

        Under what version was this image captured? It IS set to resizable, yes?

        M 1 Reply Last reply Jul 3, 2017, 10:10 AM Reply Quote 0
        • M
          Matthieu Jacquart @Quazz
          last edited by Jul 3, 2017, 10:10 AM

          @Quazz Hi,
          I test multiple modification, but always same result :

          • I delete “:2” (empty file)
          • I replaced by “2” (without ":)
          • I replaced by “1”
          • I replaced by “:1”

          😞

          Fog 1.5.9.138
          Debian 11
          Vmware ESXi

          Q 1 Reply Last reply Jul 3, 2017, 10:20 AM Reply Quote 0
          • Q
            Quazz Moderator @Matthieu Jacquart
            last edited by Quazz Jul 3, 2017, 4:23 AM Jul 3, 2017, 10:20 AM

            @Matthieu-Jacquart The image size seems to indicated it being ~248GB large (it’s sectors not bytes facepalm) if I’m not mistaken.

            It lists that as minimum size for the partitions, so obviously resizing won’t do anything.

            Try to capture it again, I think something went wrong when this one was captured initially.

            tl;dr Minimum partition size is the same as the total size, thus resizing is impossible.

            M 1 Reply Last reply Jul 3, 2017, 12:04 PM Reply Quote 0
            • M
              Matthieu Jacquart @Quazz
              last edited by Jul 3, 2017, 12:04 PM

              @Quazz I capture this image once again, on another config but still with SSD 128GB, and unable to deploy it on the 2 laptops, same error…

              Fog 1.5.9.138
              Debian 11
              Vmware ESXi

              Q 1 Reply Last reply Jul 3, 2017, 12:56 PM Reply Quote 0
              • M
                Matthieu Jacquart
                last edited by Jul 3, 2017, 12:54 PM

                Same problem on 3 other computers with SSD 120GB instead of 128GB, I need to fix this issue in one hour :(n

                Fog 1.5.9.138
                Debian 11
                Vmware ESXi

                1 Reply Last reply Reply Quote 0
                • Q
                  Quazz Moderator @Matthieu Jacquart
                  last edited by Quazz Jul 3, 2017, 6:58 AM Jul 3, 2017, 12:56 PM

                  @Matthieu-Jacquart Did you see it try to resize the second partition during capture? It seems like it’s not doing that for some reason.

                  M 1 Reply Last reply Jul 3, 2017, 12:58 PM Reply Quote 0
                  • M
                    Matthieu Jacquart @Quazz
                    last edited by Jul 3, 2017, 12:58 PM

                    @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 Jul 3, 2017, 1:01 PM Reply Quote 0
                    • Q
                      Quazz Moderator @Matthieu Jacquart
                      last edited by Jul 3, 2017, 1:01 PM

                      @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?

                      M 1 Reply Last reply Jul 3, 2017, 1:10 PM Reply Quote 0
                      • M
                        Matthieu Jacquart @Quazz
                        last edited by Jul 3, 2017, 1:10 PM

                        @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 Jul 3, 2017, 1:16 PM Reply Quote 0
                        • Q
                          Quazz Moderator @Matthieu Jacquart
                          last edited by Jul 3, 2017, 1:16 PM

                          @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.

                          M 1 Reply Last reply Jul 3, 2017, 1:21 PM Reply Quote 0
                          • M
                            Matthieu Jacquart @Quazz
                            last edited by Jul 3, 2017, 1:21 PM

                            @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
                            • M
                              Matthieu Jacquart
                              last edited by Jul 3, 2017, 1:42 PM

                              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
                              • T
                                Tom Elliott
                                last edited by Jul 3, 2017, 2:13 PM

                                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

                                M 1 Reply Last reply Jul 4, 2017, 6:57 AM Reply Quote 0
                                • M
                                  Matthieu Jacquart @Tom Elliott
                                  last edited by Jul 4, 2017, 6:57 AM

                                  @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
                                  • M
                                    Matthieu Jacquart
                                    last edited by Matthieu Jacquart Jul 5, 2017, 1:32 AM Jul 5, 2017, 7:32 AM

                                    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 Jul 5, 2017, 7:57 AM Reply Quote 0
                                    • Q
                                      Quazz Moderator @Matthieu Jacquart
                                      last edited by Jul 5, 2017, 7:57 AM

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

                                      M G 2 Replies Last reply Jul 5, 2017, 8:17 AM Reply Quote 1
                                      • M
                                        Matthieu Jacquart @Quazz
                                        last edited by Jul 5, 2017, 8:17 AM

                                        @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
                                        • G
                                          george1421 Moderator @Quazz
                                          last edited by Jul 5, 2017, 9:50 AM

                                          @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
                                          1 / 1
                                          • First post
                                            9/19
                                            Last post

                                          158

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project