Skip to main content

Laptop disk image restore fails due to index corruption

Thread needs solution

Hi,

I reported this issue using live chat, and was advised to perform chkdsk on drive.

Acronis The case number s 02973142.

As disk is new disk I added new disk and created a partition then performed chkdsk as live chat advised.
Chkdsk found 0 bad sectors.

Details of machine and problem.

I would appreciate some advise.

Cheers Noel

Laptop ASUS N82J 
DVD and USB 2/3
Restoring laptop system drive
Restore source is USB
Bios American Megatrends N82JQ 206
Total memory 8192

I need to do a restore after upgrade. Backup performed in Acronis 2016. Have tried restore in Acron 2016 and Acronis 2017.

Booted from Acronis WINPE 10 (Creator edition), also tried using linux boot option.

Have tried with original system drive and also with a new system drive, but get same error in both cases.

Backup validates but restore allways fails with index corrupt. 

Upgraded from Acronis 2016 to Acronis 2017 but restore still failed.

Please help.

Cheers Noel

<?xml version="1.0" encoding="UTF-8" ?>
<logs>
<log build="8053" product="Acronis True Image" task_name="Backup Validation" uuid="3E8839EC-412A-43A4-A9FC-B70B59B5FC0D" version="20.0">
    <event code="0" id="1" level="2" message="Operation &quot;Backup Validation&quot; started." module="100" time="1493615177" />
    <event code="1026" id="2" level="2" message="&lt;bold>Validate Backup Archive&lt;/bold>&lt;endl/>&lt;tabpoint value=30>&lt;indent value=4>Location:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>&quot;C:\Entire PC (ASUSWIN7) immediately after creators upgrade_full_b1_s1_v1.tib&quot;&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>&lt;/indent>&lt;endl/>" module="11" time="1493615177" />
    <event code="504" id="3" level="2" message="Pending operation 4 started: 'Validate Backup Archive'." module="1" time="1493615177" />
    <event code="1" id="4" level="2" message="Using default upnp detection algorithm." module="339" time="1493621206" />
    <event code="252" id="5" level="2" message="The archive was successfully checked." module="100" time="1493621206" />
</log>
<log build="8053" product="Acronis True Image" task_name="Recover" uuid="3E8839EC-412A-43A4-A9FC-B70B59B5FC0D" version="20.0">
    <event code="0" id="1" level="2" message="Operation &quot;Recover&quot; started." module="100" time="1493621320" />
    <event code="1020" id="2" level="2" message="&lt;bold>Recover Backup Archive&lt;/bold>&lt;endl/>&lt;tabpoint value=30>&lt;indent value=4>From file:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>&quot;C:\Entire PC (ASUSWIN7) immediately after creators upgrade_full_b1_s1_v1.tib&quot;&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>Recovery of:&#9;&lt;indent value=10>&lt;textcolor value=&quot;navyblue&quot;>Disks&lt;/textcolor>&lt;/indent>&lt;indent value=4>&lt;endl/>&lt;/indent>&lt;endl/>" module="11" time="1493621320" />
    <event code="504" id="3" level="2" message="Pending operation 52 started: 'Clearing disk'." module="1" time="1493621320" />
    <event code="504" id="4" level="2" message="Pending operation 14 started: 'Recovering partition sector by sector'." module="1" time="1493621320" />
    <event code="504" id="5" level="2" message="Pending operation 14 started: 'Recovering partition sector by sector'." module="1" time="1493621627" />
    <event code="502" id="6" level="4" line_tag="0x65B5EB7011094700" message="Index corrupted" module="1" time="1493625537">
        <field name="$module" type="TIdentifier">trueimg_home_pe_vsa64_8053</field>
        <event code="37" id="7" level="4" line_tag="0xA7795193C91882CC" message="Index corrupted" module="7" time="1493625537">
            <field name="$module" type="TIdentifier">trueimg_home_pe_vsa64_8053</field>
        </event>
    </event>
    <event code="0" id="8" level="2" message="Bootability restore operation has started." module="29" time="1493625537" />
    <event code="0" id="9" level="2" line_tag="0x0" message="" module="0" time="1493625539" />
    <event code="0" id="10" level="2" line_tag="0x0" message="" module="0" time="1493625539" />
    <event code="0" id="11" level="2" line_tag="0x0" message="" module="0" time="1493625539" />
    <event code="0" id="12" level="2" line_tag="0x0" message="" module="0" time="1493625539" />
    <event code="0" id="13" level="2" message="Bootability restore operation has finished." module="29" time="1493625539" />
    <event code="37" id="14" level="4" line_tag="0x91BD40306B6C5084" message="Index corrupted" module="7" time="1493625590">
        <field name="$module" type="TIdentifier">trueimg_home_pe_vsa64_8053</field>
        <event code="37" id="15" level="4" line_tag="0xA7795193C91882CC" message="Index corrupted" module="7" time="1493625590">
            <field name="$module" type="TIdentifier">trueimg_home_pe_vsa64_8053</field>
        </event>
    </event>
    <event code="252" id="16" level="4" message="Recover operation failed." module="100" time="1493625590" />
</log>
</logs>
 

0 Users found this helpful

Did you run chkdsk on the source disk (all partitions) ?  Your log indicates that the restore is being performed in sector by sector mode which should not occur unless there is corruption on disk or the user has chosen that option.  If you chose that option try the recovery again without selecting Sector by Sector.

Hi Enchantech,

Thanks for replying.

I have run chkdsk on the restore source as you have suggested, but it didn't find any errors or bad sectors.

Before performing the restore I ran a validation on the restore source, which returned the following result:

   <event code="252" id="5" level="2" message="The archive was successfully checked." module="100" time="1493621206" />

The restore is a 'sector by sector' restore, but I don't see anyway in True Image 2017 to prevent it doing a 'sector by sector' restore, as there isn't a setting to select/deselect 'sector by sector' for the restore.

How can I prevent it from doing a 'sector by sector' restore?

Thanks again for your help.

Cheers Noel

 

Noel, what was the size of the drive that you made the backup from originally, and what is the size of the drive that you are trying to restore the backup to?

When you have a sector-by-sector backup then you need a target drive which is at least the same size or larger than the source drive as there can be no automatic resizing of partitions when this mode is used.

If possible, use the MVP Log Viewer to check if you have the logs from when you originally made the backup image with ATIH 2016.  Note: you will need to launch the Log Viewer in Legacy Mode for the 2016 logs as Acronis changed the log format with 2017.  Click on File then on Program Launch mode from the menu, then select to start in Legacy mode next time followed by closing / relaunching the tool.  Link for the Log Viewer in my signature below.

The reason for asking about the original 2016 backup log was to check if the backup was also created using sector-by-sector mode?

Have you run chkdsk on the original system drive?  If there are errors on the drive from which the backup was made this can cause the sector by sector restore situation.  Steve is correct, if the backup was made in sector by sector mode then the restore would have to be done to a drive at least as large as the original drive was.

If errors are found and corrected on the original system drive then create a new backup of that drive and attempt the restore again.

Hi Steve and Enchantech,

Thanks for your suggestions.

I ran chldsk /r /f on both the source and the destination drive. I have attached the results.

I haven't used the MVP log viewer as not sure what that is or where to find it but presume it just provides a view of the xml log file.  As I can't boot the system from the original system disk as it just blue screens, do I need to extract the acronis log from the backup to find if it did a sector by sector backup?

The destination is a new 1T drive and the source drive contains a backup image of the original 300G drive, along with a number of other backups.

I attempted a drive restore again. Acronis screen showed acronis was doing a 'sector by sector' restore. The restore failed and the message on the screen was 'restore failed'. There was no entries in the Acronis log. It did restore one partition which was a hidden Fat32 restore partition.

I have previously run verify on the backupimage and the image verified as Ok.

What should I do now? Would it be helpful if I try and get the acronis log from the original backup?

Cheers Noel

Attachment Size
410903-138418.jpg 249.88 KB
410903-138421.jpg 276.12 KB

Noel, what other backup image files do you have for this laptop besides the one you have been trying to restore?

Are you restoring the backup to the same laptop internal drive as the backup was created from?

Does your backup image include a UEFI / EFI partition, and if so, are you booting the Acronis Rescue Media in the same UEFI mode?

Hi Steve,

Thanks for replying.

--- Noel, what other backup image files do you have for this laptop besides the one you have been trying to restore?

 I do have a backup taken before the creator upgrade.

--- Are you restoring the backup to the same laptop internal drive as the backup was created from?

I have tried restoring to the original system 300G drive, but as that failed, I have tried restoring to a new 1T drive.  I got the same errors of 'corrupt index' in my attempts with both destination drives prior to running chkdsk, though no errors were displaed in the last attempt as restoration other than 'Restore Failed'

--- Does your backup image include a UEFI / EFI partition, and if so, are you booting the Acronis Rescue Media in the same UEFI mode?

The Acronis 2017 rescue disk was created on a newer UEFI enabled laptop.  The laptop I'm restoring to is an old one and UEFI is disabled in bios of destination laptop.  I do have a Acronis 2011 rescue disk created on the destination laptop.

Cheers Noel

 

Noel, please see post: 128057: [Tutorial] How to recover an entire disk backup and check that you are following the same steps as shown for doing an entire disk recovery.

The key point with the rescue media is that this should be for the same version as was used to create the backup image, so if you are restoring an Acronis 2011 backup image, use the 2011 media, otherwise if the backups were created with 2016 or 2017, then use the 2017 media.  If you are doing this on the older laptop, then it should boot in Legacy mode if UEFI is disabled, assuming that this is also how Windows was booting.

Hello Noel,

The message "Index is corrupt" refers to file systems that are inside the backup. Try mounting all the partitions from the backup, opening cmd as administrator and running "chkdsk" against each mounted partition. E.g., "chkdsk E:", then "chkdsk F:" (without quotes) etc. If any problem is found by chkdsk here, you would need a read-write mount mode, run chkdsk with /f parameter, save changes by unmounting the disk volume and recovering the new incremental backup that would be created automatically once you unmount the drives. Read&write mount mode was removed since 2015 version of the software, but it was present in 2014. You can ask about it in the communication with the Support Engineer.

Validation option just verifies that backup contents remained unmodified since the backup was taken: it re-calculates checksums of backed up blocks and compares them with values stored in the backup at backup creation time. Validation operation in Acronis True Image does not tell you if the file system is bad or good.

Sometimes hardware issues may mislead the software and it could give wrong error messages. In your place I would try to exclude as many factors as possible: copy the .TIB to another drive and repeat the recovery attempt using bootable media from 2016 version to a different disk.

You can try restoring disk volumes one-by-one until you find the problematic volume. "Entire PC" backup includes all the internal disk volumes and by default also tries to restore them all. If you find the disk volume that fails to recover, you can recover it in files/folders mode into a manually created partition, and then fix the bootability from Windows repair or installation DVD.

Regards,

Slava

Thanks Steve and Slava for your help.

There appears to have been some corruption in logical drive d when I took the most recent backup.

I have restored an earlier backup and extracted the modified data from the latest backup, so I'm now happy.

I had assumed when backing up,  that as long as I ticked 'Validate when it is created', then I would always have a backup that I could restore to the orginal or replacement hardware in the event of hardware failure.

As both of you have pointed out, my assumptions about 'validation' were incorrect.

How best do you recommend I should use Acronis so that I am always confident that I can restore the system to new hardware in the event of a hardware failure?

Thanks again.

Cheers Noel

 

Noel, glad to hear that you have resolved the corruption issue.

In terms of best using Acronis, I can only recommend setting up the Notifications for each of your backup tasks and doing a careful check of the emails when you get them to make sure there are no error messages being shown.

Other than doing the above, you can do a manual validation of your backup .TIB image files and also open these in Windows Explorer (by double-clicking on the file) and have a browse around the contents to see that all looks good, perhaps select a random file or folder to copy to a temporary location.