Skip to main content

Multiple errors but disk appears OK

Thread needs solution
Beginner
Posts: 2
Comments: 12

I am getting repeated errors that come in pairs:

Error message 1:

============================

E Drive (4T) Sat task is waiting for user interaction.

Description:

Information: Failed to read data from the disk.

Details: Failed to read from sector '29,963,264' of hard disk '2'. Try to repeat the operation. If the error persists, check the disk using Check Disk Utility and create a backup of the disk.

Failed to read the snapshot. See VSS logs for details. (0x10C481) Unknown status. (0x9) A device which does not exist was specified (0xFFF0)

============================

Error message 2:

=============================

2019-07-07T00:06:19:471-05:00 13164 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-07T00:06:19:472-05:00 13164 I00640002: Operation E Drive (4T) Sat started by schedule.

2019-07-07T00:06:22:658-05:00 13164 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-07T00:06:22:660-05:00 13164 I013C0000: Operation: Backup

2019-07-07T00:06:22:661-05:00 13164 I0064000B: Priority changed to High.

2019-07-07T00:06:22:704-05:00 13164 I000B03F0: Create Backup Archive From:     Disk 2 To file:     "V:\i7g7\E drive\E Drive (4T) Sat.tib" Compression:   Normal Exclude:     Files matching mask Match criterion:     hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\eamon\AppData\Local\Temp, C:\Users\eamon\AppData\Local\Microsoft\Windows\INetCache, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\eamon\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC 

2019-07-07T00:06:22:708-05:00 13164 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-07T00:10:02:092-05:00 21948 I00640000: Writing full version to file: E Drive (4T) Sat_full_b68_s1_v1.tib

2019-07-07T00:15:23:856-05:00 13164 E000101FE: Error 0x101fe: Failed to read data from the disk.

| trace level: error

| line: 0x65b5eb7011094665

| file: c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:190

| function: DaProcessor::CommitImpl::OnFdiskErrorCallBack

| line: 0x65b5eb7011094665, c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:190, DaProcessor::CommitImpl::OnFdiskErrorCallBack

| $module: ti_demon_vs_15470

|

| error 0x10c481: Failed to read the snapshot. See VSS logs for details.

| line: 0x3fec04e376b89ee2

| file: c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492

| function: win_snapshot_volume::IoOp

| line: 0x3fec04e376b89ee2, c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492, win_snapshot_volume::IoOp

| $module: ti_demon_vs_15470

|

| error 0x9: Unknown status.

| line: 0x2aacb7b2ab852ac

| file: c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp:40

| function: Fdisk::AddKstatusError

| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError

| code: 0x1b1

| $module: ti_demon_vs_15470

|

| error 0xfff0: A device which does not exist was specified

| line: 0xbd28fdbd64edb8f1

| file: c:\bs_hudson\workspace\723\core\common\error.cpp:307

| function: Common::Error::AddWindowsError

| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\723\core\common\error.cpp:307, Common::Error::AddWindowsError

| code: 0x800701b1

| $module: ti_demon_vs_15470

2019-07-07T00:25:23:997-05:00 13164 E000101F6: Error 0x101f6: Read error

| trace level: error

| line: 0x65b5eb7011094700

| file: c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:345

| function: DaProcessor::CommitImpl::OnDaError

| line: 0x65b5eb7011094700, c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:345, DaProcessor::CommitImpl::OnDaError

| $module: ti_demon_vs_15470

|

| error 0x70003: Read error

| line: 0xdf81da2c74ec5024

| file: c:\bs_hudson\workspace\723\core\resizer\backup\output_stream.cpp:98

| function: `anonymous-namespace'::ReadDrive

| line: 0xdf81da2c74ec5024, c:\bs_hudson\workspace\723\core\resizer\backup\output_stream.cpp:98, `anonymous-namespace'::ReadDrive

| $module: ti_demon_vs_15470

|

| error 0x10c481: Failed to read the snapshot. See VSS logs for details.

| line: 0x3fec04e376b89ee2

| file: c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492

| function: win_snapshot_volume::IoOp

| line: 0x3fec04e376b89ee2, c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492, win_snapshot_volume::IoOp

| $module: ti_demon_vs_15470

|

| error 0x9: Unknown status.

| line: 0x2aacb7b2ab852ac

| file: c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp:40

| function: Fdisk::AddKstatusError

| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError

| code: 0x1b1

| $module: ti_demon_vs_15470

|

| error 0xfff0: A device which does not exist was specified

| line: 0xbd28fdbd64edb8f1

| file: c:\bs_hudson\workspace\723\core\common\error.cpp:307

| function: Common::Error::AddWindowsError

| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\723\core\common\error.cpp:307, Common::Error::AddWindowsError

| code: 0x800701b1

| $module: ti_demon_vs_15470

2019-07-07T00:25:26:189-05:00 13164 E013C0005: Error 0x13c0005: Operation has completed with errors.

| trace level: error

| line: 0x9f2c53c72e8bce5f

| file: c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617

| function: main

| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\723\products\imager\demon\main.cpp:617, main

| $module: ti_demon_vs_15470

===========================

These pairs of error message are given multiple times (with different sector numbers for message 1). These errors only occur when Acronis is set to run on schedule. If I run the backup manually, I don't get any errors at all.

Can someone help me figure this out?

 

0 Users found this helpful
Legend
Posts: 80
Comments: 17159

Doug, any "Failed to read from sector 'xxxxxx' of hard disk 'x'" type errors have always indicated that there is an actual disk issue, where this may be on a hidden or system partition on the drive which does not have a drive letter allocated to allow use of CHKDSK.

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 Toolbox, Kingston SSD Manager

 - Transcend SSDs: Transcend SSD Scope

 - Silicon Power disks: SP ToolBox

 - Toshiba disks: Toshiba PC Diagnostic Tool Utility

- Crucial disks: Crucial Storage Executive

The snapshot issue is directly related to the read error as snapshot data is stored in unused areas of the disk drive when the snapshot is created but has to be read back in order to write that data to the destination backup drive.

I cannot tell you why these errors only show when your backup is run on schedule and not as manual?

Beginner
Posts: 2
Comments: 12

Sorry to take so long to respond to your suggestion. Took a while because after downloading the utility, i found that it hung on the Long Generic test before completing it. I think this may have been because I had my computer set to go to sleep after 30 min, before the test could complete. When I reset the computer sleep to "Never" I ran all 4 tests available  (S.M.A.R.T. test, Short Drive Self Test, Short Generic and Long Generic) and the drive passed all 4. So I am thinking that the reason Acronis failed is because the computer went to sleep, even though it is set to Wake the Computer to do the backup.

Even if that is part of it, it seems odd that the Acronis program would start at all, since it should be "asleep" as well?

I will try to run the backup again with the computer set to not go to sleep and let you know what happens.

 

Beginner
Posts: 2
Comments: 12

After resetting the computer to Sleep Never, the program ran on schedule, but generated the same errors. It also generated errors while trying to back up my SSD c: drive, and then seemed to complete the backup. However, I think the c: drive backup is likely only partial, because it is much smaller than the backup file created when I run it manually (and it completes without errors).

It seems unlikely that both the SSD c: drive and the e: drive would both go bad at the same time, so I wonder if there is a different setting that needs to be changed. 

Here is the c: drive backup log as I received in my email from the program:

==============

2019-07-13T19:05:02:239-05:00 10388 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-13T19:05:02:240-05:00 10388 I00640002: Operation C Drive (OS) Sat started by schedule.

2019-07-13T19:05:21:766-05:00 10388 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-13T19:05:21:769-05:00 10388 I013C0000: Operation: Backup

2019-07-13T19:05:21:770-05:00 10388 I0064000B: Priority changed to High.

2019-07-13T19:05:21:869-05:00 10388 I00180000: Preparing the media...

2019-07-13T19:05:21:870-05:00 10388 E0004000F: Error 0x4000f: Canceled.

| trace level: error

| line: 0x37dcad4ee29f3c8

| file: c:\bs_hudson\workspace\723\builder\lib\fdd_builder.cpp:455

| function: RemovableBuilder::ActivateMedia

| line: 0x37dcad4ee29f3c8,

| c:\bs_hudson\workspace\723\builder\lib\fdd_builder.cpp:455,

| RemovableBuilder::ActivateMedia

| $module: ti_demon_vs_15470

2019-07-13T19:05:21:872-05:00 10388 I000B03F0: Create Backup Archive From:     Disk 3 To file:     "V:\i7g7\C drive\C Drive (OS) Sat.tib" Compression:   Normal Exclude:     Files matching mask Match criterion:     hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\eamon\AppData\Local\Temp, C:\Users\eamon\AppData\Local\Microsoft\Windows\INetCache, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\eamon\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC 

2019-07-13T19:05:21:882-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:05:22:207-05:00 33052 I00640000: Writing full version to file: C Drive (OS) Sat_full_b71_s1_v1.tib

2019-07-13T19:05:22:457-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:14:07:362-05:00 10388 E000101FE: Error 0x101fe: Failed to read data from the disk.

| trace level: error

| line: 0x65b5eb7011094665

| file: c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:190

| function: DaProcessor::CommitImpl::OnFdiskErrorCallBack

| line: 0x65b5eb7011094665,

| c:\bs_hudson\workspace\723\processor\diskadm\da_commit.cpp:190,

| DaProcessor::CommitImpl::OnFdiskErrorCallBack

| $module: ti_demon_vs_15470

|

| error 0x10c481: Failed to read the snapshot. See VSS logs for details.

| line: 0x3fec04e376b89ee2

| file: c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492

| function: win_snapshot_volume::IoOp

| line: 0x3fec04e376b89ee2,

| c:\bs_hudson\workspace\723\core\fdisk\win_snapshot.cpp:492,

| win_snapshot_volume::IoOp

| $module: ti_demon_vs_15470

|

| error 0x9: Unknown status.

| line: 0x2aacb7b2ab852ac

| file:

| c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp

| :40

| function: Fdisk::AddKstatusError

| line: 0x2aacb7b2ab852ac,

| c:\bs_hudson\workspace\723\core\fdisk\ver2\arch\windows\win_errors.cpp

| :40, Fdisk::AddKstatusError

| code: 0x15

| $module: ti_demon_vs_15470

|

| error 0xfff0: The device is not ready

| line: 0xbd28fdbd64edb8f1

| file: c:\bs_hudson\workspace\723\core\common\error.cpp:307

| function: Common::Error::AddWindowsError

| line: 0xbd28fdbd64edb8f1,

| c:\bs_hudson\workspace\723\core\common\error.cpp:307,

| Common::Error::AddWindowsError

| code: 0x80070015

| $module: ti_demon_vs_15470

2019-07-13T19:14:07:362-05:00 10388 E000101FE: Failed to read data from the disk.

Failed to read from sector '230,610,432' of hard disk '3'. Try to repeat the operation. If the error persists, check the disk using Check Disk Utility and create a backup of the disk.

Failed to read the snapshot. See VSS logs for details. (0x10C481) Unknown status. (0x9) The device is not ready (0xFFF0): Retry/Ignore/Ignore All/Cancel

2019-07-13T19:17:03:921-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:17:06:645-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:18:28:847-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:18:32:704-05:00 10388 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-13T19:18:32:708-05:00 10388 I000B0000: Deleting backup file with path V:\i7g7\C drive\C Drive (OS) Sat_full_b70_s1_v1.tib.

2019-07-13T19:18:32:737-05:00 10388 I00640000: The following backups have been successfully created: "V:\i7g7\C drive\C Drive (OS) Sat_full_b71_s1_v1.tib"

2019-07-13T19:18:32:794-05:00 10388 I013C0006: Operation has succeeded.

====================

The errors generated by the e: drive backup are the same as before.

Thanks for any help or suggestions.

d

 

Legend
Posts: 80
Comments: 17159

Doug, how many drives do you have in this computer?

The log above is still saying the same error:

Failed to read from sector '230,610,432' of hard disk '3'.

Open Windows Disk Management and look at how it shows your drives.

I would expect you to see Disk 0, 1 & 2 where 0 should be your OS SSD.

Acronis numbers disks starting from 1, so disk 3 = Windows disk 2 - which is the disk with the bad sector.

When making a backup, the Microsoft VSS snapshot service can use space on other drives to store the snapshot, hence backing up disk 0 can encounter errors reading snapshot data from drive 2!

Beginner
Posts: 2
Comments: 12

Steve,

Disk Management shows

Disk 0: Data_2T(D:)

Disk 1: Data_4T (E:)

Disk 2: several partitions, including OS (C:). 

I ran the backup manually on c: and e: again this morning and got the following results:

================

2019-07-14T05:23:20:583-05:00 23252 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-14T05:23:20:583-05:00 23252 I00640002: Operation C Drive (OS) Sat started manually.

2019-07-14T05:23:23:003-05:00 23252 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-14T05:23:23:005-05:00 23252 I013C0000: Operation: Backup

2019-07-14T05:23:23:006-05:00 23252 I0064000B: Priority changed to High.

2019-07-14T05:23:23:049-05:00 23252 I00180000: Preparing the media...

2019-07-14T05:23:23:049-05:00 23252 E0004000F: Error 0x4000f: Canceled.

| trace level: error

| line: 0x37dcad4ee29f3c8

| file: c:\bs_hudson\workspace\723\builder\lib\fdd_builder.cpp:455

| function: RemovableBuilder::ActivateMedia

| line: 0x37dcad4ee29f3c8, c:\bs_hudson\workspace\723\builder\lib\fdd_builder.cpp:455, RemovableBuilder::ActivateMedia

| $module: ti_demon_vs_15470

2019-07-14T05:23:23:049-05:00 23252 I000B03F0: Create Backup Archive From:     Disk 3 To file:     "V:\i7g7\C drive\C Drive (OS) Sat.tib" Compression:   Normal Exclude:     Files matching mask Match criterion:     hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\eamon\AppData\Local\Temp, C:\Users\eamon\AppData\Local\Microsoft\Windows\INetCache, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\eamon\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC 

2019-07-14T05:23:23:064-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:23:23:282-05:00 18964 I00640000: Writing full version to file: C Drive (OS) Sat_full_b72_s1_v1.tib

2019-07-14T05:23:23:563-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:34:58:353-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:35:00:926-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:36:21:756-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:36:25:503-05:00 23252 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:36:25:519-05:00 23252 I000B0000: Deleting backup file with path V:\i7g7\C drive\C Drive (OS) Sat_full_b71_s1_v1.tib.

2019-07-14T05:36:25:550-05:00 23252 I00640000: The following backups have been successfully created: "V:\i7g7\C drive\C Drive (OS) Sat_full_b72_s1_v1.tib"

2019-07-14T05:36:25:597-05:00 23252 I013C0006: Operation has succeeded.

==============

The .tib files appears normal size (115 GB) this time.

===============

2019-07-14T05:36:28:765-05:00 18004 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-14T05:36:28:765-05:00 18004 I00640002: Operation E Drive (4T) Sat started manually.

2019-07-14T05:36:31:571-05:00 18004 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;

2019-07-14T05:36:31:571-05:00 18004 I013C0000: Operation: Backup

2019-07-14T05:36:31:571-05:00 18004 I0064000B: Priority changed to High.

2019-07-14T05:36:31:618-05:00 18004 I000B03F0: Create Backup Archive From:     Disk 2 To file:     "V:\i7g7\E drive\E Drive (4T) Sat.tib" Compression:   Normal Exclude:     Files matching mask Match criterion:     hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\eamon\AppData\Local\Temp, C:\Users\eamon\AppData\Local\Microsoft\Windows\INetCache, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\eamon\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\eamon\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\eamon\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC 

2019-07-14T05:36:31:634-05:00 18004 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T05:38:03:345-05:00 17952 I00640000: Writing full version to file: E Drive (4T) Sat_full_b69_s1_v1.tib

2019-07-14T09:07:41:873-05:00 18004 I000101F8: Pending operation 173 started: 'Creating partition image'.

2019-07-14T09:07:41:920-05:00 18004 I000B0000: Deleting backup file with path V:\i7g7\E drive\E Drive (4T) Sat_full_b68_s1_v1.tib.

2019-07-14T09:07:42:015-05:00 18004 I00640000: The following backups have been successfully created: "V:\i7g7\E drive\E Drive (4T) Sat_full_b69_s1_v1.tib"

2019-07-14T09:07:42:061-05:00 18004 I013C0006: Operation has succeeded.

======================

I think these are good backups. In any case it did not show errors related to failure to read the drive or problems with snapshot. 

I have no idea what the c: drive error "2019-07-14T05:23:23:049-05:00 23252 E0004000F: Error 0x4000f: Canceled." means but it seems to have recovered from it. 

Of course, I'd like to get this back to just backing up unattended on schedule, as it did for some time. It is possible that these errors started showing up after I updated Windows 10 to version 1903, but I'm not at all sure of this.

 

 

Legend
Posts: 80
Comments: 17159

Doug, the error during your C-Drive backup occurs before the actual disk backup starts!

2019-07-14T05:23:23:049-05:00 23252 I00180000: Preparing the media...

2019-07-14T05:23:23:049-05:00 23252 E0004000F: Error 0x4000f: Canceled.

| trace level: error

| line: 0x37dcad4ee29f3c8

| file: c:\bs_hudson\workspace\723\builder\lib\fdd_builder.cpp:455

| function: RemovableBuilder::ActivateMedia

This looks to be directly connected to Advanced Options for your ATI 2018 task for Removable Media that you have set but which are not valid unless you have a FAT32 flash drive connected to be used for the same, hence why this option is cancelled.

The previous: Failed to read from sector '230,610,432' of hard disk '3'. error is for an issue on your Windows Disk 2 that you say has several partitions including your OS C: drive.

Beginner
Posts: 2
Comments: 12

Steve,

I'm not sure what I need to do to fix the problem. When I backup manually, I don't get the sector error, and running the Seagate check disk tools didn't find any errors.

I'm trying to backup to a usb hd. So do I need to uncheck the box "Place Acronis True Image (64 bit) on the media"? 

Also, I seem to remember asking Acronis to make the backup bootable, but I can't see now where that option is. 

Thanks for all of your help. Hope I can get this fixed.

Doug

Legend
Posts: 80
Comments: 17159

I'm trying to backup to a usb hd. So do I need to uncheck the box "Place Acronis True Image (64 bit) on the media"? 

Yes.  This option is really a throw back to days when users mainly backed up to CD or DVD media. You should create separate Acronis Rescue Media on a USB stick ideally using the Rescue Media Builder tool.

I would recommend creating the Windows PE version of the Acronis Rescue Media as described in the KB documents below. 

KB 60820: Acronis True Image 2018: how to create bootable media

KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works

I'm not sure what I need to do to fix the problem. When I backup manually, I don't get the sector error, and running the Seagate check disk tools didn't find any errors.

It certainly is strange that this sector error is not given when you run a manual backup but comes up when the same backup is scheduled.  I can only guess that different areas of the disk are being used when the backup task is being run as scheduled due to the different system account that is being used, but I would still expect the sector to be found by the Seagate Seatools diagnostics!

Beginner
Posts: 2
Comments: 12

Thanks! I unchecked the "Place Acronis True Image on the Media" option and will let it run on schedule on Tuesday night and let you know if that helps. I'll also make a new bootable DVD. 

doug