[RESOLVED] Cannot read data/cannot read snapshot, plus CRC errors
ATTH 2012 + Pluspack, build 7133 on windows 7 enterprise with all patches
Since about 2 weeks I keep getting the dreaded errors:
cannot read data in sector ###### of hard drive 1
cannot read snapshot (0x10C45A)
CRC error 0x100155
after which I manually cancel the operation or the scheduled operation cancels itself.
Used several tools to find disk errors, there are none.
I could use some input to find out what to do next, I am out of options.
Issue resolved here.
- Accedi per poter commentare
OK, will try that one, takes some time altogether, but will report back. Thanks.
- Accedi per poter commentare
I am afraid I have an issue with my C drive and I definitely need help.
I made an image with the recovery CD to an external USB drive.
It all seemed to go right, but just before finishing I got message "cannot read-write to sector ######". I got several of these messages, clicked ignore and after 3 messages I decided to choose the option to ignore them all. I booted into Windows alright. I choose to make a systemreport, Acronis saved it on drive I:, but that drive has no media, so it might be somewhere else.
In Acronis logfiles I find a report I understand zero. It seems suddenly the Acronis non-stop backup is running. I do not use this option, but now it is active. How come and can I stop it?
I will attach the logfiles of today (=tonight), but it is all in Dutch so I do not know if it is of any help.
If you or anyone could explain to me what is best to do, I am most grateful
- Accedi per poter commentare
Acros,
Have you run chdsk /r on the drive causing problems?
- Accedi per poter commentare
Yes, I did chkdsk /f. There were some damaged clusters but no bad sectors.
Meanwhile I found out non-stop backup was installed and/or enabled when I updated my ATTH to build 7133.
Since I have a comprehensive daily backup/imaging routine, I disabled the service because I think it unnecessary.
The image created after disabling the non-stop backup went flawless.
No idea if these issues are related.
I will create some more images to different media and see what happens next.
Will report back.
For reasons of privacy I deleted the logfiles attached yesterday.
- Accedi per poter commentare
Acros,
Make sure your run chkdsk /r, chkdsk /f is not good enough.
- Accedi per poter commentare
After scrutinizing my logfiles and trying to analyse where/when it all started it looks as though my system is at war with Windows SearchIndexing. Summarized: SearchIndexing created corrupt databases. At the regular imaging tasks the related sectors were correctly recognized by Acronis as unreadable/unwriteable sectors and Acronis stopped with the above mentioned errors.
Non-stop-backup however continued writing to these sectors.
Chkdsk found the clusters to be damaged. After a chkdsk repair and reboot all worked fine, until SearchIndexing again created havoc, as it seems
I first disabled Acronis non-stop backup service and did a new chkdsk /r to repair the bad clusers.
After reboot the regular Acronis imaging task however encountered again unreadable/unwriteable sectors and ended with errors.
I then disabled the Windows Search service and again did a chkdsk /r, which repaired the errors.
After that Acronis runs fine, no errors.
Am not sure if non-stop backup can be enabled again, but after working long time on this issue, which needs rebooting and chkdsk for hours, I do not dare to try. Besides, I do not need the service, Acronis makes daily images on an internal disk and 3 times weekly on a removable medium, so I have plenty backups in case something happens.
I go and try to trouble shoot the Windows Search Indexing service, which is not an easy one if you look on the internet. With that issue you'll never be lonely.
But for now, Acronis works fine and that is the most important thing for me.
Thank you for your input!
And to other readers: in case you encounter similar Acronis errors as mentioned in my first message, check your logfiles for any errormessages about Windows SearchIndexing. I have no clue how to remedy it, but disabling this servicce might at least help you to use Acronis.
[NB Sorry about mentioning chkdsk /f - in my earlier post. In fact I did use chkdsk /r, typo]
- Accedi per poter commentare