Failed to read from sector ‘356.983.728’ of hard disk 1. Failed to read the snapshot. (0x100155)
Hello,
I'm getting the following error message when I attempt a backup.
Failed to read data from the disk.
Failed to read from sector ‘356.983.728’ of hard disk 1. Failed to read the snapshot. (0x100155)
I've never had this problem before. Any suggestions?
Thanks
Toshiba, Win7 (64bit).


- Log in to post comments

Thank you. I'll give this a try when I can let it do nothing but run the chkdsk command. I saw this for similar but different problems and a fix for something like this for an 2009 program that involved doing some basic computer programing for lack of a better term. I hope to avoid that.
Type this "CHKDSK X: /R" ?
Thanks again.
- Log in to post comments

Yes, remember to replace X: with the right partition letter :-)
- Log in to post comments

Its highly likely you may have a drive that is failing. If Pat L.'s suggestion does not cure the problem then you may want to download and run the manufacturers utilities to test your drive. I just replaced a two year old Western Digital drive with the same error message. WD replaced it for free because the drive was still under warranty.
- Log in to post comments

I rand CHKDSK and I think it said it move a couple of sectors, but Acronis is still giving an error message.
I can "ignore all" but I don't think I'm getting a full backup, and if a restore is needed who knows if it will restore all the data necessary. And, I wonder if all subsequent backups that re dependent will fully work. I validated a backup where I "ignored" the errors and it seemed OK, but not sure it will have all my data if needed.
Any further advice?
Thanks
- Log in to post comments

DAG,
ATI can be set to ignore bad sectors, but I wouldn't do it all the time. If chkdsk doesn't see anything, try to use the disk diagnostics tools of your disk manufacturer or computer OEM.
At the end of the day, it is not a big issue, but it could be the case that the file system is not tracking the bad sector correctly and therefore some data could be corrupted. Whether this data would render the file inoperable is unknown but the probability is low.
What you have to watch for is whether the number of bad sectors increase. This is why I wouldn't set ATI to ignore bad sectors all the time. From time to time uncheck ignore bad sectors from the advanced backup options and see if ATI chokes on more and more sectors. This will be a sign that your disk is failing.
- Log in to post comments

Thanks for the insight into what may be going on and how to approach it. I'll keep and eye on the number of sectors.
- Log in to post comments

I have just built a brand new system with a brand new SSD and installed ATI2011 using the license for the machine it replaced. I got this error message the first time I ran ATI. Should this happen on a new disk?
- Log in to post comments

Hi Charles,
No. This error is indicative of another problem. The disks integrity and health sould be verified using chkdsk /r. If the error persists, snapshot errors can usually be resolved by performing a repair or clean install of the product.
- Log in to post comments

What is more important to me is how to determine what "hard disk 3" is???? I have run into this issue with winblows many times. "Hard disk 3" does not help me when I have 8 disks in my machine and every utility you bring up in windows seem to order them differently!!!!! How do I know which "disk 3" acronis is referencing? I am doing a backup that includes two ssd's and three hard drives and I have run chkdsk on all the hard drives and run the extended factory smart tests on both ssds and they all keep comming out clean. but I cannot complete a damn backup because I keep getting this error and it's literally driving me insane not knowing which disk is "hard disk 3" !!!!!!!!!!!! Argh!!!!!!!!!! <--- really frustrated!
Also the previous poster clearly said he has an SSD. I would NEVER tell anyone to run chkdsk /r on an SSD. The SSD itself has hardware to manage bad sectors using /r should not be used on SSD's just as you should never defrag an SSD.
- Log in to post comments

richard, you don't mention what flavor of winblows you are using ...
If 7 then click on Start and type manage into the search bar, open Computer Management from the results and then choose Disk Management under the Storage category. You will see all the disks listed with a breakdown of the partitions on each one, including the names/types/status etc.
If 8 then get to the metro start and type manage ... everything else is the same as 7
Hope That Helps
- Log in to post comments

richard mulawa wrote:Also the previous poster clearly said he has an SSD. I would NEVER tell anyone to run chkdsk /r on an SSD. The SSD itself has hardware to manage bad sectors using /r should not be used on SSD's just as you should never defrag an SSD.
Richard,
That post was from 2013. The controllers used in SSD's have rapidly evolved the last few years. While you would never defrag an SSD, chkdsk verifies partition markers and the file system, both of which can cause read errors regardless of drive type. The same goes for bad cells. Although SSD's are less susceptible, bad cells can and do occur. In which case a remapping of memory occurs to resolve the problem. HDPARM and GPARTED are both great utilities that can be used to secure erase and often times fix problems on SSD's. They just happen less often because of the technology in use. Using chkdsk /r won't hurt an SSD. In the end however, you may need to secure erase an SSD that has developed errors unrelated to the OS.
- Log in to post comments

I'm getting this error all the time now. Every disk, every time. Setting it to ignore these messages results in the program hanging at "Less than a minute left" and not completing. True Image 2013 has run flawlessly for 2 years, and is now completely useless!
I've tried it on several disks, with the same result. The disks have plenty of room. I've tested the disks and they are fine. I've re-installed ATI 2013 a few times, sometimes after using the "Cleanup Utility". No change.
This started happening a few days ago. Nothing has changed on my computer. I've run several virus checks including Malwarebytes. Nothing found.
"Hard Disk 1" in my case is the drive I'm backing up TO, not the main HD that I'm backing up FROM.
Any ideas?
- Log in to post comments

I'm getting the same error. Hard Disk 1 is a brand new Western Digital USB disk. It's the target disk... Same as Jody. Anyone have any ideas?
- Log in to post comments

Robert, be careful with the disk numbering here, Acronis numbers drives from 1 - Windows numbers from 0.
If you are being told by Acronis that it cannot read from sector xxxx of disk 1, then this is most likely to be the source drive and not the target.
- Log in to post comments

I thought that might be the case...
I bought a new (bigger) drive. Paid for a 3-computer license of Acronis (I only had trial version). Used your drive clone tool and just a few hours later I'm up and running! Your tools ROCK! :) Now to post tons of accolades on social media...
- Log in to post comments

Robert, glad to hear all is OK, thank you for the positive feedback.
- Log in to post comments