Need to make sure about chkdsk issue, help

Our "pub" where you can post about things completely Off Topic or about non-silent PC issues.

Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee

Post Reply
FIOL110
Posts: 1
Joined: Thu Aug 04, 2016 1:40 am

Need to make sure about chkdsk issue, help

Post by FIOL110 » Thu Aug 04, 2016 1:46 am

Image

As you can see, i ran chkdsk /r on hard drive which got some bad sectors and this is screenshot for last moment before i stopped chkdsk. i canceled chkdsk after ran some minutes because i heard run chkdsk /r on hard drive with bad sectors can lose data.
So according to this chkdsk prompt window screenshot, was that possible about that data was removed/fixed or anything changed by chkdsk? i am asking about that chkdsk could do something to data even no errors are found on prompt window.

Actually i MS support engineer gave same this answer.

"From the above description I understand that you were able to cancel the chkdsk program within 3%. usually chkdsk command examine all the files and then start the fixes. However in this case you wouldn’t have lost any data."

So, i thought i need verify that answer i got, so i had additional question.

My question was...

"If chkdsk finds error/corrupted/any kind of problem while running, is it strictly + immediately shows messages on prompt window? or possible to miss to show messages on window about what chkdsk did to data?"

And i got this answer from another place.

"When chkdsk finds a bad sector, it momentarily flashes a message like "recovering sector xxxx" while in stage 4. Did you see a message like this? If not, then your data has not been altered."

So on... i think i should make conclusion now.

For that, i just found these messages about stage 4 on chkdsk from somebody's log.

Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 2813
of name $PATH1.MKV.
Windows replaced bad clusters in file 2863
of name $PATH2.MKV.
Windows replaced bad clusters in file 2881
of name $PATH3.MKV.
Windows replaced bad clusters in file 2891
of name $PATH4.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.


I didn't see any kind of reports ↑ while chkdsk is running (as my screenshot exactly showing)
I wonder these messages are messages that he mean "recovering sector xxxx" or he was meaning another kind of messages?

Any messages like these are not written on my chkdsk prompt window but i do not remember some message was 'momentarily flashes' on chkdsk prompt window while chkdsk was running.

----------------------------------------------------------------------------------------------------------------------------------

So plus according to my screenshot, MS support engineer's answer "However in this case you wouldn’t have lost any data." is 100% right?

In other word, Are data clearly untouched and sectors are not remarked by chkdsk in my case(in screenshot)?
You do not have the required permissions to view the files attached to this post.

HFat
Posts: 1753
Joined: Thu Jul 03, 2008 4:27 am
Location: Switzerland

Re: Need to make sure about chkdsk issue, help

Post by HFat » Thu Aug 04, 2016 6:19 am

FIOL110 wrote:So plus according to my screenshot, MS support engineer's answer "However in this case you wouldn’t have lost any data." is 100% right?

In other word, Are data clearly untouched and sectors are not remarked by chkdsk in my case(in screenshot)?
I don't know exactly how chkdsk works but I don't think it matters because chkdsk can not control 100% what's going on (not with typical modern drives anyway). So that MS support person was at best misleading because you can lose data even if chkdisk doesn't try to move data around.
Mind you: I'm not saying it's likely you lost data just by running chkdsk. But you asked about "100%".
If you're afraid of losing data because your drive is failing, don't use chkdsk and more generally do not run anything that might write to the drive. Do not switch it on and off, try many tools on it and so forth. Instead start by figuring out how to image the drive with ddrescue or some such without touching the drive (by using a different system for instance) and only then do you access the drive to image it in one pass (which may take some time if the drive is failing).

If you do confirm you have a bad-but-not-dead drive and it's out of warranty, don't throw it away because such drives are handy for testing failure detection and recovery procedures.

Post Reply