Member Avatar for Member #227351

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?

  • 2 Contributors
  • 2 Replies
  • 2K Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by Member #227351

Dani AI

Generated

@pistonpilot those “Deleting index entry … in index $I30” lines mean chkdsk is fixing a folder’s NTFS directory index (the $I30 B-tree that tracks file names). The many Dc###.* names are typical of the Recycle Bin on XP/2003, so most of what you are seeing is chkdsk cleaning up stale Recycle Bin entries rather than deleting your live files. (sans.org)

Quick things that usually clear the “directory is not empty” problem you described:

  • Reset the Recycle Bin (this only empties the bin; Windows recreates it automatically).

For XP/2003:

rd /s /q C:\RECYCLER

For Vista and later:

rd /s /q C:\$Recycle.Bin

Then reboot and try the delete/move again. (forensicfocus.com)

If Windows says something is “in use,” find and close the lock before deleting. Use Sysinternals Process Explorer (Ctrl+F to search for the folder/file) or the Handle command-line tool to see which process has an open handle and close it safely. (learn.microsoft.com)

A few chkdsk tips so you are not running it in circles:

  • After you schedule a fix, review the detailed report in Event Viewer (Application log, source: Wininit/Chkdsk) to confirm what was repaired. (learn.microsoft.com)
  • If the volume keeps re-marking itself dirty, check it explicitly:
fsutil dirty query c:

If it reads “is dirty” after every reboot, dig deeper (drivers, frequent crashes, power loss). (learn.microsoft.com)

  • When corruption persists, run the deeper scan overnight on spinning HDDs; the /r pass includes /f and checks sectors as well. (learn.microsoft.com)

is right that hardware matters; SMART issues will make corruption recur no matter how often you repair. But if the disk tests clean, cleaning up the Recycle Bin and closing open handles usually stops these repeated $I30 fixes. (learn.microsoft.com)

Member Avatar for pitbullthe1st

Have you tryed using a disk serfice scanner like DH tune you can download it free here 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

Member Avatar for Member #227351

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?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.