locked
chkdsk /r - Running offline RRS feed

  • Question

  • Microsoft Windows 10 Pro (64-bit)
    Version: 1903, OS Build: 10.0.18362
    UEFI BIOS
    GPT NTFS 6TB Disks

    Goal: I want to run ALL the chkdsk stages (i.e. stage 1, stage 2, etc.) entirely offline for my system partition C:, and data partition D:

    In Windows 10, I open cmd using Run as administrator.
    The following commands run some of the stages online and the remaining stages offline.

    "chkdsk c:  /r"
    "chkdsk d:  /r"

    "chkdsk c:  /r /offlinescanandfix"
    "chkdsk d:  /r /offlinescanandfix"

    What is the proper set of parameter to make everything (stage 1, stage 2, etc.) occur offline?
    And to not have it ask the [Y/N] question?

    By-the-way, it is unclear what "/offlinescanandfix" by itself does.
    See chkdsk command.

    Is it doing "/f"?

    "chkdsk c:  /offlinescanandfix"
    "chkdsk d:  /offlinescanandfix"

    Thanks in advance.


    Saturday, November 30, 2019 8:16 PM

Answers

  • 1) There are different switches for chkdsk.

    2) They can be quick, superficial, long, deep, online, offline, etc.

    3) R includes F

    4) B includes R and F

    3) If you want the deepest and most comprehensive fix, and recovery (takes the longest time) then run:

    chkdsk /b /v

    .

    .

    4) Open administrative command prompt and type or copy and paste: 
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax:  chkdsk /r /v C: or chkdsk /r /v D:  changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    5) Use the information in this link to find the chkdsk report in the event viewer.  Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials 
    https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

    6) When chkdsk is run from command prompt it may rise to a low number in the teens and remain there until it completes.

    7) If chkdsk is ran using Windows RE it more likely will display ETA.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    • Marked as answer by petrula Sunday, December 1, 2019 1:59 AM
    Saturday, November 30, 2019 8:53 PM
  • 1) Please boot to a windows 10 iso

    2) Open the Windows advanced troubleshooting menu on the iso

    3) Click command prompt

    4) This should open a black box with title bar:  Administrator:X:\windows\system32\cmd.exe and prompt:  X:\Sources:>

    5) Type:  bcdedit | find "osdevice"

    View the partition drive letter.

    6) Type:  chkdsk /b /v W:

    Change the drive letter W: to the drive letter displayed in the earlier command result.

    In Windows RE the Windows drive letter may change from C: to D: or remain the same

    .

    .

    This link explains the different switches.

    https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk

    .

    .

    Run the command in the evening.

    In most cases a 750 GB drive takes approximately 4 - 7 hours depending upon the problems found and the amount of used and free space.  Larger drives can take substantially longer.

    .

    .

    The chkdsk results should be available in the event viewer searching for chkdsk and wininit.  See the prior post link.


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    Sunday, December 1, 2019 1:21 AM

All replies

  • 1) There are different switches for chkdsk.

    2) They can be quick, superficial, long, deep, online, offline, etc.

    3) R includes F

    4) B includes R and F

    3) If you want the deepest and most comprehensive fix, and recovery (takes the longest time) then run:

    chkdsk /b /v

    .

    .

    4) Open administrative command prompt and type or copy and paste: 
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax:  chkdsk /r /v C: or chkdsk /r /v D:  changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    5) Use the information in this link to find the chkdsk report in the event viewer.  Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials 
    https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

    6) When chkdsk is run from command prompt it may rise to a low number in the teens and remain there until it completes.

    7) If chkdsk is ran using Windows RE it more likely will display ETA.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    • Marked as answer by petrula Sunday, December 1, 2019 1:59 AM
    Saturday, November 30, 2019 8:53 PM
  • Thank you for the quick and detailed reply.

    You mentioned "chkdsk /b /v"
    I am reading the following thread to understand the implications of using "/b".
    What does the "chkdsk /b" argument do? [overclock]
    There are a number of ramifications using it.

    When Windows reboots into the offline for doing the chkdsk, is Windows loading a WinRE like image into RAM, or is Windows booted into the C: drive when it makes "/r" repairs. If the latter case, it would seem that it would be better to run the "chkdsk /b /v" command in WinRE since WinRE runs entirely in RAM.

    What is your opinion?

    If I do run "chkdsk /b /v" command in WinRE, where does WinRE put the event log (i.e. the path)?
    I assume it places it on the WinRE flash drive.

    Thank you for your help.



    • Edited by petrula Saturday, November 30, 2019 11:48 PM
    Saturday, November 30, 2019 11:46 PM
  • 1) Please boot to a windows 10 iso

    2) Open the Windows advanced troubleshooting menu on the iso

    3) Click command prompt

    4) This should open a black box with title bar:  Administrator:X:\windows\system32\cmd.exe and prompt:  X:\Sources:>

    5) Type:  bcdedit | find "osdevice"

    View the partition drive letter.

    6) Type:  chkdsk /b /v W:

    Change the drive letter W: to the drive letter displayed in the earlier command result.

    In Windows RE the Windows drive letter may change from C: to D: or remain the same

    .

    .

    This link explains the different switches.

    https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk

    .

    .

    Run the command in the evening.

    In most cases a 750 GB drive takes approximately 4 - 7 hours depending upon the problems found and the amount of used and free space.  Larger drives can take substantially longer.

    .

    .

    The chkdsk results should be available in the event viewer searching for chkdsk and wininit.  See the prior post link.


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    Sunday, December 1, 2019 1:21 AM
  • 1st R.click on cmd/run as Administrator,in cmd type: CHKDSK C: /F agree to restart.To run other HDs,simply type it in instead of C:

    Running CHKDSK C: /R  is not worth the extra time,R repair can take 2-3 hrs to run.Off Line isn't a default setting as CHKDSK takes place in MS-DOS,which is not even running the Windows OS.

    Sunday, December 1, 2019 5:54 AM