Why 'failure to read' persistent error?
ATI-Home 2010 build 7,154
Win7 64 bit
Did a clean install last week from 32 to 64 bit. Acronis ran okay on that initial image and a few days following.
I posted a message a few days ago that the app was not starting the daily scheduled image and generated no log.
As of the past 3 days I cannot get the app to manually perform an image. I get a similar error to the one attached.
last night I ran the OS error checking with both fix errors and scan empty space checked off to no apparent avail per attached log.
Suggestions?
Mark
Did the recommended with no success then read a previous message of yours suggesting killing off the current job and creating a new one. That solved both the I/O error + the auto start up problem.
Thanks--
Mark
Well, hard to see how recreating a job solves an I/O issue, but if it worked, that's fine :-)
We'll my fix almost worked.
Got the I/O problem again this morning after 2 good days post job rebuild. The job still starts as it should, however, post the rebuild.
Apart from the usual suspect of a drive scan (fix + all areas) which I performed on all partitions and drives of the source and target, any other considerations or links prior to me sending an email to Acronis?
Mark
"Failure to read the snapshot" can come from different places, it looks like. If you already uninstalled, reinstalled and checked your disks, you should get expert help from Acronis support.
I had upgraded (32 bit to 64 bit) the OS ~2 weeks ago. I installed the application along with all other applications post the OS re-install. However, I did not re-install the application a second time after the OS install and after these referenced problems.
Taking your cue, I uninstalled and reinstalled the application.
I'm pleased to say that I've now successfully run the application 5 times, 2 started as scheduled and 3 manually.
Although I have no idea why this re-install could have resolved the problems, I think the problems may be fixed.
One further point--I have as omitted file types: $*.*, *.tmp, *.bak, *.old, ~*.* and *.tib. Can you suggest any other file types to add?
Thanks--
Mark
I have not changed anything but am getting this snapshot error creating a new C drive backup. My D drive backup now just freezes - a full one or an incremental one. No other problem for years! Attached is a sample of identical error messages and codes on about 40 files out of thousands. I have now spent some days attempting to resolve issues - but seem unable to follow up all the error message information anywhere. Any pointers would be welcome.
Hello Terence,
Welcome to our Forum, we're glad to greet you here. I understand your concern, and will be glad to assist you.
As mentioned above, this error can be caused by various reasons. Luckily we have all of them described in this KB article alongside with the solutions. Please follow the instructions provided, and if the problem remain please create a system report as described in AcronisInfo Utility. After that please submit a case with the information attached, and let us know its number.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
Thank you for your very prompt reply. I have re-run chksk on all disks - no problems identified. I have run the info utility and no problem identified. Having run a new complete backup of my (30GB) C drive and "skipped" the files with the problems I have found that an incremental backup coped successfully with the same files (as commented by another forum member). I will try the D drive this evening/night and see if it freezes again. Will update tomorrow (and submit report if it does not work). Thanks again