Chkdsk

[Bob Day]

Using Windows XP all with latest updates...I am experiencing no problems
with my hard disk.

When I run Windows XP check disk and defrag, it runs fine. I have also run
Norton's version of check disk and defrag, and they run fine also. I set
both or automatically repair any errors found.

However, I use Diskeeper, which handles defrag in background while windows
is running. When I run Diskeeper "Boot Time Deframentation", which runs a
check disk and then defrags those files that cannot be defraged while
windows is running, I immediatly get the following error message (i.e. the
error is so fast, that nothing has actually had time to run):

Boot time deframengation cannot run on a dirty volume. Please run Chkdsk
/F.
Failed to initialize Volume c: - Volume probably not mounted or is not NTFS
Exiting.

I get the same error message using Diskeeper Version 8.0 and Version 10.0.
I don't get the error on other computers running Diskeeper.

Diskeeper tech support says I need to reformat and reinstall, which I am not
willing to do. It doesn't make sense that XP and Norton products do not
find any problem.

What is a Dirty Volume, and what is the problem? Is there a way to resolve
this? Why don't the other programs (besides Diskeeper) detect any problem?

Thanks!

Bob Day.

 

[Wesley Vogel]

[[If a volume's dirty bit is set, this indicates that the file system may be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set when
the computer restarts, chkdsk runs to verify the consistency of the volume.

Every time Windows XP 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.]]

XP's defrag will not run if a volume is dirty. I do not use anything else,
so I can't say about the others.

The dirty bit can be set by you or by Windows.

This will report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

fsutil dirty query C:

Hit the Enter key.

You'll see one of these.

Volume C: is not dirty
or
Volume C: is dirty

If the dirty bit was set by you, this will reset it.

Open a command prompt...
Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs /d

Hit the Enter key.

The /d switch restores the machine to the default behavior; all drives are
checked at boot time and chkdsk is run on those that are dirty.

If the dirty bit cannot be reset by running chkdsk, there may be a problem
with the hard drive.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Bob Harris]

You will also get that "dirty volume" message, if you set CHKDSK to run,
then try to run Diskeeper before CHKDSK has had a chance to run.

I have found that running CHKDSK first, rebooting if it requires, then
immediately running Diskeeper, often works.

Or, try running CHKDSK C: /R form the XP recovery console. Then, run
Diskeeper as soon as you reboot into windows.

Links to XP recovery console:

http://www.kellys-korner-xp.com/win_xp_rec.htm



http://www.wown.com/j_helmig/wxprcons.htm



http://www.xxcopy.com/xxcopy33.htm (near bottom)



http://www.webtree.ca/windowsxp/repair_xp.htm (ISO, about number 26 in list)

 

[Bob Day]

Thanks for your help

fsutil dirty query C:

reports it is dirty. However, contrary to your information below, Windows
XP boots fine, does not automatically run Chkdsk because it is dirty, etc.
Addtionally, after successfully manually running chkdsk from windows on
reboot, above still shows it is dirty.

Any other thoughts?

Bob Day

[[If a volume's dirty bit is set, this indicates that the file system may
be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the
volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set
when
the computer restarts, chkdsk runs to verify the consistency of the
volume.

Every time Windows XP 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.]]

XP's defrag will not run if a volume is dirty. I do not use anything
else,
so I can't say about the others.

The dirty bit can be set by you or by Windows.

This will report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

fsutil dirty query C:

Hit the Enter key.

You'll see one of these.

Volume C: is not dirty
or
Volume C: is dirty

If the dirty bit was set by you, this will reset it.

Open a command prompt...
Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs /d

Hit the Enter key.

The /d switch restores the machine to the default behavior; all drives are
checked at boot time and chkdsk is run on those that are dirty.

If the dirty bit cannot be reset by running chkdsk, there may be a problem
with the hard drive.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Using Windows XP all with latest updates...I am experiencing no problems
with my hard disk.

When I run Windows XP check disk and defrag, it runs fine. I have also
run Norton's version of check disk and defrag, and they run fine also. I
set both or automatically repair any errors found.

However, I use Diskeeper, which handles defrag in background while
windows
is running. When I run Diskeeper "Boot Time Deframentation", which runs
a
check disk and then defrags those files that cannot be defraged while
windows is running, I immediatly get the following error message (i.e.
the
error is so fast, that nothing has actually had time to run):

Boot time deframengation cannot run on a dirty volume. Please run Chkdsk
/F.
Failed to initialize Volume c: - Volume probably not mounted or is not
NTFS Exiting.

I get the same error message using Diskeeper Version 8.0 and Version
10.0.
I don't get the error on other computers running Diskeeper.

Diskeeper tech support says I need to reformat and reinstall, which I am
not willing to do. It doesn't make sense that XP and Norton products do
not find any problem.

What is a Dirty Volume, and what is the problem? Is there a way to
resolve this? Why don't the other programs (besides Diskeeper) detect
any problem?

Thanks!

Bob Day.

 

[Wesley Vogel]

Bob,

If the dirty bit cannot be reset by running chkdsk, there may be a problem
with the hard drive.

Autochk runs if the volume is flagged as dirty.

You do not always see it when Autochk runs at every boot. The only way I
know for sure is to try to recover the deleted bootex.log using something
like Restoration.

Try this...
Go here:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Read the instructions at the top of the page.
Scroll down to:
82. Disable or Enable Check Disk Upon Boot
Click on Disable.

You might want to read this.

Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
computer
http://support.microsoft.com/kb/831426

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for your help

fsutil dirty query C:

reports it is dirty. However, contrary to your information below, Windows
XP boots fine, does not automatically run Chkdsk because it is dirty, etc.
Addtionally, after successfully manually running chkdsk from windows on
reboot, above still shows it is dirty.

Any other thoughts?

Bob Day

[[If a volume's dirty bit is set, this indicates that the file system may
be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the
volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set
when
the computer restarts, chkdsk runs to verify the consistency of the
volume.

Every time Windows XP 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.]]

XP's defrag will not run if a volume is dirty. I do not use anything
else,
so I can't say about the others.

The dirty bit can be set by you or by Windows.

This will report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

fsutil dirty query C:

Hit the Enter key.

You'll see one of these.

Volume C: is not dirty
or
Volume C: is dirty

If the dirty bit was set by you, this will reset it.

Open a command prompt...
Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs /d

Hit the Enter key.

The /d switch restores the machine to the default behavior; all drives
are checked at boot time and chkdsk is run on those that are dirty.

If the dirty bit cannot be reset by running chkdsk, there may be a
problem with the hard drive.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Using Windows XP all with latest updates...I am experiencing no problems
with my hard disk.

When I run Windows XP check disk and defrag, it runs fine. I have also
run Norton's version of check disk and defrag, and they run fine also.
I set both or automatically repair any errors found.

However, I use Diskeeper, which handles defrag in background while
windows
is running. When I run Diskeeper "Boot Time Deframentation", which runs
a
check disk and then defrags those files that cannot be defraged while
windows is running, I immediatly get the following error message (i.e.
the
error is so fast, that nothing has actually had time to run):

Boot time deframengation cannot run on a dirty volume. Please run
Chkdsk /F.
Failed to initialize Volume c: - Volume probably not mounted or is not
NTFS Exiting.

I get the same error message using Diskeeper Version 8.0 and Version
10.0.
I don't get the error on other computers running Diskeeper.

Diskeeper tech support says I need to reformat and reinstall, which I am
not willing to do. It doesn't make sense that XP and Norton products do
not find any problem.

What is a Dirty Volume, and what is the problem? Is there a way to
resolve this? Why don't the other programs (besides Diskeeper) detect
any problem?

Thanks!

Bob Day.