Screenshot Verification failure: chkdsk

Screenshots fail to an image of the chkdsk screen.

Environment

  • Datto ALTO
  • Datto SIRIS

Cause

The machine being backed up has a chkdsk scheduled on the next boot.

Resolution

  1. Open an elevated Windows command prompt. To do so, type "CMD" into the Windows search bar, then right-click the command prompt icon and select Run as administrator.

  2. In the Windows command prompt, check if a scheduled chkdsk is pending on the agent system (and automatic file checking is scheduled).

    chkntfs <drive letter>:

    EXAMPLE  chkntfs C:

    The output may be similar to the example message below:

    The type of the file system is NTFS. Chkdsk has been scheduled manually to run on next reboot on volume C:

  3. To check explicitly for the status of the dirty bit on the volume, run the following (also requires administrative privileges):

    fsutil dirty query <drive letter>:

    EXAMPLE  fsutil dirty query C:

    This checks a given volume and returns an output indicating if the volume has its dirty bit set. If so, the output will be output similar to the output below :

    Volume - C: is Dirty

  4. Reboot the agent system to run the chkdsk unset the dirty bit on the volume. If there is no dirty bit and a check disk is not scheduled, proceed to Step 5.

    A check disk can also be performed with the following command, but will also require a reboot.

    chkdsk /f /r <drive letter>:

    EXAMPLE  chkdsk /f /r C:

  5. Force a new backup from the Protect page of the Remote Web. If the new backup still shows a chkdsk on startup, you may need to take a differential merge as the next backup.

Additional resources