CHKDSK - what do these results mean??

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

I have a Sony VAIO, and ran a CHKDSK /V which returned the following:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\richard>chkdsk c: /v
The type of the file system is NTFS.
Volume label is VAIO.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Detected minor inconsistencies on the drive. This is not a corruption.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Cleaning up 156 unused index entries from index $SII of file 9.
Cleaning up 156 unused index entries from index $SDH of file 9.
Cleaning up 156 unused security descriptors.
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

19535008 KB total disk space.
8973768 KB in 74887 files.
26268 KB in 3322 indexes.
0 KB in bad sectors.
138372 KB in use by the system.
43024 KB occupied by the log file.
10396600 KB available on disk.

4096 bytes in each allocation unit.
4883752 total allocation units on disk.
2599150 allocation units available on disk.

C:\Documents and Settings\richard>

I have run CHKDSK /F and CHKDSK /R on reboot which report that "the
volume is clean", but still I get this same result when doing CHKDSK /V.
My defrag software does not run, as it too detects some anomalies. I have
tried re-formatting the C: drive and re-installing - but still the same
message.

What does this mean? Is is something to worry about?

thanks
Richard
 
It means that running chkdsk in the read-only mode is a waste of time.

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message if
there are open files on the disk. If you do not specify the /f command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.]]

[[In read-only mode, CHKDSK quits before it completes all three phases if it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to guarantee
a static state is to lock the volume. CHKDSK locks the volume only if you
specify the /F switch (or the /R switch, which implies /F). You may need to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode. ]]

--
Hope this helps. Let us know.
Wes

In
Richard said:
I have a Sony VAIO, and ran a CHKDSK /V which returned the following:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\richard>chkdsk c: /v
The type of the file system is NTFS.
Volume label is VAIO.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Detected minor inconsistencies on the drive. This is not a
corruption. CHKDSK is verifying security descriptors (stage 3 of 3)...
Cleaning up 156 unused index entries from index $SII of file 9.
Cleaning up 156 unused index entries from index $SDH of file 9.
Cleaning up 156 unused security descriptors.
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

19535008 KB total disk space.
8973768 KB in 74887 files.
26268 KB in 3322 indexes.
0 KB in bad sectors.
138372 KB in use by the system.
43024 KB occupied by the log file.
10396600 KB available on disk.

4096 bytes in each allocation unit.
4883752 total allocation units on disk.
2599150 allocation units available on disk.

C:\Documents and Settings\richard>

I have run CHKDSK /F and CHKDSK /R on reboot which report that "the
volume is clean", but still I get this same result when doing CHKDSK
/V. My defrag software does not run, as it too detects some
anomalies. I have tried re-formatting the C: drive and re-installing
- but still the same message.

What does this mean? Is is something to worry about?

thanks
Richard
Click to expand...
 
It means that running chkdsk in the read-only mode is a waste of time.

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error
message if there are open files on the disk. If you do not specify the
/f command-line option and open files exist, chkdsk might report lost
allocation units on the disk. This could happen if open files have not
yet been recorded in the file allocation table. If chkdsk reports the
loss of a large number of allocation units, consider repairing the
disk.]]

[[In read-only mode, CHKDSK quits before it completes all three phases
if it encounters errors in earlier phases, and CHKDSK is prone to
falsely reporting errors. For example, CHKDSK may report disk
corruption if NTFS happens to modify areas of a disk while CHKDSK is
examining the disk. For correct verification, a volume must be static,
and the only way to guarantee a static state is to lock the volume.
CHKDSK locks the volume only if you specify the /F switch (or the /R
switch, which implies /F). You may need to run CHKDSK more than once
to get CHKDSK to complete all its passes in read-only mode. ]]
Click to expand...

thanks Wes, I seem to understand from your post that running with /r or
/f which forces a reboot is more reliable. Thus, running with /v might
well return false data. So what I am seeing with the /v switch is really
meaningless compared with the clean bill of health that /r or /f return.

This would in turn mean that I have nothing to worry about?

thanks
Richard
 
Richard,

Yep. As near as I can tell running chkdsk in read-only mode is meaningless.

You should be OK.

I ran chkdsk c: /v and got nearly the same results that you posted.
With the exceptions: # of unused index entries & disk space.

--
Hope this helps. Let us know.
Wes

In
Richard said:
It means that running chkdsk in the read-only mode is a waste of
time.

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error
message if there are open files on the disk. If you do not specify
the /f command-line option and open files exist, chkdsk might report
lost allocation units on the disk. This could happen if open files
have not yet been recorded in the file allocation table. If chkdsk
reports the loss of a large number of allocation units, consider
repairing the disk.]]

[[In read-only mode, CHKDSK quits before it completes all three
phases if it encounters errors in earlier phases, and CHKDSK is
prone to falsely reporting errors. For example, CHKDSK may report
disk corruption if NTFS happens to modify areas of a disk while
CHKDSK is examining the disk. For correct verification, a volume
must be static, and the only way to guarantee a static state is to
lock the volume. CHKDSK locks the volume only if you specify the /F
switch (or the /R switch, which implies /F). You may need to run
CHKDSK more than once to get CHKDSK to complete all its passes in
read-only mode. ]]
Click to expand...

thanks Wes, I seem to understand from your post that running with /r
or /f which forces a reboot is more reliable. Thus, running with /v
might well return false data. So what I am seeing with the /v switch
is really meaningless compared with the clean bill of health that /r
or /f return.

This would in turn mean that I have nothing to worry about?

thanks
Richard
Click to expand...
 
You have a problem if defrag is prevented from running due to errors in the
disk. If Error Checking on bootup cannot repair the errors , I would suggest
running a disk testing utility from the maker of the hard drive. Jym



Richard said:
It means that running chkdsk in the read-only mode is a waste of time.

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error
message if there are open files on the disk. If you do not specify the
/f command-line option and open files exist, chkdsk might report lost
allocation units on the disk. This could happen if open files have not
yet been recorded in the file allocation table. If chkdsk reports the
loss of a large number of allocation units, consider repairing the
disk.]]

[[In read-only mode, CHKDSK quits before it completes all three phases
if it encounters errors in earlier phases, and CHKDSK is prone to
falsely reporting errors. For example, CHKDSK may report disk
corruption if NTFS happens to modify areas of a disk while CHKDSK is
examining the disk. For correct verification, a volume must be static,
and the only way to guarantee a static state is to lock the volume.
CHKDSK locks the volume only if you specify the /F switch (or the /R
switch, which implies /F). You may need to run CHKDSK more than once
to get CHKDSK to complete all its passes in read-only mode. ]]
Click to expand...

thanks Wes, I seem to understand from your post that running with /r or
/f which forces a reboot is more reliable. Thus, running with /v might
well return false data. So what I am seeing with the /v switch is really
meaningless compared with the clean bill of health that /r or /f return.

This would in turn mean that I have nothing to worry about?

thanks
Richard
Click to expand...
 
You have a problem if defrag is prevented from running due to errors
in the disk. If Error Checking on bootup cannot repair the errors , I
would suggest running a disk testing utility from the maker of the
hard drive. Jym
Click to expand...
well, it's O&O defrag rather than Windows native defragger.

what puzzles me is that I formatted the drive and I still get these errors
on a /v switch. I've noticed that drive d: gets the same. But then I see
that my main PC does exactly the same, it's always file 9 that has the
"problem" with security descriptors.

I think this is a Windows anomaly - thanks for the posts everyone, I shall
sleep tonight!

Richard
 
Hello , I am not a qualified compuerist .
For the last year and 3 months I have been reinstalling Windows X Home
Edition . This has been necessary because the electricity circuit board
and other electricity related wiring needs upgrading in this old house
according to 3 electricians via the landlord . And I love using my
computer and I like Microsoft for helping me pass my time less idly .
I am waiting for the landlords response after 4 weeks .
Every harddrive I have used in this computer at this location has
made a clicking sound , think what you will , I'm unqualified ......
Now I remember on 3 occasions I have run Checkdisk and CheckDisk has
, on seperate runs of the program , found security descriptors and file
attributes and removed them .
Here is the details of the CheckDisk scan with both options checked :
Index enrty ID522 in index $SII of file 9
index entry with ID from index$SDH of file 9
Cleaning up 7 unused index entries from index $SII of file 9
Cleaning up 7 unused index entries from index $SDH of file 9
Cleaning up 7 unused security descriptors

....now the only things I can imagine that could have been wrong would
have been the harddrive failing due to the lack of power to them and
from what I have understood from browsing the internet Windows may have
tried to help the computer with itself or downloaded something itself
from Microsoft without me knowing of or those security descriptors
could have been from any of the various AntiVirus programs I tried to
run . Or when on the last occasion I ran CheckDisk when it removed :
deleting corrupt attribute record (128, "")from the file record
segment 6182 .
And on another CheckDisk CheckDisk removed a file $130 , which I
believe is Windows help file .
Someone here may find their mind equal to understanding this
information . It meant very little to my meagre mind .
Maybe Richard has a failing harddrive or his harddrive/s do not get
enogh power for some reason .........like my harddrives ?
 
Back
Top