Guest Donald Eagle Posted July 21, 2007 Posted July 21, 2007 Is there any way to terminate chkdsk after a dirty bit starts it during boot-up? I do know there is about an 8 second window to exit before it starts, but once it starts, is there anything that can be done? It has run about 4 times on my D: disk, but has never found anything, and it takes 3 hours to run. I am running XP Home, SP2 with all security updates. -- Don Eagle To reply personally, drop the Latin "not more"
Guest Byte Posted July 21, 2007 Posted July 21, 2007 RE: dirty bit chkdsk First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". 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 now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive. Good luck! TC -- XP - WNP Today is the first day of the rest of your life. "Donald Eagle" wrote: > Is there any way to terminate chkdsk after a dirty bit starts it during > boot-up? I do know there is about an 8 second window to exit before it > starts, but once it starts, is there anything that can be done? It has run > about 4 times on my D: disk, but has never found anything, and it takes 3 > hours to run. I am running XP Home, SP2 with all security updates. > -- > Don Eagle > To reply personally, drop the Latin "not more" > > >
Guest Donald Eagle Posted July 21, 2007 Posted July 21, 2007 Re: dirty bit chkdsk Thank you, TC, but I did not make myself clear. It does not run chkdsk every time; it has happened 4 times in the last couple of months without ever finding any problems. The bit has been reset to "not dirty". I did run "fsutil dirty query D:" to verify that. I am trying to avoid having to check the dirty bit every day before I log off. I will make a note of the "CHKNTFS /X D:" and "Chkdsk /f /r d:" commands for future use. If I (or my wife) turn on the computer and leave the room while it boots, I want to be able to escape chkdsk if it starts and run it later at my leisure. -- Don Eagle To reply personally, drop the Latin "not more" "Byte" <Byte@discussions.microsoft.com> wrote in message news:BE2619E0-E6A3-44CE-82A4-82F0C15312E6@microsoft.com... > First click Start> Run> bring up a command prompt by typing in "CMD" and > type > " fsutil dirty query d: ". This queries the drive, and more than likely it > will tell you that it is dirty. Next, type "CHKNTFS /X D:". 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 now you > want > to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you > through 5 stages of the scan and will unset that dirty bit. Finally, type > "fsutil dirty query d:" and Windows will confirm that the dirty bit is not > set on that drive. Good luck! > > TC > > -- > XP - WNP > Today is the first day of the > rest of your life. > > > > "Donald Eagle" wrote: > >> Is there any way to terminate chkdsk after a dirty bit starts it during >> boot-up? I do know there is about an 8 second window to exit before it >> starts, but once it starts, is there anything that can be done? It has >> run >> about 4 times on my D: disk, but has never found anything, and it takes 3 >> hours to run. I am running XP Home, SP2 with all security updates. >> -- >> Don Eagle >> To reply personally, drop the Latin "not more" >> >> >>
Recommended Posts