How to fix this NTFS volume's file system integrity? (read first pls)
Posted on 2006-05-02
Windows XP on an NTFS HD (Maxtor 6y120L0) doesn't boot normal / safe mode (flashes XP logo / loads xp drivers, then reboots).
Using Hiren's boot disk, tried Scandisc. It doesn't see the HD at all. Neither does Mini98 (98 run from a cd).
So I tried Hirens / Maxtor HD diagnostic util. The Maxtor "install confirmation test" says "passed" for all tests up to last, a "smart attribute test", which fails. Running Maxtor "quicktest", it passes several tests and then hangs on "smart help test". (should take 90 secs. waited 5 mins, gave up)
So I ran Hiren's / Partition Magic. It sees the HD and partition. Running "Partition / check for errors" found some errors, and said it fixed most of them. Others it didn't fix. ("cluster errors" fixed, "crosslinked something" fixed, "file record marked free/used" unfixed, "requested frs entry is unused/free" unfixed)
So I tried Hiren's / Paragon Partition Manager / Check File System Integrity. It says:
"Incorrect File System - File Allocation Faults. (Crosslinked files) Chkdsk should be used to correct"
I ran Hirens / NTFS Dos Pro 5.0, and let it run "chkdsk" (actually, "NTFSCHK" by winternals?) It found and fixed stuff. rebooted. No change yet. Ran it again, tried the "scandisk" option after mounting the drive with NTFS Dos Pro again. It complained that another program was interfering with the drive. (probably NTFS DOS!)
I tried Paragon's File System Integrity check again, it gave the same message as above ("Run CHKDSK").
I tried running HIren's / HDD Smart UDM Viewer. It gave me a bunch of info I didn't understand, then said, "T.T.C. detected with life-critical attribute". Anyone know anything about this? (I googled it, no joy)
As I post this, just because I don't know how to proceed (tried NTFSCHK, but can't do scandisk or chkdsk in NTFS!), I'm trying the third Maxtor HD utility scan option -- full scan. But I think it's freezing.
(This is how I spend too much time on a problem.)
(1) Any ideas on what to try next?
(2) In this day and age, why are some dos level, boot disk diagnostic tools BLIND to NTFS? (I know hiren's is a great tool -- I just don't understand this issue)