Every so often, my hard drive (Stats: AMD Sempron 2800+; Seagate 80GB
SATA; WinXP-Home 5.1, SP2; AV: Kaspersky 6.0; FW: ZoneAlarm
6.5.737.000) is prone to "cycling" (-?: "tick-tick-tick-tick,
chuh-chuh"; "tick-tick-tick-tick, chuh-chuh", ... [does it several
times, then resumes]) or sometimes it will abort boot-up, saying
something like "unable to mount volume" (sometimes I'll try again, and
it may boot-up, fine).
I'll run ChkDsk (sometimes it will resolve in "read-only" mode,
otherwise with /F, or /P in CONSOLE mode), with a typical "benign"
result being:
-------------------------
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
73023425 KB total disk space.
6674248 KB in 48717 files.
29668 KB in 4075 indexes.
336 KB in bad sectors.
166693 KB in use by the system.
65536 KB occupied by the log file.
66152480 KB available on disk.
4096 bytes in each allocation unit.
18255856 total allocation units on disk.
16538120 allocation units available on disk.
-------------------------
Lately there have been a few unusual ones, such as
-------------------------
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Read failure with status 0xc000009c at offset 0x834000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0x83c000 for 0x1000
bytes.
File record segment 8416 is unreadable.
Read failure with status 0xc000009c at offset 0x83c000 for 0x1000
bytes.
File record segment 8417 is unreadable.
Read failure with status 0xc000009c at offset 0x162d30000 for 0x10000
bytes.
The object id index entry in file 0x19 points to file 0x20e0 but the
file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0x20e1 but the
file has no object id in it.
Deleting an index entry from index $O of file 25.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
73023425 KB total disk space.
6433460 KB in 47983 files.
29240 KB in 4064 indexes.
328 KB in bad sectors.
166693 KB in use by the system.
65536 KB occupied by the log file.
66393704 KB available on disk.
4096 bytes in each allocation unit.
18255856 total allocation units on disk.
16598426 allocation units available on disk.
-------------------------
I don't mean the "File record segment ##### is unreadable" and "bad
cluster", "free space discovery", "volume bitmap" elements at the end
(which isn't unusual), but the "Read failure" and "object id index"
stuff.
Then, when I ran it Saturday, it responded
-------------------------
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Read failure with status 0xc000009c at offset 0x162930000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0x162939000 for 0x1000
bytes.
File record segment 16932 is unreadable.
Read failure with status 0xc000009c at offset 0x162939000 for 0x1000
bytes.
File record segment 16933 is unreadable.
Read failure with status 0xc000009c at offset 0x162939000 for 0x1000
bytes.
File record segment 16934 is unreadable.
Read failure with status 0xc000009c at offset 0x162939000 for 0x1000
bytes.
File record segment 16935 is unreadable.
Read failure with status 0xc000009c at offset 0x162939400 for 0x400
bytes.
The object id index entry in file 0x19 points to file 0x4224 but the
file has no object id in it.
Deleting an index entry from index $O of file 25.
Insufficient disk space to correct errors
in index $O of file 48735.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file SCATEG~1.DAT (19717) into directory file
16934.
Recovering orphaned file SCategory.dat (19717) into directory file
16934.
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system that could not be
corrected.
73023425 KB total disk space.
8210920 KB in 51827 files.
31500 KB in 4148 indexes.
340 KB in bad sectors.
166701 KB in use by the system.
65536 KB occupied by the log file.
64613964 KB available on disk.
4096 bytes in each allocation unit.
18255856 total allocation units on disk.
16153491 allocation units available on disk.
-------------------------
So I tried it again (/F) and at a point (beginning of "stage 2"?) if
just started an infinite run of "Inserting an index entry into index $O
of file 25."
I then tried it in CONSOLE (/P) mode and it responded
-------------------------
Checking file system on \DosDevices\C:
The type of the file system is NTFS.
The volume is dirty.
The index bitmap for index $O in file 0x19 is invalid or missing.
Correcting error in index $O for file 25.
The index bitmap $O is present but there is no corresponding index
allocation attribute in file 0x19.
Correcting error in index $O for file 25.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 01 02 00 00 00 00 00 00 ................
00 00 00 00 35 4b 98 b8 d0 62 c5 01 ff ff ff ff ....5K...b......
Sorting index $O in file 25.
The object id in file 0x0 does not appear in the object id index in
file 0x19.
Inserting an index entry into index $O of file 25.
The object id in file 0x3 does not appear in the object id index in
file 0x19.
Inserting an index entry into index $O of file 25.
The object id in file 0x5 does not appear in the object id index in
file 0x19.
Inserting an index entry into index $O of file 25.
[...this continues for about 117 entries, afterwhich it aborts (times
out?) in the middle of the 118th...]
The object id in file 0xed does not appear in the object id index in
file 0x19.
Inserting an index entry into index $O of file 25.
The object id in file 0xee does not appear in th
-------------------------
Since then, /F just runs away with "Inserting an index entry into index
$O of file 25" (though, in read-only mode, it just returns two
"Correcting error in index $O for file 25" in stage 2, finishes stage
2, then aborts with "Errors found. CHKDSK cannot continue in read-only
mode.") and /P mostly repeats the above attempt.
Whenever I start (boot-up) now, I get the "ChkDsk needs to be run"
message: When I skip it, the WinXP LogOn/Profiles page loads with "The
file or directory C:\WINDOWS is corrupt and unreadable. Please run the
Chkdsk utility" program error message--though I can enter a profile
and everything *SEEMs* to load okay, though I get another
"file/directory corrupt" error alert, either for "C:\WINDOWS" or
"C:\WINDOWS\System32".
I think I've found the crux of the problem: When I went to open an
image in an e-mail, I got a "could not be saved, because you cannot
change the contents of that folder." So I opened up the folder and
clicked on its properties and--lo and behold--it is checked
"Read-only" (not "grayed out", but off-color)! I unchecked it,closed
properties and reopened it and, again, "read-only" was checked! I
tried other folders, with the same results.
Then, yesterday, while saving my critical files to floppy disk (just in
case P=), I went to copy FireFox's bookmarks, inspected the folders
properties (like everything else, "read-only" was checked) and saw that
its contents was over 2 GB! I opened it up and found over a thousand
sequentially numbered copies of the bookmarks file (html) as well as a
ton of numbered copies of the cookies file!!!
Apparently FF isn't able to delete the original bookmark and cookie
files, so it just saves them as new files: The funny thing is, I can
delete all of the bookmark (and cookie) copies and even edit and resave
(using WordPad) the original bookmark file--I just can't delete it!
Thus, I suspect that the nature of the "WINDOWS corruption" is just
that ChkDsk and the LogOn/Profiles page can't alter the folders (and,
yes, I did try loading in safe-mode, using the administrator profile,
with the same results).
Is this simply a case of some switch somewheres being mismarked (that I
can correct), or is this something that needs to be taken "to the
shop"?--or is it FUBAR???
~Kaimbridge~
-----
Wikipedia-Contributor Home Page:
http://en.wikipedia.org/wiki/User:Kaimbridge
***** Void Where Permitted; Limit 0 Per Customer. *****
Reply With Quote
Bookmarks