Skip to main content

Acronis Recovery Failure from a SystemDrive Image

Thread needs solution

I have seen the other actual thread talking about recovery failure... I did not want to mix up 2 different errors, and that is why i create a new thread here.

I did an Image-Backup from my drive C with Acronis 2013, some time ago.

When now trying to restore that with Acronis 2019 the system reboots into the recovery mode, then starts operation, and then there is an errormessage saying "Failurecode 10, found errors in Filesystem". (It is on german, this is a translation). There is no choice at this point, recovery mode is left and system reboots normally, without having done the restore of the older image.

There is also a button with which i can create a system report.... i have done that when trying the second time.

I then did check the usage of an rescue-media from Seagate Recovery Tools, that one also stated "Index failure" when scanning through drive C. But here i was able to continue and to ignore the errormessage. The old state of drive C was restored and everything seems to be ok so far.

I was first thinking that errormessage points to an error in the filesystem on the actual drive C, but i did check after that and it seems that the error is in the tib-files. Selecting another set seems to be ok, that one specific set still creates the errormessage.

 

So here are my 2 questions:

Was the idea of restoring from a tib-fileset ok, or might there be errors in the files now? Because i simply did ignore the errormessage... Would it be better to use an older image instead (which unfortunatley would be very very old...)

Is there a chance to repair the tib-files?

I have screenshots from the errormessages and also the report from acronis which i could send for analyzis, if needed...

 

Thanks in advance

0 Users found this helpful

I did an Image-Backup from my drive C with Acronis 2013, some time ago.

When now trying to restore that with Acronis 2019 the system reboots into the recovery mode, then starts operation, and then there is an errormessage saying "Failurecode 10, found errors in Filesystem". (It is on german, this is a translation). There is no choice at this point, recovery mode is left and system reboots normally, without having done the restore of the older image.

How long ago was the ATI 2013 backup image created?  Was this weeks, months, years?

Recovery of any backup that includes the Windows OS is not recommended to be started from within Windows.  The recommended method is to boot from the Acronis Rescue media and to do this using the same BIOS boot mode as your Windows OS uses to boot, which will be either in Legacy (MBR) mode, or else in UEFI (GPT) mode.  This is important as using the incorrect boot mode can result in an unbootable restored system!

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

It is possible that filesystem errors can occur within the .tib file archive and if so, are very difficult to resolve as the archive is a read-only file which doesn't allow for the use of CHKDSK etc.

I then did check the usage of an rescue-media from Seagate Recovery Tools, that one also stated "Index failure" when scanning through drive C. But here i was able to continue and to ignore the errormessage. The old state of drive C was restored and everything seems to be ok so far.

If there are any disk errors / bad sectors etc on your target drive (C:) then this will cause problems for any recovery operation.  If this is a Seagate drive, then run a full disk diagnostic to check the drive.  Note: the first action when a recovery starts will be to wipe the target drive then recreate the partitions as per the data in the backup .tib archive.

Selecting another set seems to be ok, that one specific set still creates the errormessage.

If you have an older .tib backup archive and this does not give any errors when trying to recover the contents, then this may be the choice you need to make and use.

Unfortunately there are no utilities provided by Acronis to repair problem .tib files - we can only recommend that users make several different backups and store these on different media / in different places.

They are from beginning this year, when i did re-install W10 on a new machine from scratch.

The 2 backups are only days apart, but the first one is W10 naked and the second one is W10 with all setting, programs a.s.o. installed, so there is a hugh amount of work between those 2 versions.

Thanks for KB59877l, will check that. Until now i never had issues with starting a restore from within W10...

I am pretty sure that the error is not on the physical harddrive but on the tib-files. A check of that drive did not show any issue, and still using that one specific Backup-Set always shows the same errormessage, any other does not. Funny... as the errormessage sounds more like having an issue with the target drive, but it seems as if the content of the tib-files are failing a specific test.

And yes, i did store the backup files on different locations... but obviously the first created tib-file-set has the issue already in, as all copies show same behaviour.

Is there a way to find more detailed information about that errorcode in the system report i did store?

I also was not able to find any more explanation for the errorcode online... i did use the internet page suggested in the errormessage, but that code was not found...

Is there a way to find more detailed information about that errorcode in the system report i did store?

I also was not able to find any more explanation for the errorcode online... i did use the internet page suggested in the errormessage, but that code was not found...

There may be some additional information held in the system report files but without looking at it, I cannot say if it would give more details on what is happening above what is already known?

The links to the KB can often prove of no value but are there to alert the Acronis folks that these issues are happening and allow them to review if more information could be provided if there are reasonable numbers of users hitting the same issues.