Deleting Index entry - why so many and what to do? chkdsk question

[pistonpilot]

C:\Documents and Settings\root>chkdsk
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry resume.dat in index $I30 of file 48292.
Deleting index entry resume.dat.old in index $I30 of file 48292.
Deleting index entry RESUME~1.OLD in index $I30 of file 48292.
Deleting index entry Dc104.zip in index $I30 of file 61359.
Deleting index entry Dc105.exe in index $I30 of file 61359.
Deleting index entry Dc106.exe in index $I30 of file 61359.
Deleting index entry Dc107.lnk in index $I30 of file 61359.
Deleting index entry Dc108.zip in index $I30 of file 61359.
Deleting index entry Dc109.lnk in index $I30 of file 61359.
Deleting index entry Dc110.zip in index $I30 of file 61359.
Deleting index entry Dc111.wmv in index $I30 of file 61359.
Deleting index entry Dc112.avi in index $I30 of file 61359.
Deleting index entry Dc96.lnk in index $I30 of file 61359.
Deleting index entry Dc97.lnk in index $I30 of file 61359.
Deleting index entry OIScatalog.cag in index $I30 of file 138813.
Deleting index entry OISCAT~1.CAG in index $I30 of file 138813.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

C:\Documents and Settings\root>chkdsk /f c:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

C:\Documents and Settings\root>

I can run chkdsk /f c: many times and I still get these minor or maybe not so minor errors. One thing I've noticed, is that I cannot move a folder nor delete a folder directory as it stops in the middle and tells me that the directory is not empty.

I can do a copy with no errors. I frequently have this across systems in varying degrees. I shudder to think about running a /r as it takes such a long time.

What causes these errors and what can be done to mitigate their occurrence?

[pitbullthe1st]

Have you tryed using a disk serfice scanner like DH tune you can download it free here http://www.hdtune.com/hdtune_255.exe this will tell you if you have any bad blocks on your hard drive. It can also tell you the read/wright speed and give you the S.M.A.R.T. infomation from the HDD. If you have bad blocks then it is time for a new hard drive.

As for file recovery you could use this program and it could help you to get most if not all of your files back even if the HDD is corupted http://www.pcinspector.de/Sites/file_recovery/download.htm?language=1

As for not being able to delete files this program should help it will tell you what proces is using the file and it will give you the option to kill the process and deleat the file http://ccollomb.free.fr/unlocker/index.htm

[pistonpilot]

I've used that program before and also use Spinrite - drive is fine. It's just Windows being Windows. Is there another program out there that does a better job than chkdsk?