Skip to main content

Acronis True Image 2018 has yet to create a backup after several attempts. "Failed to read disk"

Thread needs solution

I have run chkdsk and found no errors with the drive.

Error details follow:

2017-11-06T23:36:40:376-05:00 16880 I00640000: Writing full version to file: ToshibaQosmioMonday_full_b1_s1_v1.tib

2017-11-06T23:37:08:702-05:00 12464 I000101F8: Pending operation 173 started: 'Creating partition image'.

2017-11-06T23:37:11:382-05:00 12464 D000101FA: Locking partition C:...

2017-11-06T23:37:11:382-05:00 12464 D00100000: Volume Tracker session manager created successfully.

2017-11-06T23:37:11:382-05:00 12464 D00100000: Volume Tracker session (volume name = 'C:', session name = '\Device\HarddiskVolume2') opened successfully.

2017-11-06T23:37:11:382-05:00 12464 D00100000: Volume Tracker checkpoint (name = 'B712735D-AA12-4C3E-921C-C4E61AB7B299', freeze on lock = '1') for volume 'C:' created successfully.

2017-11-07T08:29:48:138-05:00 15104 D00080000: AcronisLRPCConnect::BEGIN

2017-11-07T08:33:16:884-05:00 15104 D00080000: ServerLRPC::_CloseConnection id=4

2017-11-07T15:30:09:705-05:00 12464 E000101FE: Error 0x101fe: Failed to read data from the disk.

| trace level: error
| line: 0x65b5eb7011094665
| file: k:\70\processor\diskadm\da_commit.cpp:190
| function: DaProcessor::CommitImpl::OnFdiskErrorCallBack
| line: 0x65b5eb7011094665, k:\70\processor\diskadm\da_commit.cpp:190, DaProcessor::CommitImpl::OnFdiskErrorCallBack
| $module: ti_demon_vs_9850
|
| error 0x10c481: Failed to read the snapshot. See VSS logs for details.
| line: 0x3fec04e376b89ee2
| file: k:\70\core\fdisk\win_snapshot.cpp:492
| function: win_snapshot_volume::IoOp
| line: 0x3fec04e376b89ee2, k:\70\core\fdisk\win_snapshot.cpp:492, win_snapshot_volume::IoOp
| $module: ti_demon_vs_9850
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: k:\70\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, k:\70\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x45d
| $module: ti_demon_vs_9850
|
| error 0xfff0: The request could not be performed because of an I/O device error
| line: 0xbd28fdbd64edb8f1
| file: k:\70\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, k:\70\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x8007045d
| $module: ti_demon_vs_9850
2017-11-07T15:40:09:738-05:00 12464 E000101F6: Error 0x101f6: Read error
| trace level: error
| line: 0x65b5eb7011094700
| file: k:\70\processor\diskadm\da_commit.cpp:345
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094700, k:\70\processor\diskadm\da_commit.cpp:345, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_9850
|
| error 0x70003: Read error
| line: 0xdf81da2c74ec5024
| file: k:\70\core\resizer\backup\output_stream.cpp:98
| function: `anonymous-namespace'::ReadDrive
| line: 0xdf81da2c74ec5024, k:\70\core\resizer\backup\output_stream.cpp:98, `anonymous-namespace'::ReadDrive
| $module: ti_demon_vs_9850
|
| error 0x10c481: Failed to read the snapshot. See VSS logs for details.
| line: 0x3fec04e376b89ee2
| file: k:\70\core\fdisk\win_snapshot.cpp:492
| function: win_snapshot_volume::IoOp
| line: 0x3fec04e376b89ee2, k:\70\core\fdisk\win_snapshot.cpp:492, win_snapshot_volume::IoOp
| $module: ti_demon_vs_9850
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: k:\70\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, k:\70\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x45d
| $module: ti_demon_vs_9850
|
| error 0xfff0: The request could not be performed because of an I/O device error
| line: 0xbd28fdbd64edb8f1
| file: k:\70\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, k:\70\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x8007045d
| $module: ti_demon_vs_9850
2017-11-07T15:40:14:188-05:00 10712 D00080000: ServerLRPC::_CloseConnection id=1
2017-11-07T15:40:14:188-05:00 15336 D00080000: ServerLRPC::_CloseConnection id=1
2017-11-07T15:40:14:188-05:00 10712 D00080000: ServerLRPC::_CloseConnection id=2
2017-11-07T15:40:14:198-05:00 10712 D00080000: ServerLRPC::_CloseConnection id=3
2017-11-07T15:40:14:198-05:00 17024 D00080000: ServerLRPC::_CloseConnection id=2
2017-11-07T15:40:14:198-05:00 13348 D00080000: ServerLRPC::_CloseConnection id=3
2017-11-07T15:40:14:248-05:00 12464 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcdf9
| file: k:\70\products\imager\demon\main.cpp:515
| function: main
| line: 0x9f2c53c72e8bcdf9, k:\70\products\imager\demon\main.cpp:515, main
| $module: ti_demon_vs_9850
2017-11-07T15:40:14:248-05:00 14468 D00000000: WaitChangesEx returned not null
2017-11-07T15:40:14:248-05:00 14468 D00000000: Scheduler event handler is completed
2017-11-07T15:40:14:248-05:00 12464 D00000000: Scheduler event handler succesefully destroyed

0 Users found this helpful

Hello Roger Courtney ,

Seems like you have an issue either with VSS or with the disk.

You could check with VSS doctor, it shows VSS errors and suggests how to fix them: https://www.acronis.com/en-us/personal/vss-diagnostic-free-tool/

 

Roger, just to clarify some points here:

CHKDSK will only check partitions that have assigned drive letters.  You should use /R to check for any bad sectors on such partitions.

The error in your log: Failed to read the snapshot. shows that the error may be in a different area of your partition or potentially a different partition that may not have a drive letter assigned, so would not be touched by CHKDSK.

You should start by using the free Acronis VSS Doctor as advised by Renata, but I would also recommend checking with your drive manufacturers web site for any drive diagnostic tools they may have available, i.e. Seagate have SeaTools, WD have LifeGuard etc  - these tools should offer a way to check the whole drive regardless of partitions and drive letter assignment, this may involve using boot media to do so.

See KB 59873: Acronis True Image 2017: recovering Windows from a boot failure and scroll down to the section on Troubleshooting where you will see a list of links to different diagnostic tools from various disk makers.

2) Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:

 - Western Digital drives: Data Lifeguard Diagnostic for Windows

 - Seagate disks: SeaTools for Windows

 - HGST disks: HGST Windows Drive Fitness Test (WinDFT)

 - Intel SSDs: Intel Solid State Drive Toolbox

 - Samsung drives: Samsung Magician

 - ADATA drives: ADATA SSD ToolBox

 - Kingston SSDs: Kingston SSD ToolboxKingston SSD Manager

 - Transcend SSDs: Transcend SSD Scope

 - Silicon Power disks: SP ToolBox

 - Toshiba disks: Toshiba PC Diagnostic Tool Utility

Thanks for the replies!

VSS Doctor found no problems.

The drive is a Crucial SSD, and their utilitiy found no problems.

I am only backing up the C: drive (eliminating the blind recovery partition as an issue) and still get the same error.

Roger, take a look at KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview and try changing your backup task to not using Microsoft VSS per the directions given. This will take the snapshot aspect of this issue out of the picture. The KB still applies to 2018.

Roger, sorry to hear that the problem is ongoing.  Can you post a copy of the latest log file (you can attach as a .log file).

Also, do you have any other drives in this computer, and if so, are you able to do a full backup of a different drive without seeing any errors posted?

Success!!!

I removed the drive and used another computer to run CHKDSK on it.  Apparently the "schedule this volume to be checked the next time the system restarts?" wasn't doing the trick.  1 bad cluster was replaced.

Thank you all for your help!

Roger

Roger, glad to hear the good news, thanks for taking time to give feedback.

One other way of doing an offline CHKDSK is to boot from the WinPE Rescue Media or from a Windows 10 Install disc, where you can get a command prompt window.