chkdsk scheduled problem and drive marked dirty

[RONALD BURKE]

Whenever I boot, chkdsk runs on drive e: but never reports any errors.
chkntsf E: reports that E: is dirty. chkntsf /x E: has no effect. When I use
E:>Properties>Tools>Check Now with the scan for bad sectors it doesn't
report any errors. In the registry HKEY_LOCAL_MACHINE> SYSTEM>
CurrentControlSet> Control> Session Manager> BootExecute is set to autocheck
autochk *. chkdsk is not in my task scheduler to run.

The boot delay is annoying, of course, and I'd like to get rid of the chkdsk
run. More than that, I'd like to find out why the e drive is marked as
dirty.

Any help you could give will be much appreciated.

Ron

 

[Claymore]

Whenever I boot, chkdsk runs on drive e: but never reports any errors.
chkntsf E: reports that E: is dirty. chkntsf /x E: has no effect. When I use
E:>Properties>Tools>Check Now with the scan for bad sectors it doesn't
report any errors. In the registry HKEY_LOCAL_MACHINE> SYSTEM>
CurrentControlSet> Control> Session Manager> BootExecute is set to autocheck
autochk *. chkdsk is not in my task scheduler to run.

The boot delay is annoying, of course, and I'd like to get rid of the chkdsk
run. More than that, I'd like to find out why the e drive is marked as
dirty.

Any help you could give will be much appreciated.

Ron

Hello Ron,

You wrote "chkntsf /x E: "
Is this just a typo?
Should be "chkntfs /x E:"

 

[RONALD BURKE]

Thanks! It was a typo, but I made the same typo when I ran it. So I did it
right and it did exclude e: from the autocheck. But the drive was still
marked as dirty and I couldn't defrag it. I was just about to try running
chkdsk from the Recovery Console when I realized I had never run it manually
from a command prompt. I had used Start>Run to run chkdsk but that just
scheduled it for the next boot, which did nothing. So I ran chkdsk from a
command window--it ran, found no errors and--hooray!--turned off the dirty
bit. Problem solved as confirmed by fsutil. Thanks for your response and
help. (ps. I then got rid of the drive exclusion in BootExecute in the
registry.)

Whenever I boot, chkdsk runs on drive e: but never reports any errors.
chkntsf E: reports that E: is dirty. chkntsf /x E: has no effect. When I
use
E:>Properties>Tools>Check Now with the scan for bad sectors it doesn't
report any errors. In the registry HKEY_LOCAL_MACHINE> SYSTEM>
CurrentControlSet> Control> Session Manager> BootExecute is set to
autocheck
autochk *. chkdsk is not in my task scheduler to run.

The boot delay is annoying, of course, and I'd like to get rid of the
chkdsk
run. More than that, I'd like to find out why the e drive is marked as
dirty.

Any help you could give will be much appreciated.

Ron

Hello Ron,

You wrote "chkntsf /x E: "
Is this just a typo?
Should be "chkntfs /x E:"

 

[Claymore]

Thanks! It was a typo, but I made the same typo when I ran it. So I did it
right and it did exclude e: from the autocheck. But the drive was still
marked as dirty and I couldn't defrag it. I was just about to try running
chkdsk from the Recovery Console when I realized I had never run it manually
from a command prompt. I had used Start>Run to run chkdsk but that just
scheduled it for the next boot, which did nothing. So I ran chkdsk from a
command window--it ran, found no errors and--hooray!--turned off the dirty
bit. Problem solved as confirmed by fsutil. Thanks for your response and
help. (ps. I then got rid of the drive exclusion in BootExecute in the
registry.)







Hello Ron,

You wrote "chkntsf /x E: "
Is this just a typo?
Should be "chkntfs /x E:"- Hide quoted text -

- Show quoted text -

Great, Ron

You sure know your stuff!

Chris Burke (one of the clan too)