CHKDSK is being shady

G

GJSNeptune

[H]F Junkie
Joined
Mar 31, 2004
Messages
12,372
A few weeks ago I reinstalled XP Pro on a new hard drive.

160GB (new) - Windows
120GB - Two partitions, Windows and storage
40GB - Two partitions, older Windows and storage

Since my storage drives still have partitions, I'm going to transfer those files to the new drive, wipe and reformat the storage drives, and probably transfer the files back. I've been slowly copying over the files in case the new drive fails. It's been over a month and it still seems fine, except for CHKDSK being strange. I've used the WD Diagnostic program and it says the drive passes.

After about a week with the new drive, I copied over a large amount of files, mostly music, maybe 50GB or more. On the next reboot, CHKDSK decided to run and said it was correcting index errors and it deleted some of the mp3s I have transferred over. During CHKDSK, the songs it deleted were shortened with weird filenames, so I didn't know which songs it removed. Then it rebooted and Windows loaded like normal.

I figured it was okay since I still have the original folders of music that I could just copy back over because I didn't know which songs it deleted. Maybe a week later I copied over another large amount of files, and sure enough, on the next reboot, CHKDSK ran and did the same thing. I Googled to see if CHKDSK left a log, and of course it does, so I opened it up.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The attribute record length 0x30 is too small for attribute of
type 0x90 and instance tag 0x0. The minimum value is 0x40.
Deleting corrupt attribute record (144, "")
from file record segment 49540.
The attribute form code 0xa0 is invalid for attribute of type 0x10
and instance tag 0x0.
Deleting corrupt attribute record (16, "")
from file record segment 49540.
The file name in file name value in attribute of type 0x30 and instance
tag 2 contains unicode NULL.
a9 c6 00 00 00 00 01 00 01 d4 1a 64 c1 6d c7 01 ...........d.m..
01 d4 1a 64 c1 6d c7 01 01 d4 1a 64 c1 6d c7 01 ...d.m.....d.m..
01 d4 1a 64 c1 6d c7 01 00 00 00 00 00 00 00 00 ...d.m..........
00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
1d 01 30 00 37 00 20 00 50 00 61 00 67 00 65 00 ..0.7. .P.a.g.e.
20 00 39 00 35 00 20 00 41 00 72 00 00 10 e1 0d .9.5. .A.r.....
00 10 00 00 00 20 cd 3a 00 10 00 00 00 b0 be 31 ..... .:.......1
00 10 00 00 20 00 39 00 70 00 67 00 00 00 00 00 .... .9.p.g.....
80 00 00 00 48 00 00 00 01 00 00 00 00 00 04 00 ....H...........
Deleting corrupt attribute record (48, "")
from file record segment 50864.
The index root $I30 is missing in file 0xc184.
Correcting error in index $I30 for file 49540.
The file name index present bit in file 0xc184 should not be set.
Correcting a minor error in file 49540.
There is no NTFS file name attribute in file 0xc6b0.
Correcting minor file name errors in file 50864.
Unable to locate the file name attribute of index entry 07 Page 95 Art Contest #1.jpg
of index $I30 with parent 0xc6a9 in file 0xc6b0.
Deleting index entry 07 Page 95 Art Contest #1.jpg in index $I30 of file 50857.
Unable to locate the file name attribute of index entry 07PAGE~1.JPG
of index $I30 with parent 0xc6a9 in file 0xc6b0.
Deleting index entry 07PAGE~1.JPG in index $I30 of file 50857.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file 07PAGE~1.JPG (50864) into directory file 50857.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
Inserting data attribute into file 49540.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

160826683 KB total disk space.
91978116 KB in 56031 files.
21236 KB in 4809 indexes.
0 KB in bad sectors.
131847 KB in use by the system.
65536 KB occupied by the log file.
68695484 KB available on disk.

4096 bytes in each allocation unit.
40206670 total allocation units on disk.
17173871 allocation units available on disk.

Internal Info:
f0 ed 00 00 b2 ed 00 00 2a 7b 01 00 00 00 00 00 ........*{......
a4 08 00 00 00 00 00 00 f2 00 00 00 00 00 00 00 ................
22 20 48 02 00 00 00 00 10 58 e7 28 00 00 00 00 " H......X.(....
d0 3f 44 01 00 00 00 00 00 00 00 00 00 00 00 00 .?D.............
00 00 00 00 00 00 00 00 e0 ff b4 33 00 00 00 00 ...........3....
99 9e 36 00 00 00 00 00 00 38 07 00 df da 00 00 ..6......8......
00 00 00 00 00 10 e6 ed 15 00 00 00 c9 12 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
Click to expand...

Why is it doing this? I never had CHKDSK do this during my previous install/hard drive, which was also XP Pro. However, my current install was slipstreamed with nLite. I don't know if that affects this at all.
 
Sorry I didn't respond to your PM. It was on today's "to do list"! Anyway, the drive is probably physically fine, since it passes the WD test. You could also try running Memtest, although I'd think you would have more errors if the memory was bad. This is just a guess, but I've seen a lot of weird problem threads state that the build was done with an nLite disc. I've avoided that software because I did one build with it, and had very odd problems as well. Today's computers are fast enough that there isn't really a need to strip anything out of XP.
 
I like having the feeling of system cleanliness, and I'm a bit too far after the install to reinstall with the official XP disc. Plus I need this to juice this computer's performance as much as possible. It has to last me through the year.
 
I didn't mean it as in you need to upgrade. I meant it as, nLite might very well be causing a problem, based on a component you removed, even if nLite gave you no warnings. Removing components with nLite really doesn't do anything in terms of resources...it's designed to save some hard drive space after the install. nLite is infamous for causing very weird issues.
 
I know. I just don't feel like reinstalling, but I guess I'll have to if CHKDSK keeps running whenever I copy over lots of files. Maybe I'll try doing it in smaller chunks.
 
You must log in or register to reply here.
Back
Top