Windows Server 2012 R2 Essentials complaining about one of your drives? How to queue up multiple chkdsk operations for the next reboot.

Posted by Paul Braren on Dec 3 2014 (updated on Dec 22 2014) in
  • HomeServer
  • HowTo
  • Storage
  • Windows
  • Backup-was-unsuccessful-Cannot-read-the-information-on-a-drive-that-you-want-to-back-up

    I recently noticed my Windows 8.1 laptop wasn't getting backed up daily. You will still want to be sure you aren't low on disk storage to help prevent this issue from cropping up again. But if you're in a pinch, and just want to get your daily backups going again before you've had the time to reduce the bloat on your drives, here's a suggested workaround, seen in the video below.

    The view pictured above is from launching
    on my Windows 8.1 client PC that's backed up daily, then clicking 'View details'.

    Alternatively, you can get there from the WS2012R2 Dashboard, click on 'Devices' tab, double-click on the system having backup issues, 'Backup Properties', 'Backup status', 'View details'.

    Here's the error:

    Backup was unsuccessful on xx/xx/xxxx x:xx:xx AM
    To resolve this issue, go to the computer that you want to back up, and make sure that the hard drive is not low on storage space. To detect and fix drive errors, run Chkdsk.exe

    Given the warning doesn't specify which drive is to blame, this workaround procedure queues up multiple CHKDSK operations for the next reboot on all your drives, to resume those daily backups, and to restore your peace of mind.

    Here's the workaround:

    • right-click on Start (Windows 8/2012 or later)
    • select Command Prompt (Admin)
    • CHKDSK C: /F (when prompted for next reboot, Y (for Yes), only for the C: drive)
    • CHKDSK D: /F (when prompted forcing dismount), N (for No), when prompted for next reboot, Y (for Yes)
    • repeat for each local drive you have in your system
    • reboot
    • launch C:\Windows\System32\Essentials\BackupLaunchpad.exe to kick off a backup, verifying that it completes

    Here's the fix:

    • Clean up some storage, ensuring none of your local disk drives are >90% full.
    • Perform entire workaround procedure above

    In my case, I have a 73% full 1TB SSD C: drive and a 93% full 1TB D: drive, and the reboot took about 15 minutes, so manually do a reboot at a convenient time for you, so your daily backups can be resumed.


    See also

    Windows Server 2012 R2 Essentials says backup failed due to insufficient storage available, the fix may be chkdsk by Paul Braren on Nov 13 2014