One of your disks need to be checked for consistency

Page 1 of 4 123 ... LastLast

  1. Posts : 7
    Windows 7 Ultimate (32-bits)
       #1

    One of your disks need to be checked for consistency


    Hey!

    I installed Windows 7 a few weeks ago, and every time I boot up, it says that one of my disks needs to be checked for consistency. The first two times, I let it check for errors, none were found. But it keeps wanting to check every time I boot up. Sometimes I skip, sometimes I let it check, with no errors found. Is there any way to make it go away? A setting or something?

    Thanks!
      My Computer


  2. Posts : 5,747
    7600.20510 x86
       #2

    It's all about the current flag set.

    Chkdsk /f starts up a run regardless of flag state, to ensure that errors are fixed. Should stop after you manually run the command and let it finish once cleanly.

    Run the above command from the command prompt (cmd.exe) by copying and pasting into it. Hit enter.
      My Computer


  3. Posts : 6
    windows 7
       #3

    I tried running the Chkdsk /f but "access denied as you do not have sufficient privileges. You may have to invoke this program running in elevated mode."

    What do I do now?
      My Computer


  4. Posts : 2,685
    Windows 7 Ultimate x86-64
       #4

    bre3550 said:
    I tried running the Chkdsk /f but "access denied as you do not have sufficient privileges. You may have to invoke this program running in elevated mode."

    What do I do now?
    Go into windows explorer, right click your disk and tick both boxes when you check for errors.
      My Computer


  5. Posts : 2,726
    Windows 7 Ultimate 64bit
       #5

    This used to work in XP and Vista ... haven't come across it in win7 but you could try it .. dunno if it will work

    The operating system would run ScanDisk on F: drive, stating that the computer did not shut down properly, and needs to be checked for consistency .... which is not true. The system then runs a full ScanDisk on drive F: and gives an error-free report. Then after that, each time it boots, it runs ScanDisk on F: drive all over again and finds no errors.

    Well this is what Windows refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.

    You will need to open a command prompt in administrator mode by right-clicking and choosing “Run as administrator” (or use the Ctrl+Shift+Enter shortcut from the search box)



    and then type

    fsutil dirty query f: (substitute the letter "f" with the drive that is giving you problems)

    To see the other commands for fsutil type fsutil plus /? or just type fsutil alone. Here is what you will see:

    fsutil
    ---- Commands Supported ----

    behavior Control file system behavior
    dirty Manage volume dirty bit
    file File specific commands
    fsinfo File system information
    hardlink Hardlink management
    objectid Object ID management
    quota Quota management
    reparsepoint Reparse point management
    sparse Sparse file control
    usn USN management
    volume Volume management

    This queries the drive, and more than likely it will tell you that it is dirty. Next, type

    CHKNTFS /X f:

    The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.

    Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing

    Chkdsk /f /r f:

    This should take you through 5 stages of the scan and will unset that dirty bit. this takes a while so be patient. Finally, type

    fsutil dirty query f:

    and Windows will confirm that the dirty bit is not set on that drive. It will give you this message:

    Volume - f: is NOT Dirty

    From here we are back to some sense of normality ....
      My Computer


  6. Posts : 6
    windows 7
       #6

    the command prompt is now telling me "The FSUTIL requires a local volume"

    now what?
      My Computer


  7. Posts : 6
    windows 7
       #7

    I just did ran it for the c drive and it says that c is dirty
      My Computer


  8. Posts : 2,726
    Windows 7 Ultimate 64bit
       #8

    Okidoki ... then you need to continue from here

    CHKNTFS /X f:

    The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.

    Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing

    Chkdsk /f /r f:

    This should take you through 5 stages of the scan and will unset that dirty bit. this takes a while so be patient. Finally, type

    fsutil dirty query f:

    and Windows will confirm that the dirty bit is not set on that drive. It will give you this message:

    Volume - f: is NOT Dirty

    From here we are back to some sense of normality ....
      My Computer


  9. Posts : 6
    windows 7
       #9

    getting some message when I type in the chkdsk/c/r c:

    The type of file system is NTFS
    Cannot lock current drive

    Chkdsk cannot run because the volume is in use by another process.
    Would you like to schedule this volume to be checked the next time the system restarts (Y/N)? I said Y and rebooted.

    Still coming up with a dirty c
      My Computer


  10. Posts : 2,726
    Windows 7 Ultimate 64bit
       #10

    bre3550 said:
    getting some message when I type in the chkdsk/c/r c:
    Wrong command you should be typing

    Chkdsk /f /r c:

    (need to read carefully before executing these commands )
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:22.
Find Us