Does "Failed to read data from the disk" error message during backup mean that the backup is corrupted?
In particular, I'm trying to resolve an apparent contradiction: my backup has a few of these "failed to read data" errors, but the log also ends with "The following backups have been successfully created." So, was the backup truly, completely successful?
I've already determined that the error results from gradual degradation of one of my Samsung SSDs. S.M.A.R.T says that that drive's "available spares" are being used up at the rate of about 1 every 2 months. I have 90 out of 100 available spares left.
Central question: if I try to restore that Samsung SSD from this backup, will every bit of information be recovered?
Full backup log:
6/6/2020 9:00:00 PM: -----
6/6/2020 9:00:00 PM: ATI Demon started. Version: 24.6.1.25700.
6/6/2020 9:00:00 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
6/6/2020 9:00:00 PM: Operation All disks started by schedule.
6/6/2020 9:00:00 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
6/6/2020 9:00:00 PM: Operation: Backup
6/6/2020 9:00:00 PM: Preparing the media...
6/6/2020 9:00:00 PM: Error 0x4000f: Canceled.
6/6/2020 9:00:00 PM: Create Backup Archive From: Disk 1, Disk 3, Disk 4, Disk 6, Disk 7, Disk 8 To file: N:\BACKUPS\TRUE IMAGE\All disks_inc_b16_s10_v1.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata
6/6/2020 9:00:00 PM: Pending operation 174 started: 'Creating partition image'.
6/6/2020 9:00:30 PM: Writing full version to file: All disks_full_b17_s1_v1.tib
6/6/2020 10:42:46 PM: Pending operation 174 started: 'Creating partition image'.
6/6/2020 10:42:48 PM: Pending operation 174 started: 'Creating partition image'.
6/6/2020 11:06:53 PM: Error 0x101fe: Failed to read data from the disk.
6/6/2020 11:06:53 PM: Failed to read data from the disk.
Failed to read from sector '592,438,396' 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)
CRC error. (0x100155): ⎂Retry/⎂Ignore/Ignore ⎂All/⎂Cancel
6/6/2020 11:11:16 PM: Pending operation 174 started: 'Creating partition image'.
6/6/2020 11:11:20 PM: Pending operation 174 started: 'Creating partition image'.
6/6/2020 11:30:54 PM: Error 0x101fe: Failed to read data from the disk.
6/6/2020 11:30:54 PM: Failed to read data from the disk.
Failed to read from sector '1,250,084,052' 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)
CRC error. (0x100155): ⎂Retry/⎂Ignore/Ignore ⎂All/⎂Cancel
6/6/2020 11:38:51 PM: Pending operation 174 started: 'Creating partition image'.
6/7/2020 12:04:06 AM: The last created Volume Tracker checkpoint for volume 'F:' belongs to another backup plan.
6/7/2020 12:04:06 AM: Error 0x70036: The file system is corrupted. Fast incremental/differential backup is disabled and file filters are not effective.
6/7/2020 12:04:06 AM: Error 0x7002e: Forced sector-by-sector mode.
6/7/2020 12:30:33 AM: Error 0x101fe: Failed to read data from the disk.
6/7/2020 12:30:33 AM: Failed to read data from the disk.
Failed to read from sector '-1,459,184,934' 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)
CRC error. (0x100155): ⎂Retry/⎂Ignore/Ignore ⎂All/⎂Cancel
6/7/2020 12:55:49 AM: Pending operation 174 started: 'Creating partition image'.
6/7/2020 2:07:00 AM: Pending operation 174 started: 'Creating partition image'.
6/7/2020 3:28:35 AM: Pending operation 174 started: 'Creating partition image'.
6/7/2020 4:25:19 AM: Pending operation 174 started: 'Creating partition image'.
6/7/2020 4:33:46 AM: The following backups have been successfully created: N:\BACKUPS\TRUE IMAGE\All disks_full_b17_s1_v1.tib
6/7/2020 4:33:46 AM: Consolidate Backup Archive Location: N:\BACKUPS\TRUE IMAGE\All disks_full_b17_s1_v1.tib Destination: N:\BACKUPS\TRUE IMAGE\All disks_full_b17_s1_v1_B91D57FF-B137-4A2A-BF74-8BEA8596DA7A.tib
6/7/2020 4:33:46 AM: Operation has succeeded.
Start: 6/6/2020 9:00:00 PM
Stop: 6/7/2020 4:33:46 AM
Total Time: 07:33:46


- Anmelden, um Kommentare verfassen zu können

Thanks Steve, I'll proceed based on your input.
- Anmelden, um Kommentare verfassen zu können

How do you find sector e.g. 592,438,396? do you mean, you clone everything except that sector and keep that uncloned sector saved on the side to add to the new cloned drive later?
- Anmelden, um Kommentare verfassen zu können

The error means that the data in the referenced sector cannot be read so thus cannot be saved to a backup or copied by a clone operation.
Accessing such an individual sector would only show you raw data with no indication of what that raw data is or what it belongs to, i.e. a file, program etc?
Bad sectors suggest a failing disk drive.
- Anmelden, um Kommentare verfassen zu können