chkdsk at startup

  • Thread starter Thread starter Laurence
  • Start date Start date
L

Laurence

Every time I boot up the system scans one drive. It never finds anything but
by the time windows has loaded it is set ready to scan next time. It is not
in the scheduled tasks. Is there anything else I can try.

Laurie
 
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000
http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Thanks for your advice.

Following your instructions I am being told that the G drive is dirty but on
completion of the scan no errors are reported.

Looking at the BootExecute I find the following

smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
autocheck autochk *

The second part seems in line with what you suggest the first line seems to
relate to System Mechanic that I have on my machine, could this be causing
the problem?

--
Laurence


(e-mail address removed)
Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000
http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Every time I boot up the system scans one drive. It never finds anything
but by the time windows has loaded it is set ready to scan next time. It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
Hi Laurence,

iolo is iolo technologies the makers of System Mechanic.

I have no idea what this entry
smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
is doing in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
BootExecute

I would ask the iola people.
http://www.iolo.com/customercare/

I do not use or know anything about System Mechanic.

However, that entry is probably not allowing autochk exclusive use of the
drive or volume.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager contains
a list of commands to run before loading services. The Autochk.exe tool is
specified by the value of the BootExecute entry and virtual memory (paging
file) settings stored in the Memory Management subkey. Autochk, which is a
version of the Chkdsk tool, runs at startup if the operating system detects
a file system problem that requires repair before completing the startup
process.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Thanks for your advice.

Following your instructions I am being told that the G drive is dirty but
on completion of the scan no errors are reported.

Looking at the BootExecute I find the following

smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
autocheck autochk *

The second part seems in line with what you suggest the first line seems
to relate to System Mechanic that I have on my machine, could this be
causing the problem?

--
Laurence


(e-mail address removed)
Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows
2000 http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Every time I boot up the system scans one drive. It never finds anything
but by the time windows has loaded it is set ready to scan next time. It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
Laurence

A lot of contributors to these Microsoft Windows newsgroups
have a poor opinion of System Mechanic and would
recommend not using it.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Laurence said:
Thanks for your advice.

Following your instructions I am being told that the G drive is dirty
but on completion of the scan no errors are reported.

Looking at the BootExecute I find the following

smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
autocheck autochk *

The second part seems in line with what you suggest the first line
seems to relate to System Mechanic that I have on my machine, could
this be causing the problem?

--
Laurence


(e-mail address removed)
Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows
2000
http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Every time I boot up the system scans one drive. It never finds
anything
but by the time windows has loaded it is set ready to scan next
time. It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
Thanks

I have tried removing this line and resetting but made no difference.

I tried the tweak from kellys corner but this did not stop the problem.

Is there anything else I could try. eg would reformatting this logical drive
make any difference? Should I consider a total reformat of my hard drive?

--
--
Laurence



Wesley Vogel said:
Hi Laurence,

iolo is iolo technologies the makers of System Mechanic.

I have no idea what this entry
smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
is doing in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
BootExecute

I would ask the iola people.
http://www.iolo.com/customercare/

I do not use or know anything about System Mechanic.

However, that entry is probably not allowing autochk exclusive use of the
drive or volume.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
contains
a list of commands to run before loading services. The Autochk.exe tool is
specified by the value of the BootExecute entry and virtual memory (paging
file) settings stored in the Memory Management subkey. Autochk, which is a
version of the Chkdsk tool, runs at startup if the operating system
detects
a file system problem that requires repair before completing the startup
process.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Thanks for your advice.

Following your instructions I am being told that the G drive is dirty but
on completion of the scan no errors are reported.

Looking at the BootExecute I find the following

smrgdf C:\Documents and Settings\Laurence\Application Data\iolo\
autocheck autochk *

The second part seems in line with what you suggest the first line seems
to relate to System Mechanic that I have on my machine, could this be
causing the problem?

--
Laurence


Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows
2000 http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Laurence <[email protected]> hunted and pecked:
Every time I boot up the system scans one drive. It never finds
anything
but by the time windows has loaded it is set ready to scan next time.
It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
I have again tried to resolve.

By using the /k:Volume G trigger in boot execute I have stopped it running
the chkdsk. Unfortunately the machine is still setting chkdsk /f to run on
next reboot (If I try to run defrag in XP this will not run because of the
setting for the next boot up).

The problem still seems to be a dirty volume G. Is there any way of tracking
down why it thinks the volume is dirty?

Laurence
(e-mail address removed)

Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows 2000
http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Every time I boot up the system scans one drive. It never finds anything
but by the time windows has loaded it is set ready to scan next time. It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
If a volume's dirty bit is set, the only way to get rid of it is to run
chkdsk.

[[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.]]

Try running chkdsk from the Recovery Console to see if you can clear the
dirty bit on G:

Recovery Console: A command-line interface that provides a limited set of
administrative commands that are useful for repairing a computer.

Chkdsk from the Recovery Console is differnet than the regular chkdsk.

Recovery Console chkdsk help...
Paste the following line into Start | Run and click OK...

hh bootcons.chm::/bootcons_chkdsk.htm

Recovery Console
CHKDSK
chkdsk drive /p /r
The chkdsk command checks the specified drive and repairs or recovers the
drive if the drive requires it. The command also marks any bad sectors and
it recovers readable information.

You can use the following options:
/p : Does an exhaustive check of the drive and corrects any errors.
/r : Locates bad sectors and recovers readable information.

Note If you specify the /r option, the /p option is implied. When you
specify the chkdsk command without arguments, the command checks the current
drive with no options in effect.

When you run the chkdsk command, you are required to use the Autochk.exe
file. CHKDSK automatically locates this file in the startup folder. If the
Command Console was preinstalled, the startup folder is typically the
Cmdcons folder. If CHKDSK cannot find Autochk.exe in the startup folder,
CHKDSK tries to locate the Windows CD-ROM installation media. If it cannot
find the installation media, CHKDSK prompts you for the location of the
Autochk.exe file.
from...
Description of the Windows XP Recovery Console
http://support.microsoft.com/kb/314058


From: Maurice N ~ MVP Sat, Jul 30 2005
<quote>
Run CHKDSK from within Recovery Console. *Presuming you have a full
retail CD version of Windows XP* or a slipstream CD of XP.
( If you don't have the XP CD, or have an OEM version of XP, it may be
possible to run Recovery Console by booting up from XP setup diskettes.)

#1. Run CHKDSK in XP Recovery Console:
Set pc BIOS to boot from CDROM. Place XP CD in drive. Reboot from the CD.
Select the first option R Repair/Recovery Console.
Select your Windows partition by number. Usually it is 1.
Login to XP with administrator password (if your setup had a password;
otherwise press Enter).

Then run CHKDSK /P from the command line. (In Recovery Console /P
replaces /F ).

Run it once (or repeat) until it shows no errors. This should clear the
"dirty" flag on the disk drive X. Run CHKDSK for each drive on your system.
CHKDSK /P :X where X is letter for disk drive

References for Recovery Console:
Description of the Windows XP Recovery Console
http://support.microsoft.com/default.aspx?kbid=314058

HOW TO: Install and Use the Recovery Console for Windows XP
http://support.microsoft.com/default.aspx?kbid=307654

To exit the R Console, use the EXIT command.
<quote>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
I have again tried to resolve.

By using the /k:Volume G trigger in boot execute I have stopped it running
the chkdsk. Unfortunately the machine is still setting chkdsk /f to run on
next reboot (If I try to run defrag in XP this will not run because of the
setting for the next boot up).

The problem still seems to be a dirty volume G. Is there any way of
tracking down why it thinks the volume is dirty?

Laurence
(e-mail address removed)

Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows
2000 http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
Every time I boot up the system scans one drive. It never finds anything
but by the time windows has loaded it is set ready to scan next time. It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
I will try to run recovery console but this is more difficult as my original
version of XP has been updated to SP2 and according to the MS Knowledge base
I will need to carry out Integration et al. I will try this later I think as
it seems rather complex.

Thanks for your help.

Laurence

Wesley Vogel said:
If a volume's dirty bit is set, the only way to get rid of it is to run
chkdsk.

[[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.]]

Try running chkdsk from the Recovery Console to see if you can clear the
dirty bit on G:

Recovery Console: A command-line interface that provides a limited set of
administrative commands that are useful for repairing a computer.

Chkdsk from the Recovery Console is differnet than the regular chkdsk.

Recovery Console chkdsk help...
Paste the following line into Start | Run and click OK...

hh bootcons.chm::/bootcons_chkdsk.htm

Recovery Console
CHKDSK
chkdsk drive /p /r
The chkdsk command checks the specified drive and repairs or recovers the
drive if the drive requires it. The command also marks any bad sectors and
it recovers readable information.

You can use the following options:
/p : Does an exhaustive check of the drive and corrects any errors.
/r : Locates bad sectors and recovers readable information.

Note If you specify the /r option, the /p option is implied. When you
specify the chkdsk command without arguments, the command checks the
current
drive with no options in effect.

When you run the chkdsk command, you are required to use the Autochk.exe
file. CHKDSK automatically locates this file in the startup folder. If the
Command Console was preinstalled, the startup folder is typically the
Cmdcons folder. If CHKDSK cannot find Autochk.exe in the startup folder,
CHKDSK tries to locate the Windows CD-ROM installation media. If it cannot
find the installation media, CHKDSK prompts you for the location of the
Autochk.exe file.
from...
Description of the Windows XP Recovery Console
http://support.microsoft.com/kb/314058


From: Maurice N ~ MVP Sat, Jul 30 2005
<quote>
Run CHKDSK from within Recovery Console. *Presuming you have a full
retail CD version of Windows XP* or a slipstream CD of XP.
( If you don't have the XP CD, or have an OEM version of XP, it may be
possible to run Recovery Console by booting up from XP setup diskettes.)

#1. Run CHKDSK in XP Recovery Console:
Set pc BIOS to boot from CDROM. Place XP CD in drive. Reboot from the
CD.
Select the first option R Repair/Recovery Console.
Select your Windows partition by number. Usually it is 1.
Login to XP with administrator password (if your setup had a password;
otherwise press Enter).

Then run CHKDSK /P from the command line. (In Recovery Console /P
replaces /F ).

Run it once (or repeat) until it shows no errors. This should clear the
"dirty" flag on the disk drive X. Run CHKDSK for each drive on your
system.
CHKDSK /P :X where X is letter for disk drive

References for Recovery Console:
Description of the Windows XP Recovery Console
http://support.microsoft.com/default.aspx?kbid=314058

HOW TO: Install and Use the Recovery Console for Windows XP
http://support.microsoft.com/default.aspx?kbid=307654

To exit the R Console, use the EXIT command.
<quote>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Laurence said:
I have again tried to resolve.

By using the /k:Volume G trigger in boot execute I have stopped it
running
the chkdsk. Unfortunately the machine is still setting chkdsk /f to run
on
next reboot (If I try to run defrag in XP this will not run because of
the
setting for the next boot up).

The problem still seems to be a dirty volume G. Is there any way of
tracking down why it thinks the volume is dirty?

Laurence
(e-mail address removed)

Wesley Vogel said:
Check Disk runs on every boot.

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

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disk at boot time.

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.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

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.

Volume C: is not dirty
Volume C: is dirty

[[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.]]
-----

This will also report whether the dirty bit is set.

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

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

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.
-----

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

A scheduled chkdsk shows up here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
Data Type: REG_MULTI_SZ
Value Data: autocheck autochk /r \??\C:

The Value Data may be any one of these:
/P \??\Volume:
/p \??\VOLUME{GUID}
/k:Volume *
/m \??\Volume:

Description of Enhanced Chkdsk, Autochk, and Chkntfs Tools in Windows
2000 http://support.microsoft.com/kb/218461

autocheck autochk * is the default value.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Laurence <[email protected]> hunted and pecked:
Every time I boot up the system scans one drive. It never finds
anything
but by the time windows has loaded it is set ready to scan next time.
It
is not in the scheduled tasks. Is there anything else I can try.

Laurie
 
I doesn't seem to be but I have stopped the initial problem per Wesley's
advice but has not cured the fault as yet.

Thanks

Laurence
 
Laurence said:
Every time I boot up the system scans one drive. It never finds anything but
by the time windows has loaded it is set ready to scan next time. It is not
in the scheduled tasks. Is there anything else I can try.

Laurie

I had this same problem and it took me forever to fix it. The fix turned out
to be simple, but I never saw it suggested anywhere; it was the result of an
intuitive guess based on years of building PCs (and some desperation). I
tried everything mentioned in this thread so far and none of it worked.

All I had to do was SWAP THE TWO DRIVES on my IDE cable. I have an Abit
motherboard with an AMD X2 3800+. The IDE cable that came with the
motherboard has the far end labeled "master" and the near end labeled
"slave." I ignored this when installing my drives, figuring that all that
mattered was how I jumpered them. (That's been my experience in the past.) So
my boot drive was jumpered as the master and my CD drive was jumpered as
slave, but I had the boot drive hooked up to the near end (i.e., the end
nearest the motherboard) and the CD drive hooked up to the far end.

When I swapped them, my scandisk problem went away. So: check to be sure the
drive jumpered as master is on the far end of the IDE cable, and the drive
jumpered as slave is on the near end of the cable. If you have only one
drive, make sure it's on the far end.

I have no explanation for why this worked, but I know that for floppy
drives, the A: drive is always the one hooked to the far end of the cable, so
apparently in some drive subsystems, location of the drive on the ribbon
cable can make a big difference.
 
Back
Top