Skip to main content

Disk Restore FAILURE - "Index Corrupted"

Thread needs solution
Posts: 2
Comments: 8


DISK RESTORE FAILED - "Index Corrupted":

For years I've had great luck using Acronis TI to create and restore Disk images.  But a recent restore failure of a disk image made last night has shaken my confidence in using Acronis to secure my data, etc.

The disk restore failure was accompanied by the message "Index Corrupted".

THE FAILURE:   I got a windows Blue Screen of Death (win 8.1), so I decided to restore the previous night's disk image backup using Acronis Bootable Media (from ATI 2017, 8058).   It should have been easy - I was just trying to restore the previous nights backup.  I've done it many times.   But the restore failed, saying "index corrupted".   And every attempted restore of the past three weeks of nightly disk backups all failed, and all for the same reason - "index corrupted".  (3 version chains, 1 wk each - so 21 nights of backups).

I was able to succesfully restore a backup made months ago (using Bootable Media), so at least I can get the machine running - but that backup is too old to be of practical use.  I need to be able to restore one of the nightly backups from the past 3 weeks.

MY NORMAL BACKUP ROUTINE:  I backup nightly. Acronis 2017, v8058.  I backup my main disk (ie all partitions), and save the backups onto a separate disk.  (Backup Scheme:  Custom Incremental, keeing 3 weekly chains equaling 21 days of backups.)   All backups verify, both immediately after they were created and now.)

MY CONCERN:   First, I want to be able to restore my most recent disk image.  But more importantly, I'm now worried that my Acronis backups are not reliable.  If a verified backup made the night before can't be restored, wow, that raises serious questions about the reliability of all existing backups.

"INDEX CORRUPTED" MESSAGE:   From what I've been able to gather, the "Index Corrupted" message may be related to a corruption that existed on the ssd when the backup was made.  Is that correct?  If so, I'm wondering how Acronis went at least 21 nights worth of backups without warning me that there was going to be a problem restoring "index corrupted" backups?

WHAT NEXT?    Is there is anything I can do to restore the Disk backup.  (I am able to restore individual files, but that doesn't help me).   Again, I'm using Acronis 2017.

For example, is it possible, using another machine, to mount the corrupted backup, then use chkdsk to fix it, then restore? (I've seen talk of this working on ATI 2014, but not more recent versions.)

Again, this whole incident has me very shaken.  I had grown to trust Acronis's backups.  But discovering that 21 days worth of "verified" backups can't be restored is a huge confidence buster.

(BTW:  can someone at least tell me if Acronis latest version, 2019, would have prevented this fiasco, perhaps with an advance warning about "index corrupted" problems... BEFORE it's too late, ie before a restore is attempted.)

Any help is appreciated.

Thanks,  RAA

0 Users found this helpful
Forum Hero
Posts: 70
Comments: 8346


I can't say I've seen this much in the forums.  Just did a search and found a thread on this (also in 2017).  

There does look like there could be a fix as recommended by Slava:

What it sounds like, is that the backup completed successfully, hence no errors, but there could be corruption of the original file system, which carried that corruption into the backup content.  I'd give SLAVA's recommendation a try to see if you can mount the backup as a volume and then attempt to run chkdsk on it.  If you can, and if it does detect corruption, hopefully it can repair it. 

Do you ever run validation of your backup jobs?  

Validating backups (2017)

The validation procedure checks whether you will be able to recover data from a backup.

For example, backup validation is important before you recover your system. If you start recovery from a corrupted backup, the process will fail and your computer may become unbootable. We recommend that you validate system partition backups under bootable media. Other backups may be validated in Windows. See also Preparing for recovery and Basic concepts.

Validating backups in Windows

To validate an entire backup:

  1. Start Acronis True Image 2017, and then click Backup on the sidebar.
  2. In the backup list, click the down arrow icon next to the backup to validate, and then click Validate.

Validating backups in a stand-alone version of Acronis True Image (bootable media)

To validate a specific backup version or an entire backup:

  1. On the Recovery tab, find the backup that contains the version that you want to validate. If the backup is not listed, click Browse for backup, and then specify the path to the backup. Acronis True Image adds this backup to the list.
  2. Right-click the backup or a specific version, and then click Validate Archive. This opens the Validate Wizard.
  3. Click Proceed.
Posts: 2
Comments: 8


In response to your questions/suggestions…

Yes I validate my backups, and they all show ok - both now and when they were originally made.

And I looked at the link you provided that discusses using CHKDSK on a mounted backup to look for errors.   I ran chkdsk on the mounted C drive and it does report an error - but chkdsk says it can't attempt a fix because the drive is "write protected".    (BTW: the link you provided mentions that Read&Write mount support was removed after ATI 2015.  I'm using 2017.)

I then had the idea to try the Trial Version of 2019, just to see what would happen.  That gave me a more detailed error message having to do with chkdsk... but I couldn't decifer it.  

If you're interested, here's what I tried in greater detail.  At the bottom I include the more detailed error msg that ATI 2019 Trial gave me.   Perhaps you can decifer it.


First, I ran plain CHKDSK on mounted drive C, known as "drive Z" while mounted.  Chkdsk reported an error.


     The type of the file system is NTFS.

     The volume is in use by another process. Chkdsk

     might report errors when no corruption is present.

     Volume label is samEVOssd250-i7-win8.1.

     WARNING!  F parameter not specified.

     Running CHKDSK in read-only mode.


     Stage 1: Examining basic file system structure ...

     219136 file records processed.

     File verification completed.

    3823 large file records processed.

    0 bad file records processed.


     Stage 2: Examining file name linkage ...

     Error detected in index $I30 for file 5350.


       295768 index entries processed.

     Index verification completed.

     Errors found.  CHKDSK cannot continue in read-only mode.


Then I ran CHKDSK again, asking it to FIX errors, but I got a msg saying drive is "write protected.


     Z:\>chkdsk /f

     The type of the file system is NTFS.

     Cannot lock current drive.

     Windows cannot run disk checking on this volume because it is write protected.



After the above, I tried using the newer ATI 2019 TRIAL (I use 2017), just to see what would happen.

It also failed to restore my disk image, BUT... it did manage to give me a more detailed msg which mentioned using chkdsk.   But I can't figure out what it means.  The syntax of the message is confusing - maybe you can decifer it.  The ATI 2019 error message appeared as follows…


More information about this error and solutions may be available online in the Acronis Knowledge Base.  To access the online resource manually, enter the event code at:     Failed to prepare operations. Error code: 10 'File system error is found. Consider checking the disk using Check Disk Utility.' with extended code: 458,789 'Index corrupted' (0xA0001) $module = "trueimg_home_media_glx_17750"_Prepare : c:/bs_hudson/workspace/790/processor/diskadm/da_native_batch.cpp(133) Index corrupted (0x70025) $module = "trueimg_home_media_glx_17750" CheckIndex : c:/bs_hudson/workspace/790/core/resizer/ntfs/fs_ntfs_check.cpp(903)


I made a few attempts at running chkdsk again, tacking on what appears after "… with extended code:" above, but I just got chkdsk error messages.

Any ideas?


Posts: 109
Comments: 28256

RAA, as you are now trying ATI 2019 in Trial mode, please open a Support Case direct with Acronis and let them investigate this file error issue further with you.

The only other suggestion here would be to look at the Recovery Options available when getting to the final step of the recovery process using the Acronis Rescue Media, and see if you are offered the option to try doing a 'Sector-by-Sector' mode recovery?

Posts: 2
Comments: 8


I tried your idea of a  "sector-by-sector" restore.  No luck - I got the same failed restore.

I also followed your suggestion and submitted my case directly to Acronis.  I'll report back if/when they respond.  Thanks.


Posts: 109
Comments: 28256

RAA, thanks for the update - sorry the suggestion wasn't able to help here.  Please do let us know the outcome of your support case.