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

Capture failed with step clearing ntfs flag failed

Scheduled Pinned Locked Moved Solved
FOG Problems
5
8
2.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.
  • G
    gchartrandCRL
    last edited by Apr 12, 2017, 2:43 PM

    Server
    • FOG Version: 1.3.5 SVN 6067
    • OS: CentOs 7.2
    Client
    • Service Version:
    • OS: Windows 7
    Description

    I try to capture an image from a HP prodesk 400 G3 but it always failed after the resize. It complains about maybe the Windows filesystem as an ntfs flag error. Before I run the capture, I run a chkdsk and even with Gparted I run a check on both partition, the boot and the OS partition but Nothing change. Before the resize when Fog try to cleaning the NTFS flag, it’s always in error with reg file not found.

    I try to ftp the image server with the user fog to test if it’s a connection problem but it’s working I can browse the /images folder and create folder. When the upload task begin, a folder in dev folder is created.

    After that my Windows 7 can’t boot and give me a BCD boot error. I need to deploy a image on it to correct it.

    I have enough space on the server too.

    Thanks for your help

    G 1 Reply Last reply Apr 12, 2017, 8:40 PM Reply Quote 0
    • G
      george1421 Moderator @gchartrandCRL
      last edited by Apr 12, 2017, 8:40 PM

      @gchartrandCRL could you post a clear picture of the error message taken with mobile phone. The context of the error is just as important as the error.

      it sounds like the ntfs dirty flag is set on that disk. The screen shot will tell us more.

      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
      • W
        Wayne Workman
        last edited by Apr 12, 2017, 11:51 PM

        also: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

        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/

        1 Reply Last reply Reply Quote 0
        • G
          gchartrandCRL
          last edited by Apr 19, 2017, 3:49 PM

          Hi, I try the wiki, but the way 1 didn’t work, the system said is already off, the way 2, I always reboot the Pc for capture and try the way 3 didn’t help.
          Here is the 2 screen capture
          0_1492616884947_IMG_2872.JPG !
          1_1492616884948_IMG_2874.JPG

          1 Reply Last reply Reply Quote 0
          • Q
            Quazz Moderator
            last edited by Quazz Apr 20, 2017, 3:42 AM Apr 20, 2017, 9:35 AM

            Failure to read NTFS $Bitmap is a serious one, indicating that either the filesystem needs to be repaired or the disk is dying. (broken sectors).

            You can check the latter with certain SMART tools (eg Crystaldisk on Windows)

            If the disk is fine, then you should first to use ntfsfix (boot a Linux livecd):

            sudo ntfsfix /dev/sdXX
            

            Try again and see if this helps, if it does not then, you should run chkdsk on both partitions. For that, you’ll have to temporarily set a drive letter to the boot partition, though, since chkdsk can only use drive letters and it doesn’t have one by default.

            You may have to use chkdsk /r instead of chkdsk /f if you’re using a traditional hard drive. This will take far longer, but if there are sector issues (non hardware based), this is the way to go.

            G 1 Reply Last reply Apr 21, 2017, 1:48 PM Reply Quote 0
            • G
              gchartrandCRL @Quazz
              last edited by Apr 21, 2017, 1:48 PM

              @Quazz
              it’s a brand new machine with SSD drive. I didn’t have problem when I deploy an image on it, it’s work fine. I try to run a chkdsk on both partition, the reserved one and the OS, no error at all. But when I try to capture it to another image, it’s failed and leave the reserved partition in RaW mode and shrink the partition to less possible.

              T 1 Reply Last reply Apr 21, 2017, 1:51 PM Reply Quote 0
              • T
                Tom Elliott @gchartrandCRL
                last edited by Apr 21, 2017, 1:51 PM

                @gchartrandCRL Might I suggest you try out the RC-6 of 1.4.0? 1.3.5 had a lot going for it in regards to disk resizing but it still wasn’t quite right. 1.4.0-RC-1 addressed a couple more issues, and I think 1.4.0-RC-3 was intended to fix the alignment issues that could happen on occasion. Mind updating to the RC and trying to capture the image? I know it likely means you need to rebuild the image, but it should work better.

                Also, when building your image, please make sure to disable fast boot.

                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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                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

                G 1 Reply Last reply Apr 21, 2017, 4:57 PM Reply Quote 1
                • G
                  gchartrandCRL @Tom Elliott
                  last edited by Apr 21, 2017, 4:57 PM

                  @Tom-Elliott Thanks Tom, the update resolved the issue. I upgraded to 1.4.0-RC7.

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

                  148

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project