Skip to main content

Failed to read data from the disk

Thread needs solution

Using ATI 2018 imaged to a USB stick to backup to an external USB Drive.

My backs start and appears to run ok but eventually I'll get the "Failed to read data from the disk" error messages.

The "retry" option on the error message doesn't appear to do anything. "ignore" or "ignore all" will work and the backup will eventually finish and the backup verification passes.

I've ran chkdsk on both the source and destination drive and it passes ok. The source drive is an SSD.

I don't get any error messages when using another backup program.

Can i trust that acronis true image has backed up the drive successfully?

0 Users found this helpful

Adam, please use the MVP Log Viewer tool to get the full log information for your backup task if you ran this backup from within Windows, as this will give more information about this disk error?

If you performed the backup using the Acronis application booted from USB, then you would need to save the log before exiting from the standalone application as it is lost on restarting / shutting down.

It is possible that CHKDSK would not find disk issues if the issue exists in a hidden partition that is not assigned a drive letter, i.e. System Reserved / EFI partition, Recovery partition...

Adam,

To clarify, when True Image produces such error messages it indicates an issue on one or both of the disks involved.  As Steve says, the error may be on a hidden or unlettered partition or, it may be on the disk you are saving the backup image file to. 

You should run chkdsk on your external USB disk as well as all partitions on the disk you are backing up.

As mentioned on my original post. The destination drive has been chkdsk'ed ok. And the partitions on the source that aren't hidden have also been chkdsk and passed ok.

I'll have to run the backup again to get the logs as im using ATI via bootable USB. So stay tuned for them.

Attached some screenshots in the meantime.

Attachment Size
455174-149655.jpg 819.33 KB
455174-149658.jpg 738.32 KB

Adam, the screen image showing the error message box shows hard disk '1' which in Acronis speak is the first disk drive or Windows disk '0' given the difference in numbering.  This is most probably your source drive and given the very high sector number, 29,795,320 is likely to be towards the end of the drive, so perhaps in a Windows Recovery partition?

If you have opportunity, try selecting the partitions on the source drive one at a time and see which exact one gives the sector error.

I would recommend checking on the drive makers support site for any whole disk diagnostic tools they may provide and using this to check the full drive mechanics and logic.

Hi Steve,

Yes it appears to be the source drive with the issue. However, my original question remains.

Why does the backup verification pass ok despite these disk errors?

Why is acronis finding sector errors while chkdsk and other backup programs don't?

I've attached the logs from the backup i ran yesterday. I will also attempt to run the backup one partition at time and check the drive manufacturers tool (in this case it is a samsung SSD)

Attachment Size
455208-149678.log 3.22 KB

Adam asked:

Why does the backup verification pass ok despite these disk errors?

Verification only looks at the backup image .tib file, not the source drive / data.  In essence all verification does is recalculate the .tib file checksum and compare this to the value embedded with the file - this to confirm the file remains unchanged from how it was originally written to disk.

Why is acronis finding sector errors while chkdsk and other backup programs don't?

What other backup programs are being used, what options chosen, what source data etc?  Sorry but simple answer is 'don't know' other than either the exact same source data is not being selected, or else the other backup program isn't telling you about bad sectors being encountered?

Thanks for the reply Steve.

I've ran the backup selecting one partition at the time and have narrowed the fault down the the c: partition.

The partition has been chkdsk'ed ok so it is still a little confusing that acronis is seeing a problem with it.

I'm in the process now of checking the disk with a disk manufacturers tool and will report back.

I've ran EASUS on the same drive with no errors. Hence my concern with acronis' abilities.

 

Adam, did you try running CHKDSK C: /R on this drive?

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B] [/scan] [/spotfix]

  volume              Specifies the drive letter (followed by a colon),
                      mount point, or volume name.
  filename            FAT/FAT32 only: Specifies the files to check for
                      fragmentation.
  /F                  Fixes errors on the disk.
  /V                  On FAT/FAT32: Displays the full path and name of every
                      file on the disk.
                      On NTFS: Displays cleanup messages if any.
  /R                  Locates bad sectors and recovers readable information
                      (implies /F, when /scan not specified).

The disk manufacturers tool didn't provide anything useful. So I ran the chkdsk /R on all the partitions and guess what!

The backup completed without any errors :)

From what i understand the /R flag will mark any bad sectors as unusable.

I'd previously had just been running chkdsk with /F flags.

Thanks for the help! Onto the next computer now.

Adam, thanks for the update / feedback.  Glad that the CHKDSK /R did the trick for you here!

I've read so much conflicting views on running chkdsk /R on an SSD.

Seems to have resolved my problem in this case.