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

    A couple images won't shrink/resize on capture..

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    2
    5
    531
    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.
    • G
      geardog
      last edited by geardog

      I’ve captured most of the boxes around the house, but a couple of them don’t appear to resize. FOG tells me I’m capturing 232GB images.

      During capture the bar says it is basically done at 122GB.

      0_1537890794659_0a2b2a68-9932-4e2d-baec-7a8585f81559-image.png

      Image lists show it at 232GB
      0_1537890876137_cb69eed1-d927-4201-99c2-db6a106171fc-image.png

      The folder shows something like 42GB
      0_1537891125542_255a9808-b6b5-46a8-9e47-23b5b086f23e-image.png

      I’ve run cleanup, chkdsk, & defrags. These boxes aren’t encrypted.

      Any tips to get these to behave/report properly?

      george1421G 1 Reply Last reply Reply Quote 0
      • G
        geardog @george1421
        last edited by geardog

        @george1421

        I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.

        Nice thought, but the thread you note doesn’t hold my solution.
        https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
        Bit locker is off as evidenced by the encryption control commands.
        manage-bde -off 😄
        manage-bde -status 😄

        “Way 1” from the FOG wiki made no change either.
        https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

        I believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.

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

          @geardog When the image is being captured by fog. Look at the partclone screen. My bet is that it is being captured in RAW mode. If that is the case my bet is that bitlocker is enabled on that disk, even if you have it never turned on to start.

          ref: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43

          Please run through the commands by @THEMCV and recapture again. Disk encryption will stop it from shrinking the disk

          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!

          G 1 Reply Last reply Reply Quote 1
          • G
            geardog @george1421
            last edited by geardog

            @george1421

            I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.

            Nice thought, but the thread you note doesn’t hold my solution.
            https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
            Bit locker is off as evidenced by the encryption control commands.
            manage-bde -off 😄
            manage-bde -status 😄

            “Way 1” from the FOG wiki made no change either.
            https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

            I believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.

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

              @geardog Excellent job finding the problem!! Is it ok to close this case then?

              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!

              G 1 Reply Last reply Reply Quote 0
              • G
                geardog @george1421
                last edited by

                @george1421

                I consider it resolved. Thanks for chiming in.

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

                158

                Online

                12.1k

                Users

                17.3k

                Topics

                155.3k

                Posts
                Copyright © 2012-2024 FOG Project