Chkdsk automatically turns on on startup XP?

[Majki Majk]

Hi, chkdsk is automsatically starting up every time computer boots XP.
It checks my middle partition, i have three of them, and only this one
is checking. The disk consistency is always ok. Why is then this check
turning on and how to switch it off ?

Tnks

 

[Gerry]

Majki

Check the patition using HD Tune.

Try HD Tune only gives information and does not fix any
problems.

Download and run it and see what it turns up. You want HD Tune
(freeware) version 2.55 not HD Tune Pro (not Freeware) version 3.00.
http://www.hdtune.com/

Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

Select the Health tab and then double click the two page icon ( copy to
Clipboard ) and copy into a further message. Make sure you do a full
surface scan with HD Tune.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Twayne]

Hi, chkdsk is automsatically starting up every time computer boots XP.

It checks my middle partition, i have three of them, and only this
one is checking. The disk consistency is always ok. Why is then this
check turning on and how to switch it off ?

Tnks

I seem tohave lost the source URL for where I got this, but I found the
following in my files from when I had a dirty-bit problem to contend
with: Looks like it might help you.

There are other methods too but they require editing the registry which
should be more of a last ditch effort IMO. Read though the below
article once and then try it out. It's a safe procedure.

Regards,

Twayne


What you're experiencing is what Windows refers to as "setting the dirty
bit" and what you have to do is unset that bit. 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. It is
usually caused by a hard shut down or a power loss during a read-right
operation on that particular drive.

How do I fix it, you ask?

Well, that's easy. First click Start | Run | and bring up a command
prompt by typing in
CMD

and then type

fsutil dirty query d:

To see the other commands for fsutil type fsutil plus /? or just type
fsutil alone. Here is what you will see:

fsutil
---- Commands Supported ----

behavior Control file system behavior
dirty Manage volume dirty bit
file File specific commands
fsinfo File system information
hardlink Hardlink management
objectid Object ID management
quota Quota management
reparsepoint Reparse point management
sparse Sparse file control
usn USN management
volume Volume management

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 type 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. It
will give you this message:

Volume - d: is NOT Dirty

Good luck!

 

[Majki Majk]

I seem tohave lost the source URL for where I got this, but I found the
following in my files from when I had a dirty-bit problem to contend
with: Looks like it might help you.

There are other methods too but they require editing the registry which
should be more of a last ditch effort IMO. Read though the below
article once and then try it out. It's a safe procedure.

Regards,

Twayne


What you're experiencing is what Windows refers to as "setting the dirty
bit" and what you have to do is unset that bit. 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. It is
usually caused by a hard shut down or a power loss during a read-right
operation on that particular drive.

How do I fix it, you ask?

Well, that's easy. First click Start | Run | and bring up a command
prompt by typing in
CMD

and then type

fsutil dirty query d:

To see the other commands for fsutil type fsutil plus /? or just type
fsutil alone. Here is what you will see:

fsutil
---- Commands Supported ----

behavior Control file system behavior
dirty Manage volume dirty bit
file File specific commands
fsinfo File system information
hardlink Hardlink management
objectid Object ID management
quota Quota management
reparsepoint Reparse point management
sparse Sparse file control
usn USN management
volume Volume management

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 type 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. It
will give you this message:

Volume - d: is NOT Dirty

Good luck!

Solved via fsutil .

I checked HDTUNE also, found clean disk.

Thanks for the manual =)