CHKDSK /F

R

RScotti

Hi,
For some reason the Event Viewer doesn't show the winlogon event 1001 info.and there is no file name Bootex.log in the
C:\ root directory.
I just did a clean install with the HP Recovery Disks today and still don't have it.This was one reason I did it the
other was to try an get the Recovery Console didn't get that either.

HP Recovery system SUCKS!

Can you please tell me if when you do the Chkdsk /f do you get three or four options that it checks
1 File verify something (scan 1 of 4 scans)
2 index verify (scan 2 of 4 scans)
3 security verify (scan 3 of 4 scans)
4 file data verify? (scan 4 of 4 scans)

OR


1 File verify something (scan 1 of 3 scans)
2 index verify (scan 2 of 3 scans)
3 security verify (scan 3 of 3 scans)

I would really like to do the /F instead of doing the /R but don't know if the /F is working correctly.

Read-only mode is chkdsk with NO switches.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_pwfd.asp

[[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.]]
From...
Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx

[[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. ]]
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

To take advantage of all the Chkdsk parameters, use the command-line version
of Chkdsk.

See..
Understanding what CHKDSK does
here...
An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

Don't even bother running CHKDSK in read-only mode. It is a waste of time
and prone to not accurately reporting information. CHKDSK might report
spurious errors because it cannot lock the drive.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]

You have to reboot for Error-checking to run.

For a look at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Have a good day,
RScotti

remove "nospam" in order to email me.
 
A

Al Pilarcik

Curt said:
From:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true



/f : Fixes errors on the disk. The disk must be locked. If chkdsk
cannot lock the drive, a message appears that asks you if you want to
check the drive the next time you restart the computer.

"Chkdsk corrects disk errors only if you specify the /f command-line
option" and
/r : Locates bad sectors and recovers readable information. The disk
must be locked
Finding physical disk errors

Use the /r command-line option to find physical disk errors in the
file system.

Nowhere can I find anything about /r fixing files, only /f.


chkdsk /R is a superset of chkdsk /f

"On NTFS: Displays cleanup messages if any.
Locates bad sectors and recovers readable information
(implies /F)"
 
A

Al Pilarcik

RScotti said:
Hi,
Can someone please help me on this? I am totally confused.
If possible I would like some document from some source to give to HP.


I have been having problems running Chkdsk /f so I talked to HP and
they said "When you run it with the /f it only does three options."
This is what it does in READ ONLY MODE(Chkdsk no/x)


chkdsk f: /f/v

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Windows has checked the file system and found no problems.




chkdsk f: /R

The type of the file system is NTFS.
Volume label is data.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
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.
Windows has checked the file system and found no problems.
 
R

RScotti

Hi Al,
chkdsk f: /f/v

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Windows has checked the file system and found no problems.
If you ran this without the /v would you get the same thing?

Have a good day,
RScotti

remove "nospam" in order to email me.
 
A

Al Pilarcik

RScotti said:
Hi Al,

If you ran this without the /v would you get the same thing?



Yes, the exact same output.

v means 'verbose' output, which can sometimes be useful.
 
R

RScotti

Thanks Al,
I just ran the Chkdsk /R and I got errors. Here's what it said:
Is this OK?
Checking file system on C:
The type of the file system is NTFS.
Volume label is HP_PAVILION.

A disk check has been scheduled.
Windows will now check the disk.
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 file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

231833983 KB total disk space.
19706164 KB in 84629 files.
30908 KB in 7168 indexes.
0 KB in bad sectors.
174755 KB in use by the system.
65536 KB occupied by the log file.
211922156 KB available on disk.

4096 bytes in each allocation unit.
57958495 total allocation units on disk.
52980539 allocation units available on disk.

Internal Info:
00 87 01 00 9e 66 01 00 22 05 02 00 00 00 00 00 .....f..".......
95 02 00 00 01 00 00 00 b0 01 00 00 00 00 00 00 ................
24 0b 65 07 00 00 00 00 e6 5b 3e 25 00 00 00 00 $.e......[>%....
56 2f aa 07 00 00 00 00 fa 15 13 d1 01 00 00 00 V/..............
b6 15 dc 3f 09 00 00 00 62 83 36 4c 0b 00 00 00 ...?....b.6L....
30 46 f1 a6 00 00 00 00 a0 39 07 00 95 4a 01 00 0F.......9...J..
00 00 00 00 00 d0 c4 b2 04 00 00 00 00 1c 00 00 ................

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

Yes, the exact same output.

v means 'verbose' output, which can sometimes be useful.

Have a good day,
RScotti

remove "nospam" in order to email me.
 
W

Wesley Vogel

For some reason the Event Viewer doesn't show the winlogon event 1001
info.and there is no file name Bootex.log in the C:\ root directory.

C:\bootex.log gets deleted. Bootex.log can be acessed with recovery
software such as Restoration.

This is a sample of one of my Event ID 1001 Winlogon.

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/4/2004
Time: 8:01:27 AM
User: N/A
Computer: MYPENTIUM450
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
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.

9952235 KB total disk space.
6020596 KB in 40720 files.
15248 KB in 2053 indexes.
0 KB in bad sectors.
102811 KB in use by the system.
51824 KB occupied by the log file.
3813580 KB available on disk.

4096 bytes in each allocation unit.
2488058 total allocation units on disk.
953395 allocation units available on disk.

That is the same exact info as what was in the bootex.log from that time. I
know because I recovered the deleted bootex.log and compared it to the Event
Viewer entry.

Bootex.log is from BootExecute, here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
and whatever autocheck value exists or existed at the time autochk.exe ran.
autocheck autochk /r \??\C: for example.

You can create a chkdsk log.

From: Doug Knox MS-MVP...
This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.
Can you please tell me if when you do the Chkdsk /f do you get three or
four options that it checks 1 File verify something (scan 1 of 4 scans)

You get THREE. The fourth pass is OPTIONAL. "If the /R switch is in
effect, CHKDSK runs a fourth pass to look for bad sectors in the volume's
free space."

Phase 1: Checking files
Phase 2: Checking indexes
Phase 3: Checking security descriptors
Phase 4: Checking sectors

<quote>
Checking an NTFS disk
Windows displays chkdsk status reports for an NTFS disk in the following
format:

The type of the file system is NTFS.
CHKDSK is verifying files...
File verification completed.
CHKDSK is verifying indexes...
Index verification completed.
CHKDSK is verifying security descriptors...
Security descriptor verification completed.
12372 kilobytes total disk space.
3 kilobytes in 1 user files.
2 kilobytes in 1 indexes.
4217 kilobytes in use by the system.
8150 kilobytes available on disk.
512 bytes in each allocation unit.
24745 total allocation units on disk.
16301 allocation units available on disk.
<quote>
from...
Microsoft Windows XP - Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true

Understanding what CHKDSK does
CHKDSK's activity is divided into three major passes, during which CHKDSK
examines all the metadata on the volume, and an optional fourth pass.

Phase 1: Checking files
During its first pass, CHKDSK displays a message that tells you that CHKDSK
is verifying files and also displays the percent of verification that is
completed, counting from 0 to 100 percent. During this phase, CHKDSK
examines each file record segment in the volume's master file table (MFT).

Phase 2: Checking indexes
During its second pass, CHKDSK displays a message that tells you that CHKDSK
is verifying indexes and again displays the percent completed, counting from
0 to 100 percent. During this phase, CHKDSK examines each of the indexes on
the volume.

Phase 3: Checking security descriptors
During its third pass, CHKDSK displays a message that tells you that CHKDSK
is verifying security descriptors and, for the third time, displays "percent
completed," counting from 0 to 100 percent. During this phase, CHKDSK
examines each security descriptor that is associated with files or
directories that are on the volume.

Phase 4: Checking sectors
If the /R switch is in effect, CHKDSK runs a fourth pass to look for bad
sectors in the volume's free space. CHKDSK attempts to read every sector on
the volume to confirm that the sector is usable. Even without the /R switch,
CHKDSK always reads sectors that are associated with metadata. Sectors that
are associated with user data are read during earlier phases of CHKDSK if
the /R switch is specified.
from...
An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
RScotti said:
Hi,
For some reason the Event Viewer doesn't show the winlogon event 1001
info.and there is no file name Bootex.log in the C:\ root directory.
I just did a clean install with the HP Recovery Disks today and still
don't have it.This was one reason I did it the other was to try an get
the Recovery Console didn't get that either.

HP Recovery system SUCKS!

Can you please tell me if when you do the Chkdsk /f do you get three or
four options that it checks 1 File verify something (scan 1 of 4 scans)
2 index verify (scan 2 of 4 scans)
3 security verify (scan 3 of 4 scans)
4 file data verify? (scan 4 of 4 scans)

OR


1 File verify something (scan 1 of 3 scans)
2 index verify (scan 2 of 3 scans)
3 security verify (scan 3 of 3 scans)

I would really like to do the /F instead of doing the /R but don't know
if the /F is working correctly.

Read-only mode is chkdsk with NO switches.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_pwfd.asp

[[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.]]
From...
Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx

[[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. ]]
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

To take advantage of all the Chkdsk parameters, use the command-line
version of Chkdsk.

See..
Understanding what CHKDSK does
here...
An explanation of the new /C and /I Switches that are available to use
with Chkdsk.exe
http://support.microsoft.com/kb/314835

Don't even bother running CHKDSK in read-only mode. It is a waste of
time and prone to not accurately reporting information. CHKDSK might
report spurious errors because it cannot lock the drive.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix
file system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is not available to run other tasks while the disk is being
checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and
attempt recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files must be closed for this program to run. If the drive is currently
in use, a message asks if you want to reschedule the disk checking for
the next time you restart your computer. Your drive is not available to
run other tasks while the disk is being checked. If you select this
option, you do not need to select Automatically fix file system errors.
Windows fixes any errors on the disk.]]

You have to reboot for Error-checking to run.

For a look at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled
it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked. The
Winlogon service then moves the contents of each Bootex.log file to the
Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Have a good day,
RScotti

remove "nospam" in order to email me.
 
R

RScotti

Hi,
When I did a Chkdsk /R it did show up in EV but the /F still doesn't show and only does three options NOT the fourth
(Verifying file data)
C:\bootex.log gets deleted. Bootex.log can be acessed with recovery
software such as Restoration.

This is a sample of one of my Event ID 1001 Winlogon.

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/4/2004
Time: 8:01:27 AM
User: N/A
Computer: MYPENTIUM450
Description:
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
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.

9952235 KB total disk space.
6020596 KB in 40720 files.
15248 KB in 2053 indexes.
0 KB in bad sectors.
102811 KB in use by the system.
51824 KB occupied by the log file.
3813580 KB available on disk.

4096 bytes in each allocation unit.
2488058 total allocation units on disk.
953395 allocation units available on disk.

That is the same exact info as what was in the bootex.log from that time. I
know because I recovered the deleted bootex.log and compared it to the Event
Viewer entry.

Bootex.log is from BootExecute, here...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value Name: BootExecute
and whatever autocheck value exists or existed at the time autochk.exe ran.
autocheck autochk /r \??\C: for example.

You can create a chkdsk log.

From: Doug Knox MS-MVP...
This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.


You get THREE. The fourth pass is OPTIONAL. "If the /R switch is in
effect, CHKDSK runs a fourth pass to look for bad sectors in the volume's
free space."

Phase 1: Checking files
Phase 2: Checking indexes
Phase 3: Checking security descriptors
Phase 4: Checking sectors

<quote>
Checking an NTFS disk
Windows displays chkdsk status reports for an NTFS disk in the following
format:

The type of the file system is NTFS.
CHKDSK is verifying files...
File verification completed.
CHKDSK is verifying indexes...
Index verification completed.
CHKDSK is verifying security descriptors...
Security descriptor verification completed.
12372 kilobytes total disk space.
3 kilobytes in 1 user files.
2 kilobytes in 1 indexes.
4217 kilobytes in use by the system.
8150 kilobytes available on disk.
512 bytes in each allocation unit.
24745 total allocation units on disk.
16301 allocation units available on disk.
<quote>
from...
Microsoft Windows XP - Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true

Understanding what CHKDSK does
CHKDSK's activity is divided into three major passes, during which CHKDSK
examines all the metadata on the volume, and an optional fourth pass.

Phase 1: Checking files
During its first pass, CHKDSK displays a message that tells you that CHKDSK
is verifying files and also displays the percent of verification that is
completed, counting from 0 to 100 percent. During this phase, CHKDSK
examines each file record segment in the volume's master file table (MFT).

Phase 2: Checking indexes
During its second pass, CHKDSK displays a message that tells you that CHKDSK
is verifying indexes and again displays the percent completed, counting from
0 to 100 percent. During this phase, CHKDSK examines each of the indexes on
the volume.

Phase 3: Checking security descriptors
During its third pass, CHKDSK displays a message that tells you that CHKDSK
is verifying security descriptors and, for the third time, displays "percent
completed," counting from 0 to 100 percent. During this phase, CHKDSK
examines each security descriptor that is associated with files or
directories that are on the volume.

Phase 4: Checking sectors
If the /R switch is in effect, CHKDSK runs a fourth pass to look for bad
sectors in the volume's free space. CHKDSK attempts to read every sector on
the volume to confirm that the sector is usable. Even without the /R switch,
CHKDSK always reads sectors that are associated with metadata. Sectors that
are associated with user data are read during earlier phases of CHKDSK if
the /R switch is specified.
from...
An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

Have a good day,
RScotti

remove "nospam" in order to email me.
 
W

Wesley Vogel

but the /F still doesn't show
and only does three options NOT the fourth (Verifying file data)

Correct. /f only does three. "If the /R switch is in effect, CHKDSK runs a
fourth pass to look for bad sectors in the volume's free space."

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
W

Wesley Vogel

There are NO errors in your log.

Reading a chkdsk log

chkdsk log will be similar to this...

Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
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.

4096543 KB total disk space.
2906360 KB in 19901 files.
6344 KB in 1301 indexes.
0 KB in bad sectors.
49379 KB in use by the system.
22544 KB occupied by the log file.
1134460 KB available on disk.

4096 bytes in each allocation unit.
1024135 total allocation units on disk.
283615 allocation units available on disk.

It is housecleaning and housecleaning is going to happen if you run
chkdsk.exe. Think Merry Maids with brooms.
Cleaning up minor inconsistencies on the drive.

[[In the above error message, "minor inconsistencies" refers to a state
where redundant information stored in different places is "out of synch."
This is a natural and expected condition whenever there are open files on
the volume that have undergone modification. The redundant information is
not brought into synchronization until the files are closed. Typically, this
error message occurs when CHKDSK is run against the volume containing
Windows NT system files (including active user profiles and the pagefile).

WORKAROUND
You can usually safely ignore this error message even if the message appears
without there being open files, because it is only the redundant information
that is out of synchronization. The only side effect you may see as a result
of this message is an incorrect reading of free disk space or something
similar. ]]
from...
"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe reports only unused index and security descriptor entries that
were removed. ]]
[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008
Cleaning up 3 unused security descriptors.

[[When you delete a file or folder with permissions that you've set by hand
rather than allowed to be automatically inherited from its parent, the ACL
(Access Control List, the security descriptor) isn't deleted, but cached.
Running CHKDSK against these "dead" items cleans up the ACLs that are no
longer in use and frees up space. ]]
from...
Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

[[This problem occurs because if Chkdsk is run against an NTFS volume,
Chkdsk.exe may report that security descriptors are in the database that are
no longer referenced by any file or folder and that it is removing them.
However, Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

[[4096543 KB total disk space.
(This value is the total formatted disk capacity.)

2906360 KB in 19901 files.
(This value is the space used by user file data.)

6344 KB in 1301 indexes.
(This value is the space used by NTFS indexes.)

0 KB in bad sectors.
(This value is the space lost to bad sectors.)

49379 KB in use by the system.
(This value is includes MFT and other NTFS metafiles.)

22544 KB occupied by the log file.
(This value is the NTFS Log file; you use the chkdsk /l:size to adjust this
value.)

1134460 KB available on disk.
(This value is the available FREE disk space.)

4096 bytes in each allocation unit.
(This value is the cluster size [4K])

1024135 total allocation units on disk.
(This value is the total clusters on disk.)

283615 allocation units available on disk.
(This value is the available free clusters.) ]]
from...
How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

See these for help interpreting the chkdsk log.

"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524

Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
RScotti said:
Thanks Al,
I just ran the Chkdsk /R and I got errors. Here's what it said:
Is this OK?
Checking file system on C:
The type of the file system is NTFS.
Volume label is HP_PAVILION.

A disk check has been scheduled.
Windows will now check the disk.
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 file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

231833983 KB total disk space.
19706164 KB in 84629 files.
30908 KB in 7168 indexes.
0 KB in bad sectors.
174755 KB in use by the system.
65536 KB occupied by the log file.
211922156 KB available on disk.

4096 bytes in each allocation unit.
57958495 total allocation units on disk.
52980539 allocation units available on disk.

Internal Info:
00 87 01 00 9e 66 01 00 22 05 02 00 00 00 00 00 .....f..".......
95 02 00 00 01 00 00 00 b0 01 00 00 00 00 00 00 ................
24 0b 65 07 00 00 00 00 e6 5b 3e 25 00 00 00 00 $.e......[>%....
56 2f aa 07 00 00 00 00 fa 15 13 d1 01 00 00 00 V/..............
b6 15 dc 3f 09 00 00 00 62 83 36 4c 0b 00 00 00 ...?....b.6L....
30 46 f1 a6 00 00 00 00 a0 39 07 00 95 4a 01 00 0F.......9...J..
00 00 00 00 00 d0 c4 b2 04 00 00 00 00 1c 00 00 ................

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


RScotti said:
Hi Al,
On Tue, 23 Jan 2007 00:14:05 -0600, "Al Pilarcik"

chkdsk f: /f/v

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Windows has checked the file system and found no problems.

If you ran this without the /v would you get the same thing?



Yes, the exact same output.

v means 'verbose' output, which can sometimes be useful.

Have a good day,
RScotti

remove "nospam" in order to email me.
 
R

RScotti

Hi Wesley,

NO. If you run Chkdsk /R it does Five passes
Chkdsk is verifying files
Chkdsk is verifying indexes
Chkdsk is verifying security
Chkdsk is verifying file data
Chkdsk is verifying free space

Chkdsk /F should do the first four but it doesn't.

Correct. /f only does three. "If the /R switch is in effect, CHKDSK runs a
fourth pass to look for bad sectors in the volume's free space."

Have a good day,
RScotti

remove "nospam" in order to email me.
 
R

RScotti

Hi Wesley,
Thank you very much. Your information was very helpful.I really appreciate your help and all your effort you have given
me on all these topics.
Thanks again.


There are NO errors in your log.

Reading a chkdsk log

chkdsk log will be similar to this...

Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
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.

4096543 KB total disk space.
2906360 KB in 19901 files.
6344 KB in 1301 indexes.
0 KB in bad sectors.
49379 KB in use by the system.
22544 KB occupied by the log file.
1134460 KB available on disk.

4096 bytes in each allocation unit.
1024135 total allocation units on disk.
283615 allocation units available on disk.

It is housecleaning and housecleaning is going to happen if you run
chkdsk.exe. Think Merry Maids with brooms.
Cleaning up minor inconsistencies on the drive.

[[In the above error message, "minor inconsistencies" refers to a state
where redundant information stored in different places is "out of synch."
This is a natural and expected condition whenever there are open files on
the volume that have undergone modification. The redundant information is
not brought into synchronization until the files are closed. Typically, this
error message occurs when CHKDSK is run against the volume containing
Windows NT system files (including active user profiles and the pagefile).

WORKAROUND
You can usually safely ignore this error message even if the message appears
without there being open files, because it is only the redundant information
that is out of synchronization. The only side effect you may see as a result
of this message is an incorrect reading of free disk space or something
similar. ]]
from...
"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe reports only unused index and security descriptor entries that
were removed. ]]
[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008
Cleaning up 3 unused security descriptors.

[[When you delete a file or folder with permissions that you've set by hand
rather than allowed to be automatically inherited from its parent, the ACL
(Access Control List, the security descriptor) isn't deleted, but cached.
Running CHKDSK against these "dead" items cleans up the ACLs that are no
longer in use and frees up space. ]]
from...
Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

[[This problem occurs because if Chkdsk is run against an NTFS volume,
Chkdsk.exe may report that security descriptors are in the database that are
no longer referenced by any file or folder and that it is removing them.
However, Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem. ]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

[[4096543 KB total disk space.
(This value is the total formatted disk capacity.)

2906360 KB in 19901 files.
(This value is the space used by user file data.)

6344 KB in 1301 indexes.
(This value is the space used by NTFS indexes.)

0 KB in bad sectors.
(This value is the space lost to bad sectors.)

49379 KB in use by the system.
(This value is includes MFT and other NTFS metafiles.)

22544 KB occupied by the log file.
(This value is the NTFS Log file; you use the chkdsk /l:size to adjust this
value.)

1134460 KB available on disk.
(This value is the available FREE disk space.)

4096 bytes in each allocation unit.
(This value is the cluster size [4K])

1024135 total allocation units on disk.
(This value is the total clusters on disk.)

283615 allocation units available on disk.
(This value is the available free clusters.) ]]
from...
How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

See these for help interpreting the chkdsk log.

"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524

Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

Have a good day,
RScotti

remove "nospam" in order to email me.
 
W

Wesley Vogel

Hi RScotti,

You're welcome.

See my reply to yours about Five passes.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
RScotti said:
Hi Wesley,
Thank you very much. Your information was very helpful.I really
appreciate your help and all your effort you have given me on all these
topics.
Thanks again.


There are NO errors in your log.

Reading a chkdsk log

chkdsk log will be similar to this...

Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
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.

4096543 KB total disk space.
2906360 KB in 19901 files.
6344 KB in 1301 indexes.
0 KB in bad sectors.
49379 KB in use by the system.
22544 KB occupied by the log file.
1134460 KB available on disk.

4096 bytes in each allocation unit.
1024135 total allocation units on disk.
283615 allocation units available on disk.

It is housecleaning and housecleaning is going to happen if you run
chkdsk.exe. Think Merry Maids with brooms.
Cleaning up minor inconsistencies on the drive.

[[In the above error message, "minor inconsistencies" refers to a state
where redundant information stored in different places is "out of synch."
This is a natural and expected condition whenever there are open files on
the volume that have undergone modification. The redundant information is
not brought into synchronization until the files are closed. Typically,
this error message occurs when CHKDSK is run against the volume
containing Windows NT system files (including active user profiles and
the pagefile).

WORKAROUND
You can usually safely ignore this error message even if the message
appears without there being open files, because it is only the redundant
information that is out of synchronization. The only side effect you may
see as a result of this message is an incorrect reading of free disk
space or something similar. ]]
from...
"CHKDSK detected minor inconsistencies" error message in Windows 2000
and in Windows NT
http://support.microsoft.com/kb/109524
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe reports only unused index and security descriptor entries
that were removed. ]]
[[Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem.
]]
from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008
Cleaning up 3 unused security descriptors.

[[When you delete a file or folder with permissions that you've set by
hand rather than allowed to be automatically inherited from its parent,
the ACL (Access Control List, the security descriptor) isn't deleted,
but cached. Running CHKDSK against these "dead" items cleans up the ACLs
that are no longer in use and frees up space. ]]
from...
Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

[[This problem occurs because if Chkdsk is run against an NTFS volume,
Chkdsk.exe may report that security descriptors are in the database that
are no longer referenced by any file or folder and that it is removing
them. However, Chkdsk.exe just reclaims the unused security descriptors
as a housekeeping activity, and it does not actually fix any kind of
problem. ]] from...
Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

[[4096543 KB total disk space.
(This value is the total formatted disk capacity.)

2906360 KB in 19901 files.
(This value is the space used by user file data.)

6344 KB in 1301 indexes.
(This value is the space used by NTFS indexes.)

0 KB in bad sectors.
(This value is the space lost to bad sectors.)

49379 KB in use by the system.
(This value is includes MFT and other NTFS metafiles.)

22544 KB occupied by the log file.
(This value is the NTFS Log file; you use the chkdsk /l:size to adjust
this value.)

1134460 KB available on disk.
(This value is the available FREE disk space.)

4096 bytes in each allocation unit.
(This value is the cluster size [4K])

1024135 total allocation units on disk.
(This value is the total clusters on disk.)

283615 allocation units available on disk.
(This value is the available free clusters.) ]]
from...
How to locate and correct disk space problems on NTFS volumes in Windows
XP http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use
with Chkdsk.exe
http://support.microsoft.com/kb/314835

See these for help interpreting the chkdsk log.

"CHKDSK detected minor inconsistencies" error message in Windows 2000
and in Windows NT
http://support.microsoft.com/kb/109524

Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

How to locate and correct disk space problems on NTFS volumes in Windows
XP http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

An explanation of the new /C and /I Switches that are available to use
with Chkdsk.exe
http://support.microsoft.com/kb/314835

Have a good day,
RScotti

remove "nospam" in order to email me.
 
W

Wesley Vogel

Hi RScotti,

There seems to be a difference between STAGE and PHASE and I do not know
what the difference is.

I found it! ;-) You have to use the info from two MS sources, listed
below.

"When you run Chkdsk on NTFS volumes, the Chkdsk process consists of three
major stages, and optional fourth and fifth stages."

Stages 4 and 5 are both part of Phase 4.

Phase 1: Checking files
Stage 1: Chkdsk verifies each file record segment in the master file table
Chkdsk is verifying files

Phase 2: Checking indexes
Stage 2: Chkdsk checks the directories in the volume
Chkdsk is verifying indexes

Phase 3: Checking security descriptors
Stage 3: Chkdsk verifies the security descriptors for each volume
Chkdsk is verifying security

Phase 4: Checking sectors
Stages 4 and 5 (optional stages): Chkdsk reads every sector on the volume to
confirm stability
Chkdsk is verifying file data
Chkdsk is verifying free space


An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

The Chkdsk Process on NTFS Volumes
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_utol.asp

#$%#$% MS changed the link.

Click this link
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx
then do a Ctrl + F for The Chkdsk Process on NTFS Volumes

(Phase One in which Doris gets her oats. Two Of Us by The Beatles)

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
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.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
R

RScotti

Hi Wesley,
Yes that's very helpful.Thanks Again.
Hi RScotti,

There seems to be a difference between STAGE and PHASE and I do not know
what the difference is.

I found it! ;-) You have to use the info from two MS sources, listed
below.

"When you run Chkdsk on NTFS volumes, the Chkdsk process consists of three
major stages, and optional fourth and fifth stages."

Stages 4 and 5 are both part of Phase 4.

Phase 1: Checking files
Stage 1: Chkdsk verifies each file record segment in the master file table
Chkdsk is verifying files

Phase 2: Checking indexes
Stage 2: Chkdsk checks the directories in the volume
Chkdsk is verifying indexes

Phase 3: Checking security descriptors
Stage 3: Chkdsk verifies the security descriptors for each volume
Chkdsk is verifying security

Phase 4: Checking sectors
Stages 4 and 5 (optional stages): Chkdsk reads every sector on the volume to
confirm stability
Chkdsk is verifying file data
Chkdsk is verifying free space


An explanation of the new /C and /I Switches that are available to use with
Chkdsk.exe
http://support.microsoft.com/kb/314835

The Chkdsk Process on NTFS Volumes
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_utol.asp

#$%#$% MS changed the link.

Click this link
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx
then do a Ctrl + F for The Chkdsk Process on NTFS Volumes

(Phase One in which Doris gets her oats. Two Of Us by The Beatles)

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
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.

Have a good day,
RScotti

remove "nospam" in order to email me.
 
W

Wesley Vogel

Keep having fun. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 

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