Solved: Volume dirty, Chkdsk won't run

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
I have the dirty bit set on my C: volume, but Chkdsk does not run on startup. How can I get it to run, or at least reset the dirty bit so I can run defrag?
 

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
I've tried running chkdsk /f in command prompt, if that's what you mean. It asks if I want to schedule a check for when the system starts and I choose yes. I've done that several times, and I've also tried going to C: properties>tools>error checking. Neither one works.
 

valis

Moderator
Joined
Sep 24, 2004
Messages
78,020
No, in the gui.....Disk Properties->Tools->Error Checking, let it run, if all comes back fine, tick them both again and reboot and let us know what happens.

thanks,

v
 

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
I tried that and the window just disappeared after about a minute. Tried it again-- same thing. Then I tried running chkdsk from the command prompt without the /f parameter and I got this:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>chkdsk
The type of the file system is NTFS.
Volume label is SQ004675V06.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
Attribute record (128, "") from file record segment 87766sed)
is corrupt.
Attribute record (128, "") from file record segment 210310sed)
is corrupt.
Attribute record (128, "") from file record segment 297042sed)
is corrupt.
Attribute record (128, "") from file record segment 335297sed)
is corrupt.
Attribute record (128, "") from file record segment 336115sed)
is corrupt.
Attribute record (128, "") from file record segment 344493sed)
is corrupt.
Attribute record (160, $I30) from file record segment 352186d)
is corrupt.
Attribute record (128, "") from file record segment 354757
is corrupt.
356160 file records processed.
File verification completed.
2599 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
C:\Windows\system32>
 

valis

Moderator
Joined
Sep 24, 2004
Messages
78,020
try chkdsk /f in safe mode. I've seen that succeed in the past where in normal instances it does not.
 
Joined
Nov 19, 2006
Messages
1,938
try this
from the command prompt window type in fsutil dirty query C:

This queries the drive, and more than likely it will tell you that it is dirty. Next type in CHKNTFS /X C:

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, now you want to do a Chkdsk manually by typing Chkdsk /r C:

This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type fsutil dirty query C: and Windows will confirm that the dirty bit is not set on that drive. Good luck!
 

valis

Moderator
Joined
Sep 24, 2004
Messages
78,020
thanks, Jack........knew about the fsutil, but not about the /x switch..........(y)
 

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
Chkdsk /r just does the same thing as chkdsk /f. It says, "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?" I tried choosing yes and restarting again but it still didn't do anything. I've also tried running chkdsk in safe mode, and that doesn't work either.
 

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
Yes, as I said in my last post, I did that. Fsutil confirms that the volume is dirty. When I type chkdsk /r, it just prompts me to schedule a check at startup, but it still won't run.
 

wacwacwac

Thread Starter
Joined
Jan 26, 2009
Messages
63
Okay, I finally figured it out. I had to hold down F8 while booting, select "repair windows," or something like that, then open the command prompt and run chkdsk from there.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top