Chkdsk will not run and Defrag will not run until Chkdsk does

D

Danny

I have a problem on Home XP with ALL Maint up to date.
When I open IE it says there is a corrupt file C;/Doc and
settings/owner/local/temp internet/contentie5/73VVLCW.
Please run Chkdsk. I tried but it gets an error saying
something else is controlling Vol and schedule for
restart. At restart it fails to (KB823439) open since
AUg2003. Then when I try to run Defrag it says a Chkdsk
is scheduled and defrag can't run. So I used KB158675 to
change the Registry from
AutoCheck Autochk /r\??\C:
Autocheck Auto Check *
to just the
Autocheck Auto Check *
This was suppose to remove the scheduled chkdsk, but
Defrag still comes up with same error.
 
G

Guest

First install xp cd,exit the info page,next go to run,type:cmd
In cmd type:Sfc /Scannow When the bar graph is thru type:EXIT
Restart computer,boot to xp cd,recovery,press enter for password,
in recovery type:CHKDSK C: /R When thru type:EXIT Back on desktop,
run disk cleanup,then go to run,type:%Temp% Go to edit,select all,delete
all,close out,empty recycle bin.Reopen cmd,in cmd type:Defrag C:
 
G

Guest

Yes I did... I can't find the path... and a scan doesnt
find it even when include Hidden files is checked.
 
G

Guest

Thanks! I don't have the recovery CD... This IBM PC has
the PF11 function which means it is all on the current
harddrive. In fact about 6 months ago I had to do a Full
Recovery or the machine cause of flaky errors. HOWEVER, I
did go to Run and typed in the Sfc /Scannow and it ran
and finished. But Chkdsk still won't run (vol under
another proc control) and Defrag thinks there is a chkdsk
pending per my earier note.... any other thoughts.
Thanks!!! Danny
 
C

cquirke (MVP Win9x)

On Fri, 16 Jul 2004 05:40:05 -0700,
Thanks! I don't have the recovery CD... This IBM PC has
the PF11 function which means it is all on the current
harddrive. In fact about 6 months ago I had to do a Full
Recovery or the machine cause of flaky errors.

Whoa: STOP right there!!

What was the *cause* of those "flaky errors"? It should NEVER be
necessary to "just re-install Windows" for no reason - and most
reasons will still be there after you "fix" it in this way. Bad RAM
is still bad , failing HD is still failing and losing sectors, etc.
did go to Run and typed in the Sfc /Scannow and it ran
and finished. But Chkdsk still won't run (vol under
another proc control) and Defrag thinks there is a chkdsk
pending per my earier note.... any other thoughts.

1) Is your HD failing?

If so, Defrag will rightly refuse to touch it (think about it - if
your HD is failing, do you *really* want to read and re-write the
contents of every file on it?). If you have any of these signs...
- S.M.A.R.T. reports HD as bad
- HD vendor's diags report HD as bad
- ChkDsk /R "fixed" bad clusters
- NTFS's code "fixed" bad clusters "on the fly"
- mouse sticks for secs while HD LED stays on (firware "fixing")
....then you need to evacuate and replace that HD. Just about every
part of the system will conspire against you to hide defects, papering
them over and pretending all is well - the HD's firmware will do this,
NTFS's code will do this, and ChkDsk /R will do this.

2) Is there invalid AppLog (Win9x) or PreFetch (XP) info?

This info helps Defrag position parts of files optimally to speed up
program loading. But if this info is corrupted or stale (i.e. refers
to files that no longer exist) you can see Defrag refusing because of
"errors" that Scandisk will never see. This was quite common in Win9x
and the same mechanism may apply to XP.

Be very, very careful with (1).



--------------- ----- ---- --- -- - - -
Tech Support: The guys who follow the
'Parade of New Products' with a shovel.
 
G

Guest

Thanks... No I do not have any indications that the
harddrive is bad. No Errorlogs/msgs/etc. Nothing as you
mention. Everything now is running EXCEPT Defrag (waiting
on Chkdsk) and Chkdsk itself not running. So am still
stuck???????
 
C

cquirke (MVP Win9x)

On Sat, 17 Jul 2004 15:22:00 -0700,
Thanks... No I do not have any indications that the
harddrive is bad. No Errorlogs/msgs/etc.

That's what I mean - several systems will hide these things from you.

The hard drive's own firmware will (or attempt to) copy the contents
of a failing sector to another "spare" sector, then updating the
internal addressing so that the OS can't tell the difference. This
won't show up in any logs, nor will you see bad blocks in any sort of
surface scan. The only clues you have are mouse-sticking pauses with
HD LED on or cluster count latency on DOS mode surface scan.

NTFS's driver code pulls the same stunt at the OS level - if NTFS's
code has difficulty reading a sector, it copies (or attempts to copy)
the contents of that cluster to another one, then alter file system
addressing to use the new one. This should be logged somewhere (but
may not be) and should be visible if anything shows clusters marked
"bad" on the volume (not sure if anything does).

ChkDsk /R and Scandisk thourough / surface scan do the same sort of
thing, but only when these operations are explictly run by the user or
implicitly triggered on startup in response to flags indicating disk
access failure in the previous Windows session. Scandisk may or may
not log to C:\Scandisk.log, whereas ChkDsk (hopefully) does its
logging deep in the bowels of Event Viewer - and don't expect
something obvious like "ChkDsk", it will somewhere obscure like
"Windows Logon" or something.
Everything now is running EXCEPT Defrag (waiting
on Chkdsk) and Chkdsk itself not running. So am still
stuck???????

ChkDsk and Defrag may be replaced by 3rd-party utilities (e.g. Norton
Utilities or SystemWorks etc.). If the 3rd-party utilities are badly
"uninstalled" (e.g. DelTree rather than Add/Remove), you may be left
with no "hooks" to the original MS tools.

XP's Defrag tends to be far more tolerant than Win9x when it comes to
"files in use" - in fact, I've not seen it refuse to operate or
restart the process. But ChkDsk /F or /R requires exclusive access to
the volume, and when that volume is C:, that's impossible while
Windows is in session. So ChkDsk sets up AutoChk to do the test early
in the system's next bootup. It's unlikely anything would be running
that early to upset AutoChk; suspect malware if so.

OTOH, maybe there's some sort of "thou shalt not" security/permissions
thing that is disallowing the use of Defrag and/or ChkDsk.

Have you tried via Safe Mode, Admin logon?


------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top