Hi-
 
I've been struggling with Acronis True Image TS with this issue for a few weeks and thought I'd ask here to see if anyone had any insights while Acronis looks at my log files.
 
My ATI 2016 backups stall with the following error:
 
Failed to read data from the disk.
Failed to read from sector 931,752,544 of hard disk '1'. 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. (Ox1OC45A) Unknown status.
(Ox9) The request could not be performed because of an I/O device error (OxFFFO)
 
I've run chkdsk on all available drives and none report errors.
 
"Hard disk 1" has no drive letter and there's no menu option for it in Windows Disk Management except "Convert to Dynamic Disk" so I haven't found a way to run chkdsk on it, even though it seems to be the culprit if ATI is to be believed.
I've gotten the ATI error trying to backup either Disk 0 or Disk 2 (both are installed hard drives in my laptop,) so I don't understand why it's even looking at Disk 1.
 
I "guess" I should run chkdsk on disk 1, but I haven't been able to assign it a drive letter or basically do anything with it. I know more about mountvol and diskpart than I did before, but that's about it ;)!
 
Any suggestions? My ultimate goal is to clone my Disk 0 drive (which is partitioned for a dual boot system) to a larger drive.
 
Oh, and why do they say "create a backup of the disk" when that's what I was trying to do when it failed?
 
TIA-
 
-Susan
 
Edit: I marked this "Solved" because it wasn't an ATI problem. The disk was actually dying. I was eventually able to restore everything I needed to a new hard drive and I'm back up & running with no apparent ill effects. I'm still confused by ATI's disk numbering scheme and why it suggests backing up the disk when the backup already failed.
 
I'm still getting a refund for True Image 2016 because I absolutely hate the interface, which IMO isn't nearly as intuitive as TI 2013 and it seems to be missing some options from the previous version. I have a dual-boot Win 10 system, and 2013 runs with no issues on one, whereas the other one complains about compatibility with Win 10. I'm going to reinstall 2013 on that system and see what happens. If there are any problems, I'll probably move to Macrium. The way I work, I do need the ability to backup/restore indivual files/folders.

Hi Susan,
 
Hm, that is an odd problem.  My first thought was that TI is somehow confusing the Disk names (ie. Disk 1 instead of Disk 0), but since it's happening with both Disc 0 and Disk 2, that notion seems unlikely.
 
Have you run TI successfully before with the same setup?  Are you launching this from within Windows or on bootable media?
 
It's been awhile since I used TI (I think it was with version 2012), but I've used other software that do the same thing -- so I'm going by a vague familiarity of how these programs usually work.  As you said, it's puzzling why it's even looking at Disk 1 if you're trying to backup Disk 0 or 2.
 
Have you gone through the settings to see if there's something like "Check all my disks before backup" or "Verify sector by sector before/after the backup"?  Clearly, that's what it seems to be doing.   Maybe in the deep recesses ("Advanced"?) there's a box that needs unchecking...
 
BTW, what is on Disk 1?  If you do somehow manage to exclude it from the backup, is that (the fact it may be corrupted) a concern later?

I don't know if I can help, but it sounds to me like the error is occuring during validation of the backup to drive '1'.
 
Sector 931,752,544 is (@ 512 bytes / sector) at byte 477,057,302,528. If that drive is 500 GB in size it may be at the end of the disk. It's not likely that you ran out of disk space because Acronis would test that first.

 
I'm assuming that the backup is from drive 0 to drive 1.
 
The message about chkdsk is that if a drive is going bad and chkdsk fixes the errors you should back it up immediately before it might fail again.
 
I think it is the  target drive - the drive you are backup up onto - that is at fault somehow.
 
I don't know what 'Acronis True Image TS' is - never heard of a TS version.
 
'Failed to read the snapshot' means that the 'snapshot' of the drive (which is probably written last) did not verify or could not be read due to a disk error.
 
Since there was a disk error, the Event Viewer might show more information about the hardware fault.
 
I have had issues with USB connected drives near their physical end sectors - maybe something to do with the USB drivers. But that was with 4 TB drives.
 
I don't know how your backup drive is connected, but maybe you can try a different physical connector (port/slot/hub/whatever).
 
Changing that might also change the disk drive enumeration - so it might not be drive 1 anymore.
 
EDIT: if your drive is formatted at 4K bytes / sector that error location is at byte 3,816,458,420,224 very near the end of a 4 TB drive.
 

Hi Jon-

JonD
Have you run TI successfully before with the same setup? Are you launching this from within Windows or on bootable media?

I ran TI version 2013 with the same disks & laptop, but I believe the last full backup I did was when I was still on a dual-boot Windows 7/Windows 8.1 system before switching to Win 10. This is the first full backup I've tried to do with TI 2016 on a dual-boot Windows 10 system. I'm launching it from within Windows.

Have you gone through the settings to see if there's something like "Check all my disks before backup" or "Verify sector by sector before/after the backup"? Clearly, that's what it seems to be doing. Maybe in the deep recesses ("Advanced"?) there's a box that needs unchecking...

I'll look into that. Thanks for the suggestion.

BTW, what is on Disk 1? If you do somehow manage to exclude it from the backup, is that (the fact it may be corrupted) a concern later?

That's what's weird. I have no idea if any thing's on it and I can't come up with a way to find out. I've included an image of my Disk Management screen in the post below.
 
Thanks!
 
-Susan

Hi Jim-

arachnaut
I don't know if I can help, but it sounds to me like the error is occuring during validation of the backup to drive '1'.

Sector 931,752,544 is (@ 512 bytes / sector) at byte 477,057,302,528. If that drive is 500 GB in size it may be at the end of the disk. It's not likely that you ran out of disk space because Acronis would test that first.

I'm assuming that the backup is from drive 0 to drive 1.

This happens when I try to back up from Disk 0 to Disk 4. I was able at some point to do a full backup of Disk 2 (Drive D), IIRC. Disk 1 shouldn't be involved at all.
 
It sounds like you're saying when Acronis says "hard drive 1," they're not referring to my Disk 1 at all, but rather to the destination drive (assuming the source is hard drive 0.) Am I understanding you correctly?
 
I've run chkdsk on drives C, H, D and L and no errors were reported.

I don't know what 'Acronis True Image TS' is - never heard of a TS version.

Sorry, I just meant Tech Support ;).

Changing that might also change the disk drive enumeration - so it might not be drive 1 anymore.

This makes me think I probably misunderstood what you said before about drive one being the destination drive...

EDIT: if your drive is formatted at 4K bytes / sector that error location is at byte 3,816,458,420,224 very near the end of a 4 TB drive.

The largest drive I have is a 1 TB drive.
 
Here's a screenshot from Disk Management:

 
More background info: I got a Windows error on 1/8/2016 (detected a problem on the hard drive)and the Event Viewer showed a Critical Error 1 (a S.M.A.R.T. fault on my drive 0, the one with volumes H and C.) That's what started me down this path, since I figured I should replace that drive ASAP. I wanted to back up everything first and install a new drive. I can't clone the drive while I'm getting the error from ATI or backup the full drive. That's the one and only time I got that Windows error and as I've said, chkdsk and other diagnostics I've run aren't showing any errors on that drive. I still want to replace it, of course, and I have a new disk ready to go once I can get a good full backup.
 
Thanks so much for your help, guys!
 
-Susan
Edit to add: BTW, that popup is for the disk in question, #1. It has no name and the only option is to delete it.

Susan, the 8GB size of Disk 1 suggests it's the SSD caching part of a hybrid drive (also called SSHD).  If that's correct, I think your next step is determining how/if TI works with a hybrid drive (and if it's possible to bypass it).
 
From what I can tell, the small SSD is used solely for caching, so I would think it's not important as far as TI is concerned (Of course, I could be way off here. I'm basing my theory from about 5 min of googling).
 
If you can verify it is indeed a hybrid drive, then in my mind the next question becomes "Is the SSD portion necessary to clone, and if not, how do I bypass it?"
 
Maybe Acronis TS can answer that question more definitively.

You have a problem - a dual boot system with two operating systems on a single physical drive.
 
Windows 7 and Windows 8 use slightly different structures for parts of the partition table - in particular the dirty bits and stuff used by chkdsk.
 
I ran into an issue with a friend who did this and he kept getting chkdsk errors on Windows 8 because he ran ChkDsk from Windows 7.
 
You should really devote an operating system to a single drive and leave off the other one for its own separate drive.
 
I don't know which OS you are running acronis. You could run from Win 7 and backup 8 or vice versa. 
 
I would recommend booting from the Acronis Rescue DVD and use that to backup the full DISK 0 with all partitions (not a partition backup, but a disk backup). Turn on verification during the backup.
 
That small unformatted drive looks like a flash drive, perhaps used by Readyboost.
 
Maybe you can remove the unnecessary drives and perform the backup. But if the disk has errors I would not back it up with the errors, it may corrupt the backup.
 
To minimize problems going forward I recommend you do this:
 
Boot into Windows 7 and run 'Chkdsk c: /f /r /b'.
Then boot into Windows 8 and run 'Chkdsk h: /f /r /b'.
These are from administrator command prompts. The 'C:' and 'H:' are the boot drives for the respective OSes.
They might be different when you boot from one to another.
 
Do not try to run chkdsk from windows 7 on the windows 8 partition and vice versa. Both chkdsks will modify the drive partition table - it is a shared object - but they will handle it differently so there is risk here of further corruption. 
 
I have a system with 8 physical drives and 14 volumes so if a disk error occurs it is a nightmare to figure out what drive and partition is being mentioned because Windows uses global internal UUIDs for these.
 
To help discover these UUIDS I use the Sysinternal suite file called WinObj.exe:
 
https://technet.microsoft...sinternals/winobj.aspx
 
It looks like this (run as administrator):

 

Hi Jim-
 
Ok, thanks! I've been running dual-boot systems from the same (partitioned) physical drives for years and years with no problems, but I take your point.
 
I can't boot into Win 7 or 8 because both my dual-boot systems have been upgraded to Win 10.
 
Thanks-
 
-Susan

Susan G
Hi Jim-
 
Ok, thanks! I've been running dual-boot systems from the same (partitioned) physical drives for years and years with no problems, but I take your point.
 
I can't boot into Win 7 or 8 because both my dual-boot systems have been upgraded to Win 10.
 
Thanks-
 
-Susan

I think the partition structure changed in Win 8.
 
I had a web reference with details at one time but I can't find it now.
 

To determine if its an Acronis bug or an actual problem, try another backup program and see if that too comes up with an error.  Macrium Reflect has a free version and you can test with that.
 
http://www.macrium.com/reflectfree.aspx
 
I mention Macrium as that is what I use (I used to use Acronis but had problems with it).  There are other free backup programs that could be used for testing too.