Backups Fail After 20GB
I'm trying to backup a laptop with a 256GB disk in order to replace it with a 1TB disk. Backups to a USB connected NTFS disk fail after 20GB. Backups to another machine's disk via wifi also fails after 20GB.
I have tried formatting the USB disk as NTFS and exFAT. Both fail around 20GB. The message says the backup stopped, sometimes with a file system error. CHKDSK never finds a problem with the file system.I have tried backups as "Entire PC" and "Disks and partitions." Clone disk doesn't work, in the same fashion.
In two days of trying I have yet to get a complete backup of the laptop to anything and we really can't afford to have the laptop fail with no backup. Is there some kind of ~20GB limit I don't know about?
Backups on the desktop machine sail right through to local and remote disks, and even to the cloud.
Thanks for your consideration - K1EA


- Log in to post comments

As Ian has said, the log file for some of these failed backup attempts is the information we need to better understand what the real core issue is?
- Log in to post comments

The system is:
OS Name Microsoft Windows 10 Home
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name JAN-LAPTOP
System Manufacturer Acer
System Model Predator G3-571
System Type x64-based PC
System SKU 0000000000000000
Processor Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 2808 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Insyde Corp. V1.10, 8/22/2017
SMBIOS Version 3.0
Embedded Controller Version 1.10
BIOS Mode UEFI
BaseBoard Manufacturer KBL
BaseBoard Product Sienta_KLS
BaseBoard Version V1.10
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.17763.737"
User Name JAN-LAPTOP\k1ea
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 10.3 GB
Total Virtual Memory 18.3 GB
Available Virtual Memory 11.5 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Attachment | Size |
---|---|
513389-172513.log | 3.77 KB |
513389-172515.log | 3.77 KB |
513389-172518.log | 3.77 KB |
- Log in to post comments

Thanks for the ti_demon log files, these show a potential MS VSS error occuring during the backup operation.
15/09/2019 09:04:52 :273 Can't read slices: Error 0x40011: The specified file does not exist.
15/09/2019 09:07:48 :647 Error 0x1e50023: File system error is found. Consider checking the disk using Check Disk Utility.
| error 0x2160015: A backup error.
| error 0x70003: Read error.
| error 0x10c481: Failed to read the snapshot. See VSS logs for details.
| error 0x100155: CRC error.
15/09/2019 09:07:48 :726 Error 0x13c0005: Operation has completed with errors.
Please download the Acronis VSS Doctor tool (link below) and run this as Administrator then let it fix any VSS issues it finds that it can fix.
- Log in to post comments

- Log in to post comments

I forgot to run it as administrator. Here is the new one.
You guys are amazing -- I hope Acronis appreciates you.
Attachment | Size |
---|---|
513405-172521.txt | 62.4 KB |
- Log in to post comments

The VSS Doctor log confirms that you have a disk error involved here.
See webpage: Fix: Event 7 Disk has a bad block at \Device\Harddisk#\DR#
The log shows lots of the following duplicated entries:
Events: Timestamp: 9/15/2019 9:15:00 AM Type: Error Source: Disk Message: The device, \Device\Harddisk0\DR0, has a bad block. InstanceId: -1073479673 SearchLink: https://www.google.com/#newwindow=1&q=Disk+event+id+3221487623 Timestamp: 9/15/2019 9:14:59 AM Type: Error Source: Disk Message: The device, \Device\Harddisk0\DR0, has a bad block. InstanceId: -1073479673 SearchLink: https://www.google.com/#newwindow=1&q=Disk+event+id+3221487623 Timestamp: 9/15/2019 9:14:58 AM Type: Error Source: Disk Message: The device, \Device\Harddisk0\DR0, has a bad block. InstanceId: -1073479673 SearchLink: https://www.google.com/#newwindow=1&q=Disk+event+id+3221487623
As this is your computer boot drive, you need to follow the steps given in the above webpage to try to see if the bad block on the drive can be reassigned or fixed in some way.
I would also recommend investing in a spare replacement drive in case this is an indicator that the drive is starting to fail.
If you have an earlier disk backup of this drive from before these errors started up, then keep hold of that as a means of recovering your computer back to that point in time, plus make separate backups of any critical data that may have changed since that backup was made (using the Files & Folders backup option).
- Log in to post comments

You are correct. The Intel SSD Toolbox reports a bad block too. Updating the the Intel firmware did not help, so I installed a 2.5" SSD to get as much off it as possible. Ironically, I started this to get a clean backup and swap the boot Intel M.2 with a much larger Samsung M.2.
CHKDSK /R has hung for an hour at 40%. This is error detection by growing old. How long should I wait?
tnx - K1EA
- Log in to post comments

If you are able to wait, then let it keep running to see if it can recover the bad block or get past it.
If it continues to hang at 40% after many hours, then it would look like your luck is out with this drive, so my next question is to ask again if you have an older backup you could recover from?
- Log in to post comments

I want to thank everybody for their help. The bad block on the old ssd was unfixable (by me), so I reinstalled the operating system and applications on the new ssd.
How much time do we spend reinstalling OSs? Way to much...
- Log in to post comments

Glad that you have got the new SSD in and working though sorry that the old drive could not be recovered from the bad block. Thanks for the feedback.
- Log in to post comments