chkdsk /f doesn't bring up the console after boot? (Problems running autochk).

[Bill in Co.]

Anybody else run into this problem? Normally, if you run chkdsk /f, and
reboot, it runs it in that smaller blue console window, and then after
completion finally boots up into Windows. Not doing that here anymore,
for some reason.

My disk Volume is "clean" (dirty bit is off). And the normal runs of
chkdsk are pretty good (I get the "correcting errors in the volume bitmap"
stuff, but nothing really outrageous here)

So now what I notice (after having run chkdsk /f once) is that takes a
noticably longer amount of time to finish booting up into Windows. And
then if I reboot, it does the same thing again - takes a longer amount of
time (than normal) to finish booting up (I can hear disk activity in the
background, so evidently Task Manager is still trying!).
So evidently it (chkdsk /f) is not ever running to completion.

I am able to "fix" this problem by restoring the previous ERUNT backup made
prior to running chkdsk /f. And of course, this whole scenario is
repeatable.

So far I haven't found any articles covering THIS specific problem (although
there are several articles on problems with chkdsk, however)

So apparently, "autochk.exe" is not able to succesfully run in the console
mode after rebooting, but still even tries to as Windows boots up (since
there is noticeable disk activity and it takes so long! Weird.

 

[Andrew E.]

"Normal runs of CHKDSK are pretty good",like if youre running it other than
the "Blue Screen" page before xp boots....CHKDSK /F only runs before XP
starts,whats task mgr got to do with it.....Try booting to xp
cd,recovery,select
1 For C: Press enter for password,type:CHKDSK C: /R Once thru,type:EXIT
Let xp start,remove cd.Also,the correct syntax is:CHKDSK C: /F

 

[Bill in Co.]

Well, I did manage to run chkdsk /f under one of the NTFSDOS goodies, but
that doesn't really answer why I'm having this problem.

As to what does Task Manager have to do with it? Well, when you invoke
chkdsk /f (or chkdsk c:/f - doesn't matter here), it sets up the task
before rebooting, so that when rebooting control is somehow passed over to
"autochk.exe" to execute it before finally booting back up into Windows (and
you see that bluish DOS like screen).

Well, that's the way it's supposed to work, but it doesn't, at least not
anymore.

 

[Gerry]

Bill

Lengthy post by Wes Vogel offers ideas for you to look at:
http://snipurl.com/2angd [groups_google_com]


--



Hope this helps.

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

 

[Bill in Co.]

Thanks Gerry,
I just took a look at that, and there's a bit in there to digest. I'm not
running those other programs, but maybe trying something like the /x switch
might work, who knows. I'll have to reread it again and see. So thanks
again - it's a start, anyways.

Bill

Lengthy post by Wes Vogel offers ideas for you to look at:
http://snipurl.com/2angd [groups_google_com]


--



Hope this helps.

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

Anybody else run into this problem? Normally, if you run chkdsk
/f, and reboot, it runs it in that smaller blue console window, and
then after completion finally boots up into Windows. Not doing
that here anymore, for some reason.

My disk Volume is "clean" (dirty bit is off). And the normal runs
of chkdsk are pretty good (I get the "correcting errors in the volume
bitmap" stuff, but nothing really outrageous here)

So now what I notice (after having run chkdsk /f once) is that takes a
noticably longer amount of time to finish booting up into Windows.
And then if I reboot, it does the same thing again - takes a longer
amount of time (than normal) to finish booting up (I can hear disk
activity in the background, so evidently Task Manager is still
trying!). So evidently it (chkdsk /f) is not ever running to
completion.

I am able to "fix" this problem by restoring the previous ERUNT
backup made prior to running chkdsk /f. And of course, this whole
scenario is repeatable.

So far I haven't found any articles covering THIS specific problem
(although there are several articles on problems with chkdsk, however)

So apparently, "autochk.exe" is not able to succesfully run in the
console mode after rebooting, but still even tries to as Windows
boots up (since there is noticeable disk activity and it takes so
long! Weird.

 

[Bill in Co.]

Update - went through it all and got a similar result, in that "chkdsk /f"
works properly in Safe Mode, but not otherwise (just as in his case,
although our cases are not exactly identical)

Oh well, I can live with this. I was (am) just a bit curious as to what
happened over time such that "chkdsk /f" doesn't run properly, but I notice
the OP never really pinned it down to one specific thing, either.

Oh, and I learned another thing the hard way; once you invoke Safe Mode or
that Selective Boot (in msconfig), and then go back to Normal Mode, you may
lose all your prior System Restore Points. Oh well...

Thanks Gerry,
I just took a look at that, and there's a bit in there to digest. I'm
not
running those other programs, but maybe trying something like the /x
switch
might work, who knows. I'll have to reread it again and see. So
thanks
again - it's a start, anyways.

Bill

Lengthy post by Wes Vogel offers ideas for you to look at:
http://snipurl.com/2angd [groups_google_com]


--



Hope this helps.

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

Anybody else run into this problem? Normally, if you run chkdsk
/f, and reboot, it runs it in that smaller blue console window, and
then after completion finally boots up into Windows. Not doing
that here anymore, for some reason.

My disk Volume is "clean" (dirty bit is off). And the normal runs
of chkdsk are pretty good (I get the "correcting errors in the volume
bitmap" stuff, but nothing really outrageous here)

So now what I notice (after having run chkdsk /f once) is that takes a
noticably longer amount of time to finish booting up into Windows.
And then if I reboot, it does the same thing again - takes a longer
amount of time (than normal) to finish booting up (I can hear disk
activity in the background, so evidently Task Manager is still
trying!). So evidently it (chkdsk /f) is not ever running to
completion.

I am able to "fix" this problem by restoring the previous ERUNT
backup made prior to running chkdsk /f. And of course, this whole
scenario is repeatable.

So far I haven't found any articles covering THIS specific problem
(although there are several articles on problems with chkdsk, however)

So apparently, "autochk.exe" is not able to succesfully run in the
console mode after rebooting, but still even tries to as Windows
boots up (since there is noticeable disk activity and it takes so
long! Weird.

 

[Gerry]

Bill

You should not lose restore points!

--



Hope this helps.

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

Update - went through it all and got a similar result, in that
"chkdsk /f" works properly in Safe Mode, but not otherwise (just as
in his case, although our cases are not exactly identical)

Oh well, I can live with this. I was (am) just a bit curious as to
what happened over time such that "chkdsk /f" doesn't run properly,
but I notice the OP never really pinned it down to one specific
thing, either.
Oh, and I learned another thing the hard way; once you invoke Safe
Mode or that Selective Boot (in msconfig), and then go back to Normal
Mode, you may lose all your prior System Restore Points. Oh well...

Thanks Gerry,
I just took a look at that, and there's a bit in there to digest.
I'm not
running those other programs, but maybe trying something like the /x
switch
might work, who knows. I'll have to reread it again and see. So
thanks
again - it's a start, anyways.

Bill

Lengthy post by Wes Vogel offers ideas for you to look at:
http://snipurl.com/2angd [groups_google_com]


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Bill in Co. wrote:
Anybody else run into this problem? Normally, if you run chkdsk
/f, and reboot, it runs it in that smaller blue console window, and
then after completion finally boots up into Windows. Not doing
that here anymore, for some reason.

My disk Volume is "clean" (dirty bit is off). And the normal
runs of chkdsk are pretty good (I get the "correcting errors in
the volume bitmap" stuff, but nothing really outrageous here)

So now what I notice (after having run chkdsk /f once) is that
takes a noticably longer amount of time to finish booting up into
Windows. And then if I reboot, it does the same thing again -
takes a longer amount of time (than normal) to finish booting up
(I can hear disk activity in the background, so evidently Task
Manager is still trying!). So evidently it (chkdsk /f) is not ever
running to completion.

I am able to "fix" this problem by restoring the previous ERUNT
backup made prior to running chkdsk /f. And of course, this
whole scenario is repeatable.

So far I haven't found any articles covering THIS specific problem
(although there are several articles on problems with chkdsk,
however) So apparently, "autochk.exe" is not able to succesfully
run in the
console mode after rebooting, but still even tries to as Windows
boots up (since there is noticeable disk activity and it takes so
long! Weird.

 

[Bill in Co.]

OK, then I think I lost them when I did "Diagnostic Startup" then (and not
Safe Mode) (I tried both out). All I know is after trying both out, I
found I had lost those old restore points. But after all these tests, I
just went back to my imaged backup, so no harm done.

Still, I don't know what the difference is between the so called,
"Diagnostic Startup" option (in msconfig), and "Safe Mode", as I think they
are somewhat similar. Do you happen to know, off hand? Maybe I can look
it up later.

Maybe "Diagnostic Startup" is even more restricted (limited) than the
"regular" Safe Mode, and that's why it happened.

What I *do* know is that "chkdsk /f" ran fine in Safe Mode, but did NOT run
under "Diagnostic Startup" over here.

Bill

You should not lose restore points!

--



Hope this helps.

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

Update - went through it all and got a similar result, in that
"chkdsk /f" works properly in Safe Mode, but not otherwise (just as
in his case, although our cases are not exactly identical)

Oh well, I can live with this. I was (am) just a bit curious as to
what happened over time such that "chkdsk /f" doesn't run properly,
but I notice the OP never really pinned it down to one specific
thing, either.
Oh, and I learned another thing the hard way; once you invoke Safe
Mode or that Selective Boot (in msconfig), and then go back to Normal
Mode, you may lose all your prior System Restore Points. Oh well...

Thanks Gerry,
I just took a look at that, and there's a bit in there to digest.
I'm not
running those other programs, but maybe trying something like the /x
switch
might work, who knows. I'll have to reread it again and see. So
thanks
again - it's a start, anyways.

Gerry wrote:
Bill

Lengthy post by Wes Vogel offers ideas for you to look at:
http://snipurl.com/2angd [groups_google_com]


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Bill in Co. wrote:
Anybody else run into this problem? Normally, if you run chkdsk
/f, and reboot, it runs it in that smaller blue console window, and
then after completion finally boots up into Windows. Not doing
that here anymore, for some reason.

My disk Volume is "clean" (dirty bit is off). And the normal
runs of chkdsk are pretty good (I get the "correcting errors in
the volume bitmap" stuff, but nothing really outrageous here)

So now what I notice (after having run chkdsk /f once) is that
takes a noticably longer amount of time to finish booting up into
Windows. And then if I reboot, it does the same thing again -
takes a longer amount of time (than normal) to finish booting up
(I can hear disk activity in the background, so evidently Task
Manager is still trying!). So evidently it (chkdsk /f) is not ever
running to completion.

I am able to "fix" this problem by restoring the previous ERUNT
backup made prior to running chkdsk /f. And of course, this
whole scenario is repeatable.

So far I haven't found any articles covering THIS specific problem
(although there are several articles on problems with chkdsk,
however) So apparently, "autochk.exe" is not able to succesfully
run in the
console mode after rebooting, but still even tries to as Windows
boots up (since there is noticeable disk activity and it takes so
long! Weird.