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

    "Image size: ON CLIENT" shows the total size of the captured disk

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    2
    3
    567
    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.
    • T
      Tauric
      last edited by Tauric

      Hi all,

      I have 4 images in my FOG server at the moment, they all show the correct ON CLIENT size aside from one, for some reason it is showing the size of the fixed disk that I captured from (64.01gb)

      7f2121e6-4754-497a-ac64-dbc41059f717-image.png

      I doubt this is anything more than a cosmetic issue as images deploy fine and show the correct size after deployment, however I was wondering if there’s any easy fix for this? I tried recapturing but the size didn’t change.

      d1.minimum.partitions (below) shows the Microsoft Reserved Partition as 132892160 sectors, which at 512kb per sector in gibibytes is 63.37GB.

      d1.minimum.partitions.txt

      The deployment looks odd as the total block progress is at a lower percentage than the data block process, it does show the actual space in use on the image as 17.1GB which is correct:

      03b49c62-e87f-4742-97b7-8a86c548ff3c-image.png

      when this partition finishes the total block progress jumps to 100%

      Edit: A normal deployment at part 3 for reference:

      2fba4dfd-31ba-419d-9a92-5746c662421a-image.png

      As far as I can see none of the settings are different between images.

      Thanks for any suggestions ❤

      T 1 Reply Last reply Reply Quote 0
      • T
        Tauric @Tauric
        last edited by

        @Tauric

        I guess its just something wrong with this specific build of windows, I freshly reinstalled windows and setup the image again, this time it seems to be capturing the correct size

        Still not sure what the issue here was, I guess fog was unable to resize the partition?

        3cfde62d-826a-47f6-8cd6-4e8f751cb892-image.png

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

          @Tauric From the pictures we see that FOG recognized the filesystem as NTFS and should be able to resize it. It’s still strange the size was larger. Good you got this fixed by reinstalling the master to capture from. No idea what could have been wrong with the other one.

          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 1
          • [[undefined-on, S Sebastian Roth, ]]
          • 1 / 1
          • First post
            Last post

          186

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project