Direkt zum Inhalt

Image restore fails: I thought I was safe, but I was not.

Thread needs solution

I am using Acronis already for a long time. Instead of using Windows Recovery I have nine image versions of my OS-partition (Windows 10): three of the most recent days, three of the most recent weeks and three of the most recent months. Two days ago, I wanted to restore the image of the day before, because something happened I didn't trust.

In the restore process, after selecting the location for the image to recover, the error massage "Index corrupted" appeared. Despite the error massage, the recovery process started, but when it was finished, the error message "Recovery operation failed" appeared, leaving unallocated space in the partition where the image should be restored. I validated the image and the test was OK. I tried to fix the image by mounting it and then checking the partition or removing 'invalid' files, however the mounting failed with the error message "Cannot assign a drive letter to a partition of the backup archive".

OK, so I tried the image of two days before. Same result, etc. At the end only the oldest version (from March 1st 2016) succeeded (which puts me back four months! Would this have occurred a month later, no proper images would be left. And the worst of all: I thought I was safe, but I was not. Reliability should be number 1 in backup software).

The issue is already in the hands of Support, but it seems to take some time to get the proper feedback, while I have to decide whether to continue with the recovery of the old image or there is still a change to fix the corrupted images (it concerns my work laptop). So, I want also to address my issue also to this community. Does anybody know if there is a way to get my more recent images restored?

By the way: I wonder why it can happen that the restore of an image fails, while it is an image of a system that worked and the image is valid. Acronis mentioned that the message "Index corrupted" is not from True Image but from the system or something else. I think this is not a good excuse. During the restore, the message "Index corrupted" already appears at the stage of selection of the location, before the restore itself is started. So, apparently the image is tested at this stage. Why is this test not executed after creation of an image, incorporated in the validation, so one knows something is wrong and can take measures? I urgently recommend Acronis to do so.

Kind regards, Jan Hoogendoorn.

 

0 Users found this helpful

The error you speak of most commonly refers to File System Index errors.  File Systems create an index of data on disks so that such data can be located when requested. 

Did you attempt this recovery from within the Windows installed True Image app?  It might be possible to use the bootable Recovery Media to first validate the backup files that you have created and if that is successful you should be able to use the Recovery Media to restore the backup.  If you have a spare disk to use as a target for doing this you might give it a try.

I started recovering the image with the Windows installed True Image app, but as that failed (and emptied the partion) I had to change to recovery with the bootable Recovery Media. The image validation was OK and the image contains a working system. I know about the File System Index error (that also the message), which can be fixed by mounting the image. However, the image failed also to mount.

 

I usually do not recommend third party software however, your situation I believe can possibly be fixed using a third party tool known as TestDisk.  Please review the links below.  The first link is a general overview of TestDisk, the second is an explanation of the advanced feature set of TestDisk and how it can repair the MFT index.  You might consider giving it a try.

 

http://www.cgsecurity.org/wiki/TestDisk

http://www.cgsecurity.org/wiki/Advanced_NTFS_Boot_and_MFT_Repair

The image is the problem, not the disk. What I would need is software to fix the image or Acronis should add the the option to ignore the corrupted index during restore or Acronis should test the partiotion before making an image, so one can repare the partiotion before an image is made.

 

I understand that, you still might fix it using the recommendation.

Were you able to complete a restore to a disk?  It sounds that way in your previous posts.  Using the TestDisk software it might be possible to repair the restored disk so that it will boot and work for you.

Ok, sorry for the misunderstanding.