Clean XP Pro install has FS errors

[Steve Nielsen]

This HDD was thoroughly tested with manufacturer's utility, no errors,
then zero-filled using same utility.
RAM thouroughly tested using Memtest86, no errors.
Clean install of XP Pro SP1 using OEM restore CD supplied with PC.
Nothing else done to it yet, except CHKDSK /F.

Why would a perfectly healthy drive have FS errors after a clean install
of XP, espcially after thorough testing?

This makes no sense to me and appears to me that something is awry in
XP's version of NTFS, or perhaps something screwey with CHKDSK itself in XP.

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 19 unused index entries from index $SII of file 0x9.
Cleaning up 19 unused index entries from index $SDH of file 0x9.
Cleaning up 19 unused security descriptors.

39070048 KB total disk space.
1732528 KB in 9021 files.
2216 KB in 554 indexes.
0 KB in bad sectors.
76788 KB in use by the system.
65536 KB occupied by the log file.
37258516 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
9314629 allocation units available on disk.

Internal Info:
82 25 00 00 72 25 00 00 64 2a 00 00 00 00 00 00 .%..r%..d*......
3a 00 00 00 00 00 00 00 7e 00 00 00 00 00 00 00 :.......~.......
40 4b 4c 00 00 00 00 00 aa ec a3 06 00 00 00 00 @KL.............
fc be 80 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 2c c8 bb 0e 00 00 00 00 ........,.......
99 9e 36 00 00 00 00 00 3d 23 00 00 00 00 00 00 ..6.....=#......
00 c0 be 69 00 00 00 00 2a 02 00 00 00 00 00 00 ...i....*.......

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

Steve

 

[Steve Nielsen]

Steve Nielsen wrote:

I just wiped out the partition and did a completely fresh install again
and it just gets better - this time CHKDSK /F found 23 errors!

Steve

 

[Guest]

My first guess would be the driver for the disk
controller. I had these symptoms until I downloaded a
new driver from my motherboard maker's support site. The
driver supplied didn't like certain models of disk
drives - one of which I had of course.

Most annoyingly, the updated driver wasn't on their main
(Taiwan) site or their US mirror. In desperation I found
it on the German mirror.

 

[Steve Nielsen]

My first guess would be the driver for the disk
controller. I had these symptoms until I downloaded a
new driver from my motherboard maker's support site. The
driver supplied didn't like certain models of disk
drives - one of which I had of course.

Most annoyingly, the updated driver wasn't on their main
(Taiwan) site or their US mirror. In desperation I found
it on the German mirror.

Thanks for the tip. I'll try that.

Steve

 

[Rock]

This HDD was thoroughly tested with manufacturer's utility, no errors,
then zero-filled using same utility.
RAM thouroughly tested using Memtest86, no errors.
Clean install of XP Pro SP1 using OEM restore CD supplied with PC.
Nothing else done to it yet, except CHKDSK /F.

Why would a perfectly healthy drive have FS errors after a clean install
of XP, espcially after thorough testing?

This makes no sense to me and appears to me that something is awry in
XP's version of NTFS, or perhaps something screwey with CHKDSK itself in
XP.

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 19 unused index entries from index $SII of file 0x9.
Cleaning up 19 unused index entries from index $SDH of file 0x9.
Cleaning up 19 unused security descriptors.

39070048 KB total disk space.
1732528 KB in 9021 files.
2216 KB in 554 indexes.
0 KB in bad sectors.
76788 KB in use by the system.
65536 KB occupied by the log file.
37258516 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
9314629 allocation units available on disk.

Internal Info:
82 25 00 00 72 25 00 00 64 2a 00 00 00 00 00 00 .%..r%..d*......
3a 00 00 00 00 00 00 00 7e 00 00 00 00 00 00 00 :.......~.......
40 4b 4c 00 00 00 00 00 aa ec a3 06 00 00 00 00 @KL.............
fc be 80 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 2c c8 bb 0e 00 00 00 00 ........,.......
99 9e 36 00 00 00 00 00 3d 23 00 00 00 00 00 00 ..6.....=#......
00 c0 be 69 00 00 00 00 2a 02 00 00 00 00 00 00 ...i....*.......

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

Steve

Steve, I don't think those "minor inconsistencies" -- the "unused"
errors you are seeing are significant. My system runs great and every
time I run check disk it comes up with some errors of that type on all
partitions. What happens if you query the drive's dirty bit from
start | run | cmd | enter
fsutil dirty query C:

If it says c: is NOT DIRTY then I wouldn't worry about those "minor
inconsistencies".

 

[Steve Nielsen]

Steve, I don't think those "minor inconsistencies" -- the "unused"
errors you are seeing are significant. My system runs great and every
time I run check disk it comes up with some errors of that type on all
partitions. What happens if you query the drive's dirty bit from
start | run | cmd | enter
fsutil dirty query C:

If it says c: is NOT DIRTY then I wouldn't worry about those "minor
inconsistencies".

It reports Volume - c: is NOT dirty

Thanks Rock. I know they are minor inconsistencies and I also see them
on other XP systems frequently.

Steve

 

[Rock]

It reports Volume - c: is NOT dirty

Thanks Rock. I know they are minor inconsistencies and I also see them
on other XP systems frequently.

Steve

You're welcome.