Main Forum > Tweaking.com Support & Help

Chkdsk False Errors

(1/2) > >>

Shane:
When you run chkdsk in read only mode, either from the windows repair program or normally you might get reports that there are errors when there isnt.

This is a know problem with chkdsk. When it checks the drive and it happens to be checking a file that is currently being written to then it will repair an error when there isnt one. If you did a chkdsk and got no errors then you are good to go.

A little ways down this page you will find this
http://technet.microsoft.com/en-us/library/bb457122.aspx


--- Quote ---    Chkdsk might fail in read-only mode or might report false errors.

    The read-only Chkdsk process involves three phases. If Chkdsk encounters errors in the early phases, Chkdsk might abort before it completes all three phases. In addition, Chkdsk is prone to falsely reporting errors when in read-only mode, and it might report that a volume is corrupted even when no corruption is present. For example, Chkdsk might report corruption if NTFS modifies an area of the disk on behalf of a program at the same time Chkdsk is examining the same area. To verify a volume correctly, the volume must be in a static state, and the only way to guarantee that state is to lock the volume. Chkdsk locks the volume only when you specify the /f, /r, or /x parameters. Thus, you might need to run Chkdsk more than once for Chkdsk to complete all stages in read-only mode.
--- End quote ---

So if you have chkdsk run at next boot and it doesnt find any errors then you should be good to go and can ignore the false errors it might have reported.

Shane

makinero:
best parameter is the addition /V (Verbose)
Example:
CHKDSK /V DRIVE:

and

CHKNTFS C: D: Z:
Note:
C, D . . . Z: - partition letter

Very Fast check of each partition, whether the data is disrupted and is required to use the CHKDSK.

makinero:

--- Quote from: Shane on October 27, 2014, 10:14:21 pm ---When you run chkdsk in read only mode, either from the windows repair program or normally you might get reports that there are errors when there isnt.
--- End quote ---

It is caused by corruption important system files.
Should fix it.
 WR 3.9.1 does not detect and does not repair these errors (!)

Raandy:

--- Quote from: makinero on June 07, 2016, 07:03:52 am ---
--- Quote from: Shane on October 27, 2014, 10:14:21 pm ---When you run chkdsk in read only mode, either from the windows repair program or normally you might get reports that there are errors when there isnt.
--- End quote ---

It is caused by this bathmate site for the bathmate x30 and corruption important system files.
Should fix it.
 WR 3.9.1 does not detect and does not repair these errors (!)

--- End quote ---

I thought that id did repair these errors. If it doesn't then what does?

Boggin:
Chkdsk in read-only mode does not repair - it's only a quick gude which may or not report correctly.

You'd be better off running chkdsk as chkdsk /f which repairs files and will report if it finds any bad sectors or use chkdsk /r which will move and repair corrupt data from bad sectors, but cannot repair those sectors - it only prevents data from being written to those sectors in the future.

If a chkdsk /r reports KBs in bad sectors, you may have some leeway in its continued use but the hard drive will eventually fail, sooner rather than later and you should have your whole system backed up in a system image for when it does.

Navigation

[0] Message Index

[#] Next page