Drive marked "dirty"

[VJF]

I was showing someone how to run chkdsk and when it rebooted it wont run
it. It says it cannot get exclusive access to the drive.

I am not seeking to find out why at this point, I would just like the
command line command to remove the "dirty" bit from the drive so it does
not try to run chkdsk at every bootup and so that diskeeper will
continue to run. It wont run with the dirty bit set.


I am aware of the hp drivers, pcanywhere file, etc that cause a computer
to not run chkdsk and give access to the drive. I also know about the
reg hack to make it not scan.

None of those will help at this point.


I used to have the command saved but the boomark is not valid anymore.


Maybe is was a form of fsutil or autochk?


Any help would be greatly appreciated.

 

[Steve Nielsen]

I was showing someone how to run chkdsk and when it rebooted it wont run
it. It says it cannot get exclusive access to the drive.

I am not seeking to find out why at this point, I would just like the
command line command to remove the "dirty" bit from the drive so it does
not try to run chkdsk at every bootup and so that diskeeper will
continue to run. It wont run with the dirty bit set.


I am aware of the hp drivers, pcanywhere file, etc that cause a computer
to not run chkdsk and give access to the drive. I also know about the
reg hack to make it not scan.

None of those will help at this point.


I used to have the command saved but the boomark is not valid anymore.


Maybe is was a form of fsutil or autochk?


Any help would be greatly appreciated.

I'd boot from an XP CD and go into Recovery Console, login to the
Windows installation with the Administrator password (in XP Home this is
blank by default, in XP Pro it's whatever you set it as at install time)
and run CHKDSK /F from there.

Steve

 

[VJF]

I'd boot from an XP CD and go into Recovery Console, login to the
Windows installation with the Administrator password (in XP Home this is
blank by default, in XP Pro it's whatever you set it as at install time)
and run CHKDSK /F from there.

Steve

Thank you Steve for your help. It worked great to fix the dirty bit.


Now if I can only figure out why a new system with only office, nero and
norton av 2k4 cannot run a chkdsk b/c of the drive not being ready.


Does norton av cause this problem?

 

[Steve N.]

Thank you Steve for your help. It worked great to fix the dirty bit.

Good, glad that worked.

Now if I can only figure out why a new system with only office, nero and
norton av 2k4 cannot run a chkdsk b/c of the drive not being ready.


Does norton av cause this problem?

I've not heard of NAV causing that problem but you could try
uninstalling it and see if CHKDSK runs. This isn't the same system with
DiskKeeper is it?

Steve

 

[Alex Nichol]

I was showing someone how to run chkdsk and when it rebooted it wont run
it. It says it cannot get exclusive access to the drive.

I am not seeking to find out why at this point, I would just like the
command line command to remove the "dirty" bit from the drive so it does
not try to run chkdsk at every bootup and so that diskeeper will
continue to run. It wont run with the dirty bit set.

This one is associated with version 5.0 of Zone Alarm. Either just
uninstall that and reboot for the chkdsk to run, or get the new version
that cures the problem, released today - 5.1.011

 

[VJF]

VJF wrote:




This one is associated with version 5.0 of Zone Alarm. Either just
uninstall that and reboot for the chkdsk to run, or get the new version
that cures the problem, released today - 5.1.011

No zone alarm, no pcanywhere, no hp drivers


Only Diskeeper, office 2k3, nav 2k4 ,nero 6

 

[VJF]

Good, glad that worked.



I've not heard of NAV causing that problem but you could try
uninstalling it and see if CHKDSK runs. This isn't the same system with
DiskKeeper is it?

Steve

Same system as diskeeper. Diskeeper wont run any boot time defrag b/c
of the same reason of not being able to get exclusive acces to the drive.

Its either nero, nav 2k4 or the motherboard or video drivers that are
causing this i believe.

 

[Steve N.]

Same system as diskeeper. Diskeeper wont run any boot time defrag b/c
of the same reason of not being able to get exclusive acces to the drive.

Its either nero, nav 2k4 or the motherboard or video drivers that are
causing this i believe.

Try removing NAV. Then try rmoving DiskKeeper. I don't think mb or video
drivers would cause this.

Steve