CHKDSK Always finds something wrong....


D

Dave Onex

Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it checks
the disks. Every single time it finds something wrong. I literally do a disk
check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave
 
Ad

Advertisements

J

Jim

Dave Onex said:
Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it
checks the disks. Every single time it finds something wrong. I literally
do a disk check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave
Those are file system errors which the manufacturer's diagnostic might not
catch.
Jim
 
N

nass

Dave Onex said:
Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it checks
the disks. Every single time it finds something wrong. I literally do a disk
check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave


Open a run command and type in:
cmd.exe click [OK] then on the command prompt type in:
fsutil dirty query c: <= Hit Enter on your keyboard.

What the report say?


The CHKDSK utility incorrectly identifies and deletes in-use security
descriptors with HotFix
http://support.microsoft.com/kb/831374

HTH,
nass
 
N

nass

Dave Onex said:
Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it checks
the disks. Every single time it finds something wrong. I literally do a disk
check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave


Again can you run the defrag please in Safe Mode.
 
D

Dave Onex

nass said:
Dave Onex said:
Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it
checks
the disks. Every single time it finds something wrong. I literally do a
disk
check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if
I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave


Open a run command and type in:
cmd.exe click [OK] then on the command prompt type in:
fsutil dirty query c: <= Hit Enter on your keyboard.

What the report say?


The CHKDSK utility incorrectly identifies and deletes in-use security
descriptors with HotFix
http://support.microsoft.com/kb/831374

Hi Nass - thanks for the reply :)

Running fsutil dirty query c: shows that the volume is NOT dirty - which is
what I expected.
This is a new RAID 0 array with a new O/S install and there's not been any
unexpected power failures etc that would cause file system/index corruption
(that I can think of).

My expectation is that even if there was something a little out of kilter
CHKDSK would fix it and immediately running CHKDSK again would show zero
errors/issues.

The KB article you mentioned sounded like it might be a possible root cause
but the problem was supposed to have been addressed with the latest service
pack for XP - I'm all up to date in that respect. So, I don't know why it
would find things wrong when there's no reason to.

The O/S is only 2 or 4 days old so far.... :)
 
Ad

Advertisements

N

nass

Dave Onex said:
nass said:
Dave Onex said:
Hi Folks;

I'm running MCE 2005. It's a clean install with all updates on a RAID 0
array.
I used the hard drive vendors diagnostic utility to completely scan both
disks - both are perfect.

Every once in a while I do a CHKDSK through XP and when I re-start it
checks
the disks. Every single time it finds something wrong. I literally do a
disk
check back to back and every time it will find something.
Why is this? There doesn't actually appear to be anything wrong with the
disks (they are new and pass the most stringent diagnostic tests) yet if
I
do a CHKDSK it will always find something...

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 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
976760000 KB total disk space.
210728248 KB in 45597 files.
14964 KB in 4463 indexes.
0 KB in bad sectors.
159916 KB in use by the system.
65536 KB occupied by the log file.
765856872 KB available on disk.

Thanks!
Dave


Open a run command and type in:
cmd.exe click [OK] then on the command prompt type in:
fsutil dirty query c: <= Hit Enter on your keyboard.

What the report say?


The CHKDSK utility incorrectly identifies and deletes in-use security
descriptors with HotFix
http://support.microsoft.com/kb/831374

Hi Nass - thanks for the reply :)

Running fsutil dirty query c: shows that the volume is NOT dirty - which is
what I expected.
This is a new RAID 0 array with a new O/S install and there's not been any
unexpected power failures etc that would cause file system/index corruption
(that I can think of).

My expectation is that even if there was something a little out of kilter
CHKDSK would fix it and immediately running CHKDSK again would show zero
errors/issues.

The KB article you mentioned sounded like it might be a possible root cause
but the problem was supposed to have been addressed with the latest service
pack for XP - I'm all up to date in that respect. So, I don't know why it
would find things wrong when there's no reason to.

The O/S is only 2 or 4 days old so far.... :)

As Lesley in another thread, you can try to Restore the system and then
monitor what can cause this to happen.

HTH,
nass
http://www.nasstec.co.uk
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top