Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 930
  • Last Modified:

Reluctant reset of dirty bit

How can I reset a reported dirty bit when << chkdsk /f and /r >> show no problem, and running << chkdsk /r >> through recovery console does not resolve? (Win XP Pro).

I have also tried using a new hard disk (employing a mirror image of original) but problem remains.

Short of reformatting and reloading everything bit by bit on one of the hard drives, is there anything else I can try?
0
mike_oram
Asked:
mike_oram
  • 5
  • 4
  • 2
1 Solution
 
theProfessaCommented:
To fix this problem you should go to Start -> Run -> "cmd"

In the command prompt type in "fsutil dirty query X:"  x being the drive in question
This checks to see if the drive is dirty or not.

Next type in "CHKNTFS /X D:"  <- This tells Windows not to check the drive at the next startup.
Reboot the computer and do a manual CHKDSK by typing "Chkdsk /f /r d:"  This will do a full check up and remove the dirty bit
Then type in "fsutil dirty query x:" to confirm that the drive is no longer dirty and you should be set.

Hopefully this helps!
0
 
mike_oramAuthor Commented:
Tks Professa but I have already done precisely all that (which prompted my question here) - except the drive in question is c: , which I take should appear where you have "d:"...
If that is not correct and I need to put "d:" even though my problem drive is c: , please let me know.
0
 
theProfessaCommented:
My mistake, C: is correct.
You can try this registry edit from:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Go to Disable or Enable Check Disk on boot
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mike_oramAuthor Commented:
Tks again Professa but I sense that would only hide my problem upon boot; not solve it. If the dirty bit remains set I cannot (eg) defragment.
0
 
nobusCommented:
it is possible the disk has a problem; i suggest running the disk diag you need :   http://www.tacktech.com/display.cfm?ttid=287
0
 
mike_oramAuthor Commented:
Thank you Nobus. I have in fact alrady run all HD tests using SeaTools for Windows (my system hard drives are Seagate and Maxtor) and they show up fine.  Whenever I run tests for a 'dirty bit' on both drives, the drive booted from shows DIRTY, whereas the other shows NOT dirty. If I swap over through reboot, that which earlier showed NOT dirty is then (as C:) reported as DIRTY.

From all this I am wondering if it is the MFT that is somehow corrupt (having been loaded as a mirror image).  The MFT each drive is in two fragments which, under normal conditions I understand should in itself not be a problem.  I have tried increasing the MFT to much higher size (4GB) but to no effect upon the problem.
0
 
nobusCommented:
did you image those drives?  then you copied the problem on both...
0
 
mike_oramAuthor Commented:
Yes, I imaged...as my original post.
0
 
nobusCommented:
try running chkdsk from safe mode :
>>>  . Finally I tried a chkdsk /f from a Command prompt in Safe Mode. To my surprise this worked and solved the problem. Why the use of Safe Mode made a difference escapes me having many times seen the same checks executed at boot up before Windows starts up.   <<< 
from :
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21469100.html
 
0
 
mike_oramAuthor Commented:
Thanks nobus,

Before I received your last post I tried another solution myself which has appeared to work splendidly. If the problem of a recaletrant dirty bit comes up again, I shall certainly try what you have suggested.

The solution that has worked my my case has been achieved through the Windows Recovery Console. This was achieved in two stages - a bit lengthy but the dirty bit has been reset and in fact file access is being achieved much faster than even before the problem became aparent.

Accessing the Recovery Console, I first re-ran a disk repair (chkdsk /r) at the first screen. Then I rebooted again from the XP Pro Disk (in my case I have a disk) and selected the install Windows XP option. This caused a search for for what is already installed and offered me the option of reinstalling or repairing. I chose 'Repair".

The whole process took a great deal of time, with a series of reboots and then online updates.  But, as I have said, everything is now working fine. I am presently reformatting the drive which had the mirror image with the problem.
0
 
nobusCommented:
if no more help is needed, don't forget to close your question !
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now