Windows 10 chkdsk read error and bad sectors found on chkdsk however report displayed: Windows has scanned the file system and found no problems.

  • Thread starter Thread starter questionsformicrosoftproducts
  • Start date Start date
Q

questionsformicrosoftproducts

Guest
On a drive multiple tests were ran in addition to chkdsk /r.

The error or surface scans displayed errors.

The chkdsk /r report displayed:

Stage 4: Looking for bad clusters in user file data ...
Read failure with status 0xc0000483 at offset 0x5573901000 for 0x10000 bytes.
A disk read error occurredc0000483
The disk does not have enough space to replace bad clusters


Windows has scanned the file system and found no problems.
No further action is required.



For a chkdsk /r


a) What determines whether it does or not display that it found no problems?

"Windows has scanned the file system and found no problems."

b) How come the read error was not displayed in the conclusion as a problem?

c) How come the bad clusters were not displayed in the conclusion as a problem?

d) When determining the amount of free space needed to replace bad clusters what comparisons are made by the chkdsk tool?

More...
 
Back
Top