This morning, my Win2kPro system froze up, requiring a Reset to get
things going again.

Now, when I try to run Executive Software's defragmenter, it reports
that a CHKDSK run was scheduled for C: upon the next boot, and refused
to defragment.

The trouble is, rebooting does NOT cause CHKDSK to run.

I would like to somehow cancel the pending CHKDSK and then run it
manually from a boot-time cmd window. How do I do this?

TIA

Jason

Well, you really do want to run CHKDSK before defragmenting. I would
recommend booting to the Recovery Console, and running CHKDSK from there.
--
Greg Stigers, MCSA
this space for rent

J Warren wrote:

> This morning, my Win2kPro system froze up, requiring a Reset to get
> things going again.
>
> Now, when I try to run Executive Software's defragmenter, it reports
> that a CHKDSK run was scheduled for C: upon the next boot, and refused
> to defragment.
>
> The trouble is, rebooting does NOT cause CHKDSK to run.
>
> I would like to somehow cancel the pending CHKDSK and then run it
> manually from a boot-time cmd window. How do I do this?
Hi

Run "chkdsk C: /f", and then reboot, and see if it helps...


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/com...r/default.mspx

In article <(E-Mail Removed)>, "Torgeir Bakken
\(MVP\)" <Torgeir.Bakken-(E-Mail Removed)> says...
> J Warren wrote:
>
> > This morning, my Win2kPro system froze up, requiring a Reset to get
> > things going again.
- snip -
>
> Run "chkdsk C: /f", and then reboot, and see if it helps...
>
I tried that. chkdsk does not run. chkntfs still reports that c: is
dirty.

Jason

In article <(E-Mail Removed)>,
gregstigers+(E-Mail Removed) says...
> Well, you really do want to run CHKDSK before defragmenting. I would
> recommend booting to the Recovery Console, and running CHKDSK from there.
>
I did that, with the /r repair option. It ran for quite a long time and
then seemed to terminate normally without reporting anything the matter.
The system boots fine, but I tried another boot-time chkdsk and it
failed. chkntfs still reports that c: is dirty and chkdsk at boot claims
that it cannot open the volume for direct access.

Is there anything else I can try?

Jason

chkntfs /x volume should allow you to "turn off" the default boot time
check.

I assume that you have been able to run chkdsk before, and the inability to
do so is a new development. Make sure that chkdsk from the Recovery Console
does not report errors. If it does report errors, do try rerunning that
chkdsk. But, repeated problems like this are indicative of hardware failure.
Your harddrive vendor likely provides a diagnostic that you can download and
run, to see if the drive itself is failing. Other culprits can include the
cable and the drive controller. Incorrect changes to the BIOS settings can
cause interesting problems as well.

A good article is "Description of Enhanced Chkdsk, Autochk, and Chkntfs
Tools in Windows 2000" at
<<http://support.microsoft.com/?id=218461>>
--
Greg Stigers, MCSA
this space for rent

In article <(E-Mail Removed)>,
gregstigers+(E-Mail Removed) says...
> chkntfs /x volume should allow you to "turn off" the default boot time
> check.
>
> I assume that you have been able to run chkdsk before, and the inability to
> do so is a new development. Make sure that chkdsk from the Recovery Console
> does not report errors. If it does report errors, do try rerunning that
> chkdsk. But, repeated problems like this are indicative of hardware failure.
> Your harddrive vendor likely provides a diagnostic that you can download and
> run, to see if the drive itself is failing. Other culprits can include the
> cable and the drive controller. Incorrect changes to the BIOS settings can
> cause interesting problems as well.
>
> A good article is "Description of Enhanced Chkdsk, Autochk, and Chkntfs
> Tools in Windows 2000" at
> <<http://support.microsoft.com/?id=218461>>
>
chkdsk only began giving trouble in the past few days, following a
system hang that I had to undo with the Reset button - no clean shutdown
was possible. Running chkdsk from the Recover Console seemed to work
fine - no problems reported. I did run it a second time for good
measure... Per your suggestion, I ran the WD diags on the drive and
they, too, report nothing amiss. I know of no recent BIOS settings
changes.

I'm now considering reformatting the c: partition and restoring its
contents. I presume that will fix things unless the problem is in
damaged/conflicting Registry settings.

Hi J. Warren - See if the info here helps: How to Cancel CHKDSK After It
Has Been Scheduled
http://support.microsoft.com/default...b;en-us;158675

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In news:(E-Mail Removed),
J Warren <(E-Mail Removed)> typed:
> In article <(E-Mail Removed)>,
> gregstigers+(E-Mail Removed) says...
>> chkntfs /x volume should allow you to "turn off" the default boot time
>> check.
>>
>> I assume that you have been able to run chkdsk before, and the inability
to
>> do so is a new development. Make sure that chkdsk from the Recovery
Console
>> does not report errors. If it does report errors, do try rerunning that
>> chkdsk. But, repeated problems like this are indicative of hardware
failure.
>> Your harddrive vendor likely provides a diagnostic that you can download
and
>> run, to see if the drive itself is failing. Other culprits can include
the
>> cable and the drive controller. Incorrect changes to the BIOS settings
can
>> cause interesting problems as well.
>>
>> A good article is "Description of Enhanced Chkdsk, Autochk, and Chkntfs
>> Tools in Windows 2000" at
>> <<http://support.microsoft.com/?id=218461>>
>>
> chkdsk only began giving trouble in the past few days, following a
> system hang that I had to undo with the Reset button - no clean shutdown
> was possible. Running chkdsk from the Recover Console seemed to work
> fine - no problems reported. I did run it a second time for good
> measure... Per your suggestion, I ran the WD diags on the drive and
> they, too, report nothing amiss. I know of no recent BIOS settings
> changes.
>
> I'm now considering reformatting the c: partition and restoring its
> contents. I presume that will fix things unless the problem is in
> damaged/conflicting Registry settings.

If chkdsk and diags report no problems, I would be reluctant to reformat the
drive, especially if experiencing suspicious behavior. Does Disk Manager
show the disks as healthy? Can you run Microsoft's defrag utility, or does
it similarly complain?

The idea of the tools described at the link provided is to give the admin
complete control to either force a chkdsk, or prevent one. You can of course
check the involved registry keys, and see how they are set, and reset them
manually as desired.
--
Greg Stigers, MCSA
this space for rent

"J Warren" <(E-Mail Removed)> wrote

> > I assume that you have been able to run chkdsk before, and the inability to
> > do so is a new development.

> chkdsk only began giving trouble in the past few days, following a
> system hang that I had to undo with the Reset button - no clean shutdown
> was possible. Running chkdsk from the Recover Console seemed to work
> fine - no problems reported.

I will be watching for answers here myself. I had a program that just today
aborted loading due to an error, so my first response was to try CHKDSK
but I found, like you did, that CHKDSK did not work. I tried to get into SafeMode
but getting there took an inordinate amount of time, like the scheduled CHKDSK
was running before I could get into Safe Mode. So, I let it run but it rebooted
at the end so I don't know what it was actually doing. When I did get into
SafeMode I found that it did not let CHKDSK work there either, then I went
looking for help from the KB:

http://support.microsoft.com/default...b;en-us;160654
http://support.microsoft.com/default...b;en-us;823439


The first is a statement about XP that they know about, but no fix for yet,
the second link has a few instructions to try to stop other programs from
locking the partition at startup. I tried stopping my anti-virus and firewall
from loading up, but that did not help. I did not try a different profile....

I finally un/re-installed the software which fixed that original problem but I am
still concerned about CHKDSK not working correctly.

I did see mention of the Recovery Console in Help but I thought SafeMode
should have worked. So, I may have that route, but still, it should work
as it did before. I don't know when it stopped working, I don't use it all
that often, I do know I had no problems with SP3. When I re-formatted and
re-installed the OS in April, I was forced to take SP4.

In addition to the OS, I spent a lot of time re-installing software and I seem to
recall having a problem with Visual Studio.NET, which caused me to use
CHKDSK between attempts to be sure the disk was still good.

Today was the first time I tried to use it since then. Like you, I found it wanted to
boot into CHKDSK at startup but then could not get access to the disk. When I
did get into SafeMode (with Command Prompt) and tried CHKDSK there, it reported
that it could not do it, and asked if I wanted to schedule it for the next reboot,
I said No there, and did not see it try to boot into CHKDSK after that.

About the only other thing I can think of, (to stop some software from locking
the partition) is to empty out the (HKLM) Run key in the Registry. I guess that
will be my next move because there are 6 things there, 3 of which are from
Norton AntiVirus....

LFS