Defrag vs. chkdsk /f problem

[Guest]

Hi!

I have been facing a problem, that I can't get Defrag to start, just getting
an error/remark "first run chkdsk /f". It's not possible to get it running
because the disk is locked, so it will be scheduled to be run on the next
reboot.

But, it won't be running either upon the reboot!

So, what may be causing this behaviour?

I have now been
- checking/changing the dirty bit status
- checking/editing the BootExecute key
- trying to run chkdsk /f /r on MS-DOS
- trying to get Check Disk started on Windows with the two options
- checking the HP All-In-One Printer/Scanner drivers, but no updates
available
- running the System file Checker

but, nothing seems to help or correct this behaviour ... so, what to try next?


Best regards,

Pete V.

 

[Guest]

Go to run,type:cmd In cmd type:CLEANMGR Select to clean C: After type:
Defrag C: Defrag should run,you might after typeegrag C: /REVERT
Also,to run chk disk,install xp cd,boot to xp cd,recovery,select 1 For C:
Press enter for password,type:CHKDSK C: /p Or type:CHKDSK C: /R
The /p is correct for recovery,after type:EXIT Let xp restart.Also,in xp
cmd for Sfc Type:Sfc /Scannow /REVERT

 

[Guest]

When you use CHKDSK C: /F (replacing C with whatever drive is having the
problem), do you accept the prompt to run it on the next boot?

____________________
Shawn

 

[Guest]

Hi!

Please, following you have latest info on this "dirty
bit/chkdsk/chkntfs/autochk" issue of mine.

I have been doing several tests with these utilities noting, that the Check
Disk procedure is not working properly for the System Disk C: itself, but all
well and properly, if the same disk is set as a Work Disk E: under another
System Disk C:, a bit-by-bit back-up from the other one, but once again,
neither on this C: itself ...

Anyway, the initial Defrag vs. chkdsk /f problem was gone by this E: Check!

This may have something to do with the fact, that I had Diskeeper 9.0
installed on the System Disk, but did a total Windows XP repair install above
the old one, with all pertinent procedures, activation, SP2 and some 50+
updates etc. on it.

So, this is what happens:

A. Disk Check reboot trial for a separate Work Disk E:

Disk Check procedure with a "problematic" System Disk C: set as a Work
Disk E:
under another Windows XP System Disk is working all well!

Upon checking the statuses
- the Dirty Bit for E: is ok set off, but for C: remaining as it was
in the beginning,
if first off then still off, if first on then still on
- the BootExecute key is still "ready" for the /r for the drive C:,
before beginning
it was "ready" for the /r for the both C: and E:

B. Disk Check reboot trial for the System Disk C:

1. Regular start-up behaviour until the light blue screen for Disk Check

2. On the screen appearing in two-three seconds the following 5 text rows
(sorry, free translation)

The file system of the drive C: will be checked
File system type NTFS
The drive cannot be opened into use directly
Windows has checked the hard drive
....... (yes, 7 dots appearing one by one)

3. In a second after the above screen the system is got locked with an
empty black screen!

4. After power-down/up
- the black screen for Safe Mode appearing
- choosing Normal the regular start-up will begin/continue normally
through the light blue screen with the 5 text rows until the login
screen etc.,
so, now everything seems about normal

5. Upon checking the statuses
- the Dirty Bit is remaining as it was in the beginning, if first off
then still off, if first on then still on
- BootExecute key is still "ready" for the /r for the drive C:


So, what may be causing this "no Disk Check for C:" i.e. autochk failing,
and how to cure it?


Best regards,

Pete V.

 

[Guest]

Hi!

Thanks for your reply.

I did utilize some of your hints, but not all, as the problem got focused on
a "neighbouring" point, I may come back to this.


Best regards,

Pete V.

 

[Guest]

Hi!

Thanks for your reply.

Yes, the run has always got accepted.

Please, check my 2nd post on this topic.


Best regards,

Pete V.

 

[Guest]

Hi!

The problem totally solved!

Sorry, e.g. for Diskeeper, for some maybe misleading assumptions on this
topic ...

Yes, the mysterious locking up program, preventing autochk chkdsk to be
proceeded at boot-up for me, was the Spyware Doctor/ikhlayer.sys! I didn't
even have the Spyware Doctor active, so, I just simply deleted the
ikhlayer.sys file from Win\Sys32\Drivers and everything began to work
normally.

Many thanks for Wes for the advice at

http://www.microsoft.com/communitie...port&mid=a734fefb-fcf8-463d-beb7-595a65e377a2


Best regards,

Pete V.