Chkdsk finds errors

[Ed H]

Running CHKDSK in XP, get error message:

'Correcting errors in the volume bitmap, '

'Correcting errors in the master file table's bitmap attribute windows. '

'Found problems with the file system, run chkdsk with /f option'

So I schedule a chkdsk, reboot and my mouse will freeze sometimes, so I
reboot and my mouse is fine. Run chkdsk, sometimes the errors are gone,
sometimes they are not, but they come back after some computin' ??? The gud
error checking tool runs with no problem.

Newsgroup suggests that I download a utility by my HD manufacturer but I
don't know who that is.

 

[Guest]

You dont need any utilities,xp has them already.Try installing xp cd,
exit the info page,restart computer,boot to xp cd,recovery,press enter
for password,at cmd screen type:CHKDSK C: /R When its thru,type:
EXIT remove xp cd and let xp restart.Back on desktop,run defrag.

 

[Ed H]

NTFS File System Corruption
In very rare circumstances, the NTFS Metafiles $MFT or $BITMAP may become
corrupted and result in lost disk space. This issue can be identified and
fixed by running a chkdsk /F against the volume in question. Toward the end
of chkdsk, you receive the following message if the $BITMAP needs to be
adjusted:
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

Found this in MSKBA # Q303079

 

[Ed H]

Found this too:

Thank you for contacting Microsoft Online Support Service.

As I understand, the issue is: You received the following error report when
performing Chkdsk.exe tool on your Windows XP:

"Security descriptor verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these."

If I have misunderstood your concerns please let me know.

According to my research, I have included the following information for your
reference:

This problem occurs because when 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 is not actually fixing any kind of problem.

Microsoft has confirmed that this is a problem in Windows. Fortunately, this
error message is an informational message, and can be safely ignored.

All NTFS volumes contain a security descriptor database. This database is
populated with security identifiers that represent unique permission
settings applied to files and folders. When files or folders have unique
NTFS permissions applied, NTFS stores a unique security descriptor once on
the volume, and also stores a pointer to the security descriptor on any file
or folder that references it.

If files or folders no longer use that unique security descriptor, NTFS does
not remove the unique security descriptor from the database, but instead,
keeps it cached. Like any caching strategy, you want to keep the cached
information as long as possible because it may be used again.

To determine if more serious problems exist before scheduling or running
Chkdsk.exe with the /f switch, run the "chkntfs :" (without
the quotation marks) command, where is the drive letter of the drive you
want to run the "chkdsk /f" (without the quotation marks) command against.
If this command reports that the "dirty bit" is set, there may be real
damage that needs to be fixed.

I hope the information helps. If anything is unclear, feel free to let me
know.
***********************************************************

Sounds promising!

 

[Richard Urban]

Andrew, the manufacturers of the hard drives (every manufacturer) have
utility programs that are used to check their respective hard drives for
physical and logical defects. If you use one of these utilities, and it
shows a defect, you will be able to get a replacement drive without any
problem what-so-ever (assuming it is still under warranty).

There is no Window utility that does as thorough or complete testing
procedure.

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard