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

Failed to complete capture (savePartition)

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
7
3.6k
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.
  • R
    riko
    last edited by Mar 27, 2017, 8:30 AM

    Server
    • FOG Version: 1.3.4
    • OS: Debian8
    Client
    • Service Version:
    • OS: Ubuntu 16 et Windows7 (dualboot)
    Description

    Hello,
    When I try to capture an image from my server,
    I get the error message “Failed tro complete capture”.
    However, my hard drive is almost empty.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Mar 27, 2017, 9:52 AM

      Would you post a clear screen shot of the error (taken with a mobile). Its important to see the context of the error (i.e. the dialog before and after the error).

      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
      • R
        riko
        last edited by Mar 27, 2017, 10:25 AM

        Ok, no problem. This is the link:
        Lien du screen

        I have the same error message.

        G 1 Reply Last reply Mar 27, 2017, 11:53 AM Reply Quote 0
        • G
          george1421 Moderator @riko
          last edited by george1421 Mar 27, 2017, 5:54 AM Mar 27, 2017, 11:53 AM

          @riko We had the same issue in another thread. In that case there was a physical issue with the hard drive. What we found if you watch the process (very carefully) while partclone is deploying the image. Partclone will abort part of the way through the deployment and print the error on the screen for less than 1 second. When it aborts FOG only knows that it stopped in the middle of the deployment and it doesn’t know why so it guesses the most likely cause (FOG server disk space).

          So, what I want you to try is to see if the reported issue is ONLY with this specific target computer by trying to upload another target. You can try to capture this system again and closely watch the partclone process for partition 3 and see if you can read the error (quickly).

          ref link: https://forums.fogproject.org/topic/9758/fog-upload-issues

          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!

          R 1 Reply Last reply Mar 27, 2017, 12:30 PM Reply Quote 0
          • R
            riko @george1421
            last edited by Mar 27, 2017, 12:30 PM

            @george1421
            The partclone starts and a few minutes later, a message of error came “extfsclone: bitmap free count err partclone get free:14450300 but extfs get 14450386”.
            Clic here
            The screen look like my error message.

            1 Reply Last reply Reply Quote 0
            • R
              riko
              last edited by Mar 28, 2017, 8:02 AM

              First, i get this error message at cloning.
              0_1490688126930_Error2.jpg
              Then, few secandes after:
              0_1490687886147_Error.jpg

              G 1 Reply Last reply Mar 28, 2017, 10:01 AM Reply Quote 0
              • G
                george1421 Moderator @riko
                last edited by Mar 28, 2017, 10:01 AM

                @riko with this error, it appears to be a software error on the target computer’s hard drive. Clonezilla and FOG uses the same disk cloning engine called partclone. I found this answer on the clonezilla site: http://drbl.org/faq/fine-print.php?path=./2_System/108_bitmap_free_count_err.faq#108_bitmap_free_count_err.faq

                It says:
                "You should make sure the file system integrity is OK before you save it as an image, i.e. the file system is unmounted cleanly. If you want to check and repair the file system, you can run “fsck” on GNU/Linux or ‘chkdsk /f’, ‘chkdsk /p /r’ on MS Windows. For GNU/Linux file system, e.g. ext4, reiserfs, you can also check option “-fsck-src-part-y” when you save an image. "

                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
                  6/7
                  Last post

                231

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project