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

    Capture Image partclone fail.

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    25
    3.9k
    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.
    • S
      sourceminer @george1421
      last edited by

      @george1421
      Thanks for the update, so the partclone error only specified the issue of the OS having dirty shutdown flags.

      • I have since while waiting for your reply, booted back into windows and again verified the disks are clean by running a check disk on boot. Waited for everything to be good. Re-ran sysprep and shut down and was about to capture again. I will also add the items you suggest. The Image is only 120 GB or so…

      5a4f72e7-db77-4428-a175-9573beccdf3c-image.png

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

        @sourceminer Ah, ok this now explains what is happening.

        How are you powering off this computer prior to capture?

        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!

        S 1 Reply Last reply Reply Quote 0
        • S
          sourceminer @george1421
          last edited by

          @george1421 I am having it shut down.

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

            @sourceminer sysprep is shutting it down or you are picking start button -> shutdown?

            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!

            S 1 Reply Last reply Reply Quote 0
            • S
              sourceminer @george1421
              last edited by

              @george1421 Sysprep is set to shutdown. Also the settings for Ram Disk were already at 275000, and the capture resize was changed from 7 to 10.

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

                @sourceminer Well… all of the probable issues seem to be a miss with this problem.

                Ok lets do what partclone is telling us.

                Schedule a debug capture if its still not in that state. Get to the FOS Linux command prompt on the target computer.

                at the command prompt key in fsck -t ntfs /dev/sda4 Lets check the file system in linux. This is a command guess. If the fsck program completes without issue then issue fog to single step through the image capture.

                I’m thinking there is something with that partition its not liking.

                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!

                S 1 Reply Last reply Reply Quote 0
                • S
                  sourceminer @george1421
                  last edited by

                  @george1421 I am waiting for this next iteration of capture finishes. Its at 80%

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    sourceminer @sourceminer
                    last edited by

                    @george1421
                    Ok so when I attempted to run fsck -t ntfs /dev/sda4 I got not found…
                    So I ran it as fsck -t ntfs dev/sda4 and it worked but didn’t seem to do anything or there were no errors Tried to run fog still an error. Very puzzling.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      sourceminer @sourceminer
                      last edited by

                      @george1421 Attempted to run through this article: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

                      • rerunning fog capture in debug to test.
                      S 1 Reply Last reply Reply Quote 0
                      • S
                        sourceminer @sourceminer
                        last edited by

                        @george1421 ok ran ntfsfix /dev/sda4 came back as good.
                        6cda3ff2-11be-4088-aece-2f2ee56c7265-image.png

                        Re-ran FOG and it still complained with same error… Not sure what else it could be.

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

                          @sourceminer ref: https://medium.com/@mikeycpham/using-clonezilla-to-image-and-getting-the-error-ntfclone-ng-c-ntfs-volume-dev-sd-is-7a467b617c4d

                          Clonezilla also sees this error.

                          In your case you will want to pxe boot into fog instead of usb booting clonezilla.

                          edit:
                          ref: https://askubuntu.com/questions/112150/how-to-correctly-fix-a-dirty-ntfs-partition-without-using-chkdsk

                          ntfsfix -d /dev/sdb1
                          

                          Clears the dirty flag.

                          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!

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            sourceminer @george1421
                            last edited by

                            @george1421 So yes I just ran that again… says it was processed successfully. Same as before. I will see if that -d did anything else

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              sourceminer @sourceminer
                              last edited by

                              @george1421 OK, finally, was able to capture the image successfully. This partition /dev/sda4 apparently was the recovery partition so all efforts prior to this (IE hibernation settings, and running chkdsk on the os volume were not the issue). What fixed the issue was running:

                              ntfsfix -d /dev/sda4

                              Suggestion: would it be a good idea to test these dirty flags prior to running the lengthy imaging process so that perhaps we don’t have to do so much guesswork.

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

                                @sourceminer said in Capture Image partclone fail.:

                                Suggestion: would it be a good idea to test these dirty flags prior to running the lengthy imaging process

                                I know there is a check for the dirty bit before imaging starts, but that might only be on the OS partition. Looking in the code I see a resetFlags function that actually runs the “ntfsfix -d” command. I’m not sure how its applied. I know if your drive contains the windows dirty bit the imager will stop before it starts deploying anything. So its not clear why it didn’t catch the issue on the 4th partition. But I do have to say its rare that the recovery partition would have been shut down uncleanly.

                                But in the end I’m glad you have it worked out.

                                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
                                • O
                                  Ouédraogo @george1421
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • 1
                                  • 2
                                  • 1 / 2
                                  • First post
                                    Last post

                                  215

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project