|
|
|
re: Question about 'Prevent file corruption problems'
Monday, September 15, 2003 at 3:04 pm
Windows XP Annoyances Discussion Forum
Posted by James S.
(7 messages posted)
I am having this same type problem. I run chkdsk from the command line prompt and
consistently see the error,
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
--------------
I have this compaq presario, windows xp or prof., brand new pc since 11/02. Just
recently, over the past 4 to 8 weeks, I am not able to correct the problem above.
A couple of the newsgroups from yahoo suggest that the HDD is corrupt. Also, HP/Compaq
say the same, corrupt. I was introduced to the 6 floppy disk set of xp boot disk
setup. Was told to delete the partition and start over. Tried this several times.
No success. Tried several FDISK's, no success. Early this morning, after doing a
disk sanitizer, windows IS able to fix the errors above. AFTER I install most of
the critical updates, I have the errors, again. Have tried both, c.l.i. or the 'c'
drive icon, properties, tools, check now. Neither will fix the errors. I have tried
20 attempts. I have a LOW tolerance if a problem CANNOT fix a problem. Windows did
crash due to a re-boot. I am getting the report, the HDD is not dirty. I will try
the suggestion, format in fat32. If you have any comments, feel free to e-mail me,
js8jim@msn.com Thank you, JIM
=================================
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' (James S.: Mon, Sep 15, 2003, 3:04 pm) |
|  | | Sins of NTFS (Down For The Count: Thu, Jan 22, 2004, 8:22 pm) |
|  | re: (Tong Narak: Tue, Jan 25, 2005, 6:43 pm) |
| |
| |
