1

I ran chkdsk /r on drive with some bad sectors, and I manually aborted chkdsk at stage 4. I took this screenshot just before exiting chkdsk.

interrupted CHKDSK

1 ~ 3 stages are passed with no error messages and stage 4 only showed "looking for bad clusters in user file data..." nothing more, I aborted chkdsk at this point as shown in the screenshot.

So, at stage 4, since no messages were recorded on prompt yet, that means stage 4 didn't do anything to data (clusters) yet.

Am I correct?

Improve this question
4
  • I am sorry, it was just my mistake. i wanna show it.
    – Seiya Souji
    Commented Aug 16, 2016 at 3:06
  • @galacticninja, the duplicate isn't currently deleted.
    – fixer1234
    Commented Aug 30, 2016 at 16:35
  • @galacticninja - Besides the author has asked the same question several times, across multiple users, instead of just improving a single question. But that fact is irrelevant. The duplicate question still exists though.
    – Ramhound
    Commented Aug 30, 2016 at 18:28
  • @fixer1234 and Ramhound: My bad. I must have mistaken the question marked as original for another question.
    – galacticninja
    Commented Aug 31, 2016 at 10:06

1 Answer 1

Reset to default
1

CHKDSK does not make any changes to the disk until the scanning is complete, and any changes made to the disk are specifically stated by CHKDSK after the scan is complete.

To stay on the safe side, you should rerun CHKDSK (to completion this time) as soon as possible to make sure there is nothing corrupted on the disk, and to not aggravate any corruption present in the disk.

From TechNet:

Interrupting chkdsk is not recommended. However, canceling or interrupting chkdsk should not leave the volume any more corrupt than it was before chkdsk was run. Rerunning chkdsk checks and repairs any remaining corruption on the volume.

Improve this answer
12
  • Really? Chkdsk doesn't correct issues, and then proceed to make changes from the already-(partially-)repaired partition? That's very interesting to know; makes Chkdsk seem safer (and more memory intensive). Do you know of an official resource that documents this?
    – TOOGAM
    Commented Aug 16, 2016 at 2:58
  • 1
    I confirmed chkdsk on stage 4 report errors or what kind of job is happening at "real time" like this. Stage 4: Looking for bad clusters in user file data ... Windows replaced bad clusters in file 2813 of name $PATH1.MKV. or Stage 4: Looking for bad clusters in user file data ... Read failure with status 0xc0000185 at offset 0xb2b4000 for 0x10000 bytes. A disk read error occurredc0000185 The disk does not have enough space to replace bad clusters detected in file 73702 of name \PROGRA~1\WI7DB9~1\MIE81F~1.0_X\MRT100~1.DLL.
    – Seiya Souji
    Commented Aug 16, 2016 at 3:02
  • Those messages are happening while chkdsk is running, i have not seen those messages, think i aborted it before that can happen, chkdsk doesn't detect errors yet in this case. i got this answer from MS support engineer and other experts. are they wrong?
    – Seiya Souji
    Commented Aug 16, 2016 at 3:04
  • This kind of reliable behavior is a trace of the old DOS days. I am not sure what the exact reason for this is, though.
    – oldmud0
    Commented Aug 16, 2016 at 3:10
  • oldmud0, a caveat about the TechNet citation. If you cancel chkdsk and exit gracefully, that's what the citation refers to. If you terminate the process without exiting gracefully ("pulling the plug" on it), my understanding is that you can get corruption. I don't believe the point about chkdsk saving changes until scanning is complete is correct. My understanding is that it does the cleanup as it goes (and reports it as it goes). So besides leaving stuff it didn't get to yet, terminating it externally could leave a specific repair procedure in a state it isn't intended to be left in.
    – fixer1234
    Commented Aug 16, 2016 at 3:23

Not the answer you're looking for? Browse other questions tagged .