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

    Hard drive space issues when deploying image

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    3
    9
    585
    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.
    • C
      CJR_ie
      last edited by

      Hi
      Recently ran into this problem. I captured my image as per normal but went to deploy it to a new 120GB SSD it has shrunk the hard drive to 55GB

      I never changed resizing options before. What should I do?

      What has went wrong? Help!!

      0_1539975823234_19-10-2018 19-54-21.jpg

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @CJR_ie
        last edited by

        @CJR_ie What version of Fog are you using?

        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!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        C 2 Replies Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by

          @CJR_ie said in Hard drive space issues when deploying image:

          it has shrunk the hard drive to 55GB

          What do you mean by that? Do you refer to the “Image Size: ON CLIENT” figure of 55.90 GiB? That is just roughly the amount of data stored on the client and is more or less just the lowest limit of disk size that image can be deployed to. But if you deploy that resizable image to a 120 GB SSD it should expand to the full 120 GB. Please post a picture of windows disk manager after you deployed that image to a machine.

          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

          C 1 Reply Last reply Reply Quote 0
          • C
            CJR_ie @Wayne Workman
            last edited by

            @Wayne-Workman Running Version 1.4.4

            1 Reply Last reply Reply Quote 0
            • C
              CJR_ie @Sebastian Roth
              last edited by

              @Sebastian-Roth 0_1540204649690_Capture.JPG

              1 Reply Last reply Reply Quote 0
              • C
                CJR_ie @Wayne Workman
                last edited by

                @Wayne-Workman 0_1540205161001_Capture2.jpg

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

                  @CJR_ie Please post the contents of d1.partitions, d1.original.partitions and d1.fixed_size_partitions - files are in /images/IMAGENAME on your FOG server.

                  Is upgrading to the latest FOG version 1.5.4 an option for you? If it turns out to be an issue with 1.4.4 we won’t be able to help properly as we can’t support back porting fixes to older versions.

                  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

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    CJR_ie @Sebastian Roth
                    last edited by

                    @Sebastian-Roth

                    d1.partitions:
                    label: dos
                    label-id: 0x86308630
                    device: /dev/sda
                    unit: sectors

                    /dev/sda1 : start= 2048, size= 204800, type=7, bootable
                    /dev/sda2 : start= 206848, size= 117024256, type=7

                    d1.original.partitions:
                    /dev/sda2 ntfs

                    d1.fixed_size_partitions:
                    :1:2

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

                      @CJR_ie Here you go. FOG detects your windows system partition to be fixed as well and therefore does not expand it on deployment. Edit the file d1.fixed_size_partitions by hand using a text editor and make it read

                      :1
                      

                      Then schedule a new deploy task for your host and it should expand to the full SSD size properly.

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

                      130

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.4k

                      Posts
                      Copyright © 2012-2024 FOG Project