MFT errors? chkdsk acting funny? Help!

[OzzieGT]

OK so I noticed today that my C: partition had only 3GB free. Finding this unusual, I decided to run chkdsk. It says there were problems and I needed to run on boot. So I did. It found some errors and I have 10 gigs free, but if I select all on my C drive it says I am only using 8 gigs so I should have 2 free. So I run chkdsk again...it says there are errors again and I need to restart. I restart and it doesn't find any errors. Hmm. I run chkdsk in windows again, it says there are errors and I need to restart. On boot it doesn't find any errors. This time I do a full surface scan on boot. I have run chkdsk twice in a row now (in windows) and this is what i have gotten:

The type of the file system is NTFS.
Volume label is System.

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)...
Index verification completed.
CHKDSK is recovering lost files.
Recovering orphaned file VBULLE~3.JS (920) into directory file 44780.
Recovering orphaned file vbulletin_global[2].js (920) into directory file 44780.
Recovering orphaned file VBULLE~2.JS (927) into directory file 58031.
Recovering orphaned file vbulletin_menu[2].js (927) into directory file 58031.
Recovering orphaned file ROLLOV~1.JS (937) into directory file 44780.
Recovering orphaned file rollovers[1].js (937) into directory file 44780.
Recovering orphaned file REGIST~1.GIF (947) into directory file 48876.
Recovering orphaned file register_over[1].gif (947) into directory file 48876.
Recovering orphaned file OS7FA0~1.TXT (96651) into directory file 9012.
Recovering orphaned file osman@burstnet[1].txt (96651) into directory file 9012.
Recovering orphaned file OS59DA~1.TXT (98989) into directory file 9012.
Recovering orphaned file osman@www.burstbeacon[2].txt (98989) into directory file 9012.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

20482843 KB total disk space.
9826700 KB in 69279 files.
36600 KB in 5981 indexes.
28 KB in bad sectors.
228047 KB in use by the system.
65536 KB occupied by the log file.
10391468 KB available on disk.

4096 bytes in each allocation unit.
5120710 total allocation units on disk.
2597867 allocation units available on disk.

C:\Documents and Settings\Osman>chkdsk
The type of the file system is NTFS.
Volume label is System.

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 numlist[1].gif in index $I30 of file 44780.
Deleting index entry NUMLIS~1.GIF in index $I30 of file 44780.
Deleting index entry editlivejava[1].js in index $I30 of file 48876.
Deleting index entry EDITLI~1.JS in index $I30 of file 48876.
Deleting index entry favicon[2].ico in index $I30 of file 48876.
Deleting index entry FAVICO~2.ICO in index $I30 of file 48876.
Deleting index entry italic[2].gif in index $I30 of file 48876.
Deleting index entry ITALIC~2.GIF in index $I30 of file 48876.
Deleting index entry messagepost[1].aspx in index $I30 of file 48876.
Deleting index entry MESSAG~1.ASP in index $I30 of file 48876.
Deleting index entry raisedmenuback[1].gif in index $I30 of file 48876.
Deleting index entry RAISED~1.GIF in index $I30 of file 48876.
Deleting index entry bullist[1].gif in index $I30 of file 58031.
Deleting index entry BULLIS~1.GIF in index $I30 of file 58031.
Deleting index entry htmleditor[1].js in index $I30 of file 58031.
Deleting index entry HTMLED~1.JS in index $I30 of file 58031.
Deleting index entry link[1].gif in index $I30 of file 58031.
Deleting index entry LINK_1~1.GIF in index $I30 of file 58031.
Deleting index entry bold[1].gif in index $I30 of file 71393.
Deleting index entry BOLD_1~1.GIF in index $I30 of file 71393.
Deleting index entry messagepost[1].htm in index $I30 of file 71393.
Deleting index entry MESSAG~1.HTM in index $I30 of file 71393.
Deleting index entry raisedmenusep[1].gif in index $I30 of file 71393.
Deleting index entry RAISED~1.GIF in index $I30 of file 71393.
Deleting index entry under[1].gif in index $I30 of file 71393.
Deleting index entry UNDER_~1.GIF in index $I30 of file 71393.
Index verification completed.

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

Any ideas what the hell is going wrong? This is like the fourth or fifth time it has "corrected errors in the MFT BITMAP attribute". Is my HDD on it's way out? It's an 80GB Seagate...it's about 3 years old now.

 

[aGreenAgent]

It doesn't have /f specified, so it's probably not fixing much.

Run chkdsk /r and see what happens.

 

[OzzieGT]

I know it doesn't have /f specified...I can't specify /f on the C: drive without having it run on-boot. When I run on boot it's not finding anything...

Every time I run it, it finds more invalid index files...

Does /r just do a surface scan? Cuz like I asid in my post, I ran that already.

 

[aGreenAgent]

/r is a surface scan, but it also invokes the /f switch.

I'd give it a try, but you might want to bring you HD to someone else's computer and slave it, and have them chkdsk it from windows.

 

[OzzieGT]

I think my indexing files are corrupt. Any idea where I can find them and remove them? I have turned indexing off anyway...

I've already cleaned out index.dat in my cookies, temp internet files, and history

 

[lansalot]

NTFS indexes, not "indexing service" indexes.

Get manufacturers disk utility and run a non-desctructive scan using it, it will be more thorough than CHKDSK.

 

[dclive]

Originally posted by: lansalot
NTFS indexes, not "indexing service" indexes.

Get manufacturers disk utility and run a non-desctructive scan using it, it will be more thorough than CHKDSK.

That would attempt to find mechanical or read/write errors on the drive, but would not fix any NTFS-corruption issues he's got.

If running CHKDSK on boot doesn't fix the issue (what, exactly, does the eventlog say when you schedule this?) then slave the drive to another machine and chkdsk (/f) it from there.