First off... I'm glad I finally found this thread after 10 days of reinstalling windows 
2000 on 3 different systems at least 3 times each. I was getting ready to throw all 
the hardware against the wall!

Anyways, I've been experiencing very similar circumstances involving the chkdsk utility 
of win2k. Running chkdsk on the bootable drive thru the windows desktop almost always 
concludes in some kind of "file system" problem but, according to this thread it's 
because some files are open or running off this partition/drive. However, running 
chkdsk via windows desktop on data partitions/drives would sometimes end up with 
the same "file system" problems also.
My problems started when I redid my system after installing a used motherboard. I 
had 2 hard drives attached to the board. Drive 1 had 2 partitions. Partition 1 was 
the boot drive, and partition 2 was the data drive. After reformatting both partitions 
of drive 1, I powered down and attached drive 2 as a slave. Drive 2 held all my saved 
data from my previous setup and other computer (drivers, files, programs, mp3's, 
divx movies, etc.). My plan was to copy all the saved files from drive 2 and create 
a duplicate set on partition 2 of drive 1. I attempted this by right-clicking the 
mouse and using "copy" & "paste" on directories I wanted to duplicate. The directories 
varied in size but could get as large as 40gigs for one directory. During the process 
some directories & files were corrupted and subsequently lost. This got me started 
on a chkdsk frenzy. I'd run chkdsk just to run chkdsk and found that I had these 
weird file system errors on one or all drives. If one partition or drive checked 
out ok/good one time, the next day it would check out bad with a file system error. 
"What's up with that?" I've been talking to people & searching the net and this thread 
is probably one of the best informational support groups on this problem.

For the people with boot problems: a friend of mine said he experienced similar boot 
problems and his internet research resulted in information regarding using NTFS on 
hard drives which had previous installations of windows98se & FAT32 installed. Apparently, 
a NTFS installation will somehow detect the remnants of a fat32 boot sector resulting 
in the system not booting.  Does this sound right? Is this possible? He then suggested 
to only use NTFS on brand new hard drives with no prior fat32 installations. He's 
followed this strategy and it's worked out for him. Unfortunately for me, I can't 
afford to buy a new hard drive every time I want to change an OS.
I mentioned this situation to another friend that works in I.T. and he suggested 
using a utility that supposedly will totally wipe a drive clean called "kill fdisk" 
or something. At the place he works, he has dealt with FAT32 hard drives that were 
changed or converted to NTFS over time and, thus far they have suffered none of the 
problems mentioned in this thread.
(NOTE: my drives had previous FAT32 installations before changing over to win2k & 
NTFS...coincidence?)

In regards to my problem, I just found this article: Microsoft Knowledge Base Article 
- 327009 (This article was previously published under Q327009)
Here's the link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;327009
I'm hoping this is helpful to anyone as well as me. It involves similar messages/problems 
I'm receiving so I've posted it for people. It mentions something about transferring 
a large number of files which result in security descriptor errors & file system 
corruption that chkdsk will find. These are supposedly minor index problems that 
arise when the original files have certain security features enabled by a user and 
these files get copied or transferred over to another drive. For some reason when 
the files get moved over to another system, those security features that were enabled 
via the prior computer system, are by default not enabled on the new computer they 
were transplanted to. Subsequently, this results in these errors. Does this make 
sense to anyone? Hopefully someone can shed some more light on the subject. I'm only 
posting here so that people can build on this info and provide more insight. I really 
don't want to go back to FAT32.

Hope This Helps Someone,

Ed







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?