1.    06 Aug 2016 #1
    Join Date : Aug 2016
    Posts : 5
    Windows 10

    What CHKDSK exactly logging and 'flashing' messages on prompt?


    Click image for larger version. 

Name:	chkdsk.png 
Views:	8 
Size:	16.8 KB 
ID:	94630

    This is the screen just before exiting chkdsk. There were bad sectors on the disk. In that case some files, I heard, could be deleted when chkdsk is executed with /r switch, so I turned it off in haste. As you see, chkdsk didn't leave any messages that it deleted or modifed something. Still could there be any files already deleted? When I checked it out after the terminaton no found.xxx folder or chk file was found.

    It is said that there could be losses in the data recorded on the sectors marked as bad in the recovery process using /r switch. What I'd like to know is if there could be any possibility that when the job occurred it proceeded without leaving any job history on the prompt screen.
      My ComputerSystem Spec
  2.    07 Aug 2016 #2
    Join Date : Feb 2016
    Phoenix, AZ
    Posts : 230
    Windows 10 Pro 1703 15063.413

    It doesn't look like Stage 4 completed successfully. If you aborted it before it completed, it wouldn't report any bad sectors.
      My ComputersSystem Spec
  3.    07 Aug 2016 #3
    Join Date : Jun 2015
    Posts : 12,682
    Windows 10 Pro

    Hi VIEN,

    Welcome to the 10forums

    There hasn't been any occasion that chkdsk deleted files in bad sectors with the users I requested to run chkdsk with /r parameter.

    Still could there be any files already deleted? When I checked it out after the terminaton no found.xxx folder or chk file was found.
    Depends on where the bad sector(s) are, you let chkdsk scan 869 sectors from 93936 present in the user data (the part where data is present), if any is present within the 869 then they could've been marked as bad where the data in it would be moved to a different location. If none was present then nothing happened.

    Chkdsk will leave a log in the event viewer when its job is finished, mostly what you'll see in the log is security descriptors been deleted what has nothing to do with personal files being deleted. Only in the log you'll see certain things as 'this and that has been deleted' but nothing will be from personal files.
      My ComputersSystem Spec
  4.    08 Aug 2016 #4
    Join Date : Aug 2016
    Posts : 5
    Windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Depends on where the bad sector(s) are, you let chkdsk scan 869 sectors from 93936 present in the user data (the part where data is present), if any is present within the 869 then they could've been marked as bad where the data in it would be moved to a different location. If none was present then nothing happened.
    Unfortunately log was not created in this time because of abort chkdsk by myself. according to screenshot, chkdsk was checking 869 clusters and did not find any errors yet (judging by prompt, any error messages aren't leaved on prompt), so i assume chkdsk did not touch any data/sectors yet, and i canceled before something can happen with data/sectors by chkdsk. how do you think about this conclusion?
      My ComputerSystem Spec
  5.    08 Aug 2016 #5
    Join Date : Jun 2015
    Posts : 12,682
    Windows 10 Pro

    It is an incorrect conclusion TBH, chkdsk will say if it found a bad sector after a stage is done.
    So, there are 5 stages,
    1. file structure scan,
    2. file name linkage scan,
    3. security descriptors scan,
    4. user data scan,
    5. free space scan

    if in stage 4 a single sector is found then chkdsk will mention that after the scan of stage 4 is finished.

    The conclusion is that it is not known if chkdsk found any bad sectors.
      My ComputersSystem Spec
  6.    08 Aug 2016 #6
    Join Date : Aug 2016
    Posts : 5
    Windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    It is an incorrect conclusion TBH, chkdsk will say if it found a bad sector after a stage is done.



    if in stage 4 a single sector is found then chkdsk will mention that after the scan of stage 4 is finished.

    The conclusion is that it is not known if chkdsk found any bad sectors.
    I just found these messages about stage 4, my conclusion was refer on these messages = if chkdsk found any errors in stage 4, it leaving messages 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.
    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.

    Did you mean that all messages will be mentioned that after the scan of stage 4 is finished? or i understood wrong?
      My ComputerSystem Spec
  7.    08 Aug 2016 #7
    Join Date : Jun 2015
    Posts : 12,682
    Windows 10 Pro

    As I mentioned in my first post in this thread, most messages will be visible in the log after the scan. Stuff as bad sectors are included while the scan is going, but after a stage is finished. I've never seen bad sectors being mentioned while a stage scan is not yet finished.
      My ComputersSystem Spec
  8.    12 Aug 2016 #8
    Join Date : Aug 2016
    Posts : 5
    Windows 10
    Thread Starter

    Does chkdsk already could changed/removed data in "this" situation?


    Click image for larger version. 

Name:	ndisk.png 
Views:	5 
Size:	19.1 KB 
ID:	95794

    This is the last screen just before exiting chkdsk. There were bad sectors on the disk. In that case some corrupted data on bad sectors, I heard, could be changed/removed when chkdsk is executed with /r switch, so I turned it off in haste. As you see, chkdsk didn't leave any messages that it deleted or modifed something. Still could there be any files already changed? When I checked it out after the terminaton no found.xxx folder or chk file was found.

    It is said that there could be losses in the data recorded on the sectors marked as bad in the recovery process using /r switch. What I'd like to know is if there could be any possibility that when the job occurred it proceeded without leaving any job history on the prompt screen.
      My ComputerSystem Spec
  9.    12 Aug 2016 #9
    Join Date : Apr 2015
    Posts : 12,588
    W10Prox64

    You can check the log in Event Viewer to see what was done.
    Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums

    You didn't stop the chkdsk in the middle of the scan did you?
    It's my understanding that if chkdsk /r finds bad sectors it will attempt to move the data to a safe place and then mark those bad sectors off so they're not used again.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Solved CHKDSK freeze
This is not strictly a BSOD. It is a solid freeze. Ctrl-Alt-Del does not break it. I have to power off. It happens when I run this: rem chk.btm rem /F =full chkdsk repair. /R = surface check. /B = reevaluate bad clusters rem Put drives first...
BSOD Crashes and Debugging
Command Prompt Window Keeps Flashing
I have two computers of mine that keep running "system32\schtasks.exe" in a command prompt. It will appear but go away in a fraction of a second; only by capturing the frame at the right time was I able to get a screenshot of it. It launches that...
General Support
Solved Chkdsk issue
Hi, so I recently upgraded to windows 10 from windows 7 and it was working fine for a week. However a few hours ago, the system prompted me to restart to scan disk for errors. I restart, windows does a scan and gets stuck at 59%. I let it run...
Performance & Maintenance
W10 PC hangs on chkdsk
Hi Opens a CMD prompt as admin and ran chkdsk r on the c drive, the drive was busy so it ran on restart. The process was going okay but stopped 0n 12%, it stayed on 12% for 12 hours then I restarted and chkdsk ran and again it stopped on...
Drivers and Hardware
Chkdsk oddity
By chance checked diskpart commands on PS and found warnings regarding both USB drives (one a micro-SD). PS C:\windows\system32> Get-Volume DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining ...
Performance & Maintenance
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:21.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums