varying CHKDSK results


I

Irv Spalten

This is on WinXP Pro SP 2.

Today I ran CHKDSK on my Raid 0 Array for the first time in a very long
time from the disk properties on re-boot. Many many Invalid Security
Descriptors were found and replaced with default values. OK, didn't seem
to do any harm. That was early this afternoon.

Now I decided to run CHKDSK from a command prompt without the /F to see
if it was OK.

3 successive runs produced these results

Run 1
=====================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry McAfee.com Update Check (IRVS-Irv Spalten).job in
index $I3
0 of file 9927.
Deleting index entry MCAFEE~2.JOB in index $I30 of file 9927.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
====================

Run 2 immediately after the one above

==========================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
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.

488215349 KB total disk space.
56985160 KB in 196022 files.
72932 KB in 13541 indexes.
0 KB in bad sectors.
294561 KB in use by the system.
65536 KB occupied by the log file.
430862696 KB available on disk.

4096 bytes in each allocation unit.
122053837 total allocation units on disk.
107715674 allocation units available on disk.
============================

Security descriptors now OK? Found other problems that it didn't test in
Run 1 howere.

Now run 3

=======================================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry RE5E60~1.CTB in index $I30 of file 42810.
Deleting index entry Results.{44AD86D5-FCE2-4E88-B293-4C023EF2667B}.ctb
in index
$I30 of file 42810.
Deleting index entry ThumbnailCache.dat.fgi in index $I30 of file 42816.
Deleting index entry ThumbnailCacheInfo.fgi in index $I30 of file 42816.
Deleting index entry THUMBN~1.FGI in index $I30 of file 42816.
Deleting index entry THUMBN~2.FGI in index $I30 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.pel in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.idx in
index $I3
0 of file 42816.
Deleting index entry {44AD8~1 in index $I30 of file 42816.
Deleting index entry {44AD8~1.DAT in index $I30 of file 42816.
Deleting index entry {44AD8~1.FGI in index $I30 of file 42816.
Deleting index entry {44AD8~1.IDX in index $I30 of file 42816.
Deleting index entry {44AD8~1.PEL in index $I30 of file 42816.
Deleting index entry {44AD8~2.FGI in index $I30 of file 42816.
Deleting index entry lofihandheld[1].css in index $I30 of file 105541.
Deleting index entry LOFIHA~1.CSS in index $I30 of file 105541.
Deleting index entry lofiprint[1].css in index $I30 of file 105541.
Deleting index entry LOFIPR~1.CSS in index $I30 of file 105541.
Deleting index entry lofiscreen[1].css in index $I30 of file 105541.
Deleting index entry LOFISC~1.CSS in index $I30 of file 105541.
Deleting index entry t832[1].htm in index $I30 of file 105541.
Deleting index entry T832_1~1.HTM in index $I30 of file 105541.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

=======================

More index errors? What gives?

Ideas or suggestions?

Thanks,
Irv Spalten
 
Ad

Advertisements

D

Dave Patrick

I'd download and run the manufacturer's diagnostic utilities. (disk and
drive controller)

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Irv Spalten said:
This is on WinXP Pro SP 2.

Today I ran CHKDSK on my Raid 0 Array for the first time in a very long
time from the disk properties on re-boot. Many many Invalid Security
Descriptors were found and replaced with default values. OK, didn't seem
to do any harm. That was early this afternoon.

Now I decided to run CHKDSK from a command prompt without the /F to see if
it was OK.

3 successive runs produced these results

Run 1
=====================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry McAfee.com Update Check (IRVS-Irv Spalten).job in
index $I3
0 of file 9927.
Deleting index entry MCAFEE~2.JOB in index $I30 of file 9927.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
====================

Run 2 immediately after the one above

==========================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
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.

488215349 KB total disk space.
56985160 KB in 196022 files.
72932 KB in 13541 indexes.
0 KB in bad sectors.
294561 KB in use by the system.
65536 KB occupied by the log file.
430862696 KB available on disk.

4096 bytes in each allocation unit.
122053837 total allocation units on disk.
107715674 allocation units available on disk.
============================

Security descriptors now OK? Found other problems that it didn't test in
Run 1 howere.

Now run 3

=======================================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry RE5E60~1.CTB in index $I30 of file 42810.
Deleting index entry Results.{44AD86D5-FCE2-4E88-B293-4C023EF2667B}.ctb in
index
$I30 of file 42810.
Deleting index entry ThumbnailCache.dat.fgi in index $I30 of file 42816.
Deleting index entry ThumbnailCacheInfo.fgi in index $I30 of file 42816.
Deleting index entry THUMBN~1.FGI in index $I30 of file 42816.
Deleting index entry THUMBN~2.FGI in index $I30 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.pel in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.idx in
index $I3
0 of file 42816.
Deleting index entry {44AD8~1 in index $I30 of file 42816.
Deleting index entry {44AD8~1.DAT in index $I30 of file 42816.
Deleting index entry {44AD8~1.FGI in index $I30 of file 42816.
Deleting index entry {44AD8~1.IDX in index $I30 of file 42816.
Deleting index entry {44AD8~1.PEL in index $I30 of file 42816.
Deleting index entry {44AD8~2.FGI in index $I30 of file 42816.
Deleting index entry lofihandheld[1].css in index $I30 of file 105541.
Deleting index entry LOFIHA~1.CSS in index $I30 of file 105541.
Deleting index entry lofiprint[1].css in index $I30 of file 105541.
Deleting index entry LOFIPR~1.CSS in index $I30 of file 105541.
Deleting index entry lofiscreen[1].css in index $I30 of file 105541.
Deleting index entry LOFISC~1.CSS in index $I30 of file 105541.
Deleting index entry t832[1].htm in index $I30 of file 105541.
Deleting index entry T832_1~1.HTM in index $I30 of file 105541.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

=======================

More index errors? What gives?

Ideas or suggestions?

Thanks,
Irv Spalten
 
I

Irv Spalten

Dave Patrick said the following On 1/8/2007 10:13 PM:
I'd download and run the manufacturer's diagnostic utilities. (disk and
drive controller)
Dave, these are twin Western Digital WD25000JB drives in a RAID 0
configuration. I've tried the WD Diags for the drive and it seems they
don't support RAID configurations, only discrete drives...

Also, I rebooted and my varying results went away. I'm left with this
problem only,

Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.

If I run CHKDSK /F and allow CHKDSK to run on boot, it find nothing
wrong. However, running CHKDSK from a command prompt always gives the
above error.

I've seen other people with the same problem in searching the web. It
could be a WinXP NTFS problem?

Irv
 
R

Rock

This is on WinXP Pro SP 2.

Today I ran CHKDSK on my Raid 0 Array for the first time in a very long
time from the disk properties on re-boot. Many many Invalid Security
Descriptors were found and replaced with default values. OK, didn't seem
to do any harm. That was early this afternoon.

Now I decided to run CHKDSK from a command prompt without the /F to see if
it was OK.

3 successive runs produced these results

Run 1
=====================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry McAfee.com Update Check (IRVS-Irv Spalten).job in
index $I3
0 of file 9927.
Deleting index entry MCAFEE~2.JOB in index $I30 of file 9927.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
====================

Run 2 immediately after the one above

==========================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
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.

488215349 KB total disk space.
56985160 KB in 196022 files.
72932 KB in 13541 indexes.
0 KB in bad sectors.
294561 KB in use by the system.
65536 KB occupied by the log file.
430862696 KB available on disk.

4096 bytes in each allocation unit.
122053837 total allocation units on disk.
107715674 allocation units available on disk.
============================

Security descriptors now OK? Found other problems that it didn't test in
Run 1 howere.

Now run 3

=======================================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry RE5E60~1.CTB in index $I30 of file 42810.
Deleting index entry Results.{44AD86D5-FCE2-4E88-B293-4C023EF2667B}.ctb in
index
$I30 of file 42810.
Deleting index entry ThumbnailCache.dat.fgi in index $I30 of file 42816.
Deleting index entry ThumbnailCacheInfo.fgi in index $I30 of file 42816.
Deleting index entry THUMBN~1.FGI in index $I30 of file 42816.
Deleting index entry THUMBN~2.FGI in index $I30 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.pel in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.idx in
index $I3
0 of file 42816.
Deleting index entry {44AD8~1 in index $I30 of file 42816.
Deleting index entry {44AD8~1.DAT in index $I30 of file 42816.
Deleting index entry {44AD8~1.FGI in index $I30 of file 42816.
Deleting index entry {44AD8~1.IDX in index $I30 of file 42816.
Deleting index entry {44AD8~1.PEL in index $I30 of file 42816.
Deleting index entry {44AD8~2.FGI in index $I30 of file 42816.
Deleting index entry lofihandheld[1].css in index $I30 of file 105541.
Deleting index entry LOFIHA~1.CSS in index $I30 of file 105541.
Deleting index entry lofiprint[1].css in index $I30 of file 105541.
Deleting index entry LOFIPR~1.CSS in index $I30 of file 105541.
Deleting index entry lofiscreen[1].css in index $I30 of file 105541.
Deleting index entry LOFISC~1.CSS in index $I30 of file 105541.
Deleting index entry t832[1].htm in index $I30 of file 105541.
Deleting index entry T832_1~1.HTM in index $I30 of file 105541.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

=======================

More index errors? What gives?

You should not give credence to these "errors" that show up when running
chkdsk without /F from within windows. If running a chkdsk /F which will
only happen for the boot volume after a restart, doesn't show any problems
then don't worry about it. Chkdsk when run from within windows is
unreliable as an indicator of problems.
 
W

Wesley Vogel

Now I decided to run CHKDSK from a command prompt without the /F to see
if it was OK.

Using chkdsk with no switches is the same as running in read-only mode.

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.

[[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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Irv Spalten said:
This is on WinXP Pro SP 2.

Today I ran CHKDSK on my Raid 0 Array for the first time in a very long
time from the disk properties on re-boot. Many many Invalid Security
Descriptors were found and replaced with default values. OK, didn't seem
to do any harm. That was early this afternoon.

Now I decided to run CHKDSK from a command prompt without the /F to see
if it was OK.

3 successive runs produced these results

Run 1
=====================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry McAfee.com Update Check (IRVS-Irv Spalten).job in
index $I3
0 of file 9927.
Deleting index entry MCAFEE~2.JOB in index $I30 of file 9927.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
====================

Run 2 immediately after the one above

==========================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
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.

488215349 KB total disk space.
56985160 KB in 196022 files.
72932 KB in 13541 indexes.
0 KB in bad sectors.
294561 KB in use by the system.
65536 KB occupied by the log file.
430862696 KB available on disk.

4096 bytes in each allocation unit.
122053837 total allocation units on disk.
107715674 allocation units available on disk.
============================

Security descriptors now OK? Found other problems that it didn't test in
Run 1 howere.

Now run 3

=======================================
c:\>chkdsk
The type of the file system is NTFS.
Volume label is Drive_C_SATA.

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)...
Deleting index entry RE5E60~1.CTB in index $I30 of file 42810.
Deleting index entry Results.{44AD86D5-FCE2-4E88-B293-4C023EF2667B}.ctb
in index
$I30 of file 42810.
Deleting index entry ThumbnailCache.dat.fgi in index $I30 of file 42816.
Deleting index entry ThumbnailCacheInfo.fgi in index $I30 of file 42816.
Deleting index entry THUMBN~1.FGI in index $I30 of file 42816.
Deleting index entry THUMBN~2.FGI in index $I30 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.dat.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}.pel in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info in index
$I30 of
file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.fgi in
index $I3
0 of file 42816.
Deleting index entry {44AD86D5-FCE2-4E88-B293-4C023EF2667B}Info.idx in
index $I3
0 of file 42816.
Deleting index entry {44AD8~1 in index $I30 of file 42816.
Deleting index entry {44AD8~1.DAT in index $I30 of file 42816.
Deleting index entry {44AD8~1.FGI in index $I30 of file 42816.
Deleting index entry {44AD8~1.IDX in index $I30 of file 42816.
Deleting index entry {44AD8~1.PEL in index $I30 of file 42816.
Deleting index entry {44AD8~2.FGI in index $I30 of file 42816.
Deleting index entry lofihandheld[1].css in index $I30 of file 105541.
Deleting index entry LOFIHA~1.CSS in index $I30 of file 105541.
Deleting index entry lofiprint[1].css in index $I30 of file 105541.
Deleting index entry LOFIPR~1.CSS in index $I30 of file 105541.
Deleting index entry lofiscreen[1].css in index $I30 of file 105541.
Deleting index entry LOFISC~1.CSS in index $I30 of file 105541.
Deleting index entry t832[1].htm in index $I30 of file 105541.
Deleting index entry T832_1~1.HTM in index $I30 of file 105541.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

=======================

More index errors? What gives?

Ideas or suggestions?

Thanks,
Irv Spalten
 
I

Irv Spalten

Wesley Vogel said the following On 1/9/2007 4:10 PM:
Now I decided to run CHKDSK from a command prompt without the /F to see
if it was OK.

Using chkdsk with no switches is the same as running in read-only mode.

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.

[[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

Wes, thanks for the info and pointers. I had looked at some of those
same pages and dismissed them, as I didn't fully read the little bits
you pointed out.

Running under boot-up shows no errors. Good enough for me, thanks again.

Irv
 
Ad

Advertisements

D

Dave Patrick

After backup you can run
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows XP
CD-Rom. At the "Welcome to Setup" screen. Press F10 or R to repair a Windows
XP installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Ad

Advertisements

W

Wesley Vogel

Hi Irv,
Wes, thanks for the info and pointers. I had looked at some of those
same pages and dismissed them, as I didn't fully read the little bits
you pointed out.

It just goes to show you, there's always something.
Running under boot-up shows no errors. Good enough for me, thanks again.

Glad to hear it. Keep having fun.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Irv Spalten said:
Wesley Vogel said the following On 1/9/2007 4:10 PM:
Now I decided to run CHKDSK from a command prompt without the /F to see
if it was OK.

Using chkdsk with no switches is the same as running in read-only mode.

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.

[[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


Irv
 

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