|
|
|
re: Question about 'Prevent file corruption problems'
Tuesday, October 22, 2002 at 8:10 am
Windows XP Annoyances Discussion Forum
Posted by Mike
(1 messages posted)
Paul:
I'm amazed that I have not seen more messages like yours on the Web!
For the last several months on both of my machines I have experienced problems similar
to yours with my Windows XP Pro boot drives that are formatted with the NTFS file
system. If you're interested I suggest you read Microsoft Knowledge Base Article
Q315688. I'm not endorsing the article per se, however you may want to note their
brief paragraph toward the end of the article, which is titled "NTFS File System
Corruption". It is indicative of the kind of problems I have experienced running
Chkdsk from the command prompt.
I could go on and on, but I will make only a couple of more points. One, if you call
Microsoft, the techs will probably tell you to load Recovery Console (if you haven't
already; it is not installed by default) in order to correct the Chkdsk reporting
errors. My experience is that as soon as you think you accomplished something with
it (using Chkdsk with the "p" and "r" switches), the problem comes right back. This
is not to suggest that Recovery Console in and of itself is not a good thing. In
fact as I write this I am seriously comtemplating using it to reformat my boot drives
with FAT32.
The last comment I want to make is that I have recently discovered that in excess
of 20% of my boot drive usage (as reported by various disk utilities) cannot be accounted
for (yes, after making adjustments for page and hibernation files). And, in contradistinction
to the KB article referred to above (note the references to "misreporting of disk
space allocation"), my folder/file sizes compared to "size on disk" is relatively
tight. So who knows what's going on?
Thanks for providing an outlet for my frustration. Later,
Mike
On Friday, October 4, 2002 at 10:02 pm, Paul wrote:
>I have a question about Prevent
>file corruption problems:
>
>I have tried running the "new" CHKDSK under Windows XP using both the Error Checking
>tool in "My Computer/File/Properties" and from the command line.
>
>When I used the Error Checking tool (without selecting the Automatic fix of file
>system errors or the scan for bad sectors) XP displayed a dialogue with a sequence
>of messages, telling me that the Error Checker was performing phase 1 of its check,
>then phases 2 and 3 and finally a new dialogue appeared telling me that the check
>had been completed - and nothing more.
>
>When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the
output
>was more informative:
>
>"The type of the file system is NTFS.
>
>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.
>CHKDSK is verifying security descriptors (stage 3 of 3)
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused security descriptors.
>Security descriptor verification completed.
>CHKDSK is verifying Usn Journal...
>Usn Journal verification completed.
>Correcting errors in the Volume Bitmap.
>Windows found problems with the file system.
>Run CHKDSK with the /F (fix) option to correct"
>
>My question is, which should I trust - the Error Checking tool (which I assume invokes
>CHKDSK in the background) or the command line? Or perhaps a third party program?
|
All messages in this thread [show all]
 |  | re: Question about 'Prevent file corruption problems' (Mike: Tue, Oct 22, 2002, 8:10 am) |
|  | | Sins of NTFS (Down For The Count: Thu, Jan 22, 2004, 8:22 pm) |
|  | re: (Tong Narak: Tue, Jan 25, 2005, 6:43 pm) |
| |
| |
