Corrupt Index
Hi All,
I tried to make 2 recoveries with latest TI 2020. Both show corrupt index messages and then I get to boot into the keyboard language menu and then I end up in the recovery console.
What is going on? I haven't had an issue with TI for at least 5 years.
Am I going to have to revert to an older version ?
Thanks for the help
Hi Enchantech,
I'm using Windows 10 1909. I have images from TI 2019. All restored images are rebooting into Recovery console.
I even chose an imaged dated 6 months and the same thing happened.
I really don't understand what is going on.
The more I look into this the more I think that this version of TI in fact I suspect that all my TI backups have been recoded and have become corrupt. This means that I don't have a single functioning backup and I'm probably stuck to reinstall my whole operating system.
If that's the case, I'm not going to be a very happy camper.
OK, just as I thought. Version 22510 has a serious bug. Recoded all my images.
I reinstalled Windows, then installed TI 2019, validated an older image and restored. Then I installed 2020 21400 Validated last image made and was able to restore.
What a nightmare. Guys, you made a mistake with this update.
Zardoc wrote:OK, just as I thought. Version 22510 has a serious bug. Recoded all my images.
I reinstalled Windows, then installed TI 2019, validated an older image and restored. Then I installed 2020 21400 Validated last image made and was able to restore.
What a nightmare. Guys, you made a mistake with this update.
When I consider how many customers are affected by tib backups and can no longer produce their images under the Build 22510.
Ati your builds are lately shotgun where I as a customer can not use.
-Aus Ati 2019 no pictures with build 22510
-Installing the Build 22510 sometimes only with huge effort to connect on some systems (the ATI 2019 doing without problems)
Crashes / trailers after starting the 22510
I would like to have more quality from you and not such snap shots as 2020.
Zardoc wrote:Hi Enchantech,
I'm using Windows 10 1909. I have images from TI 2019. All restored images are rebooting into Recovery console.
I even chose an imaged dated 6 months and the same thing happened.
I really don't understand what is going on.
I've never used the Recovery console so am not sure of some of this terminology. When you say "All restored images" does that imply you have done the restores, or are you referring to images available to do a restore? And what do you mean by "are rebooting into Recovery console"?
Have you tried booting from an ATI recovery medium and seeing if it can recognize your backups?
I don't know how the recovery console works but I assume it invokes the (OS-based) ATI recovery function. While that might be OK for a "files and folders" recovery it is not the safest way to do a "disks and partitions" recovery. The recovery process will change your boot information (Not accurate terminology, I'm sure.), reboot into recovery software, and (with luck) reboot back into Windows when complete. You're much safer doing your own boot into a ecovery medium - no boot records get changed.
Patrick O'Keefe wrote:Zardoc wrote:Hi Enchantech,
I'm using Windows 10 1909. I have images from TI 2019. All restored images are rebooting into Recovery console.
I even chose an imaged dated 6 months and the same thing happened.
I really don't understand what is going on.
I've never used the Recovery console so am not sure of some of this terminology. When you say "All restored images" does that imply you have done the restores, or are you referring to images available to do a restore? And what do you mean by "are rebooting into Recovery console"?
Have you tried booting from an ATI recovery medium and seeing if it can recognize your backups?
I don't know how the recovery console works but I assume it invokes the (OS-based) ATI recovery function. While that might be OK for a "files and folders" recovery it is not the safest way to do a "disks and partitions" recovery. The recovery process will change your boot information (Not accurate terminology, I'm sure.), reboot into recovery software, and (with luck) reboot back into Windows when complete. You're much safer doing your own boot into a ecovery medium - no boot records get changed.
Hi Patrick,
I'll try to keep it simple. I created an image with TI 22510 2 days ago. I decided to restore that image. I used a USB bootable media. When came time to select drive to recover to (Which should be C) I got a ‟CORRUPT INDEX” MESSAGE. Nevertheless, restore went ahead. When I tried to reboot to windows, all I got was a first message to choose a Keyboard language and then I ended up in the Winre (Windows recovery environment) AKA Recovery console.
I then tried to restore another backup and got the same message.
Then I tried to restore a .TIB backup created from TI 2019. Same results.
Then I decided to use a USB bootable media from ATI 2018 and tried to restore a backup that I was sure had already been used without any issues and I ran into the same problem on reboot into Windows (choose a Keyboard language and then I ended up in the Winre console).
That’s when I suspected that TI 2020 had recoded my backups.
So, I reinstalled Windows, reinstalled TI 2020 but used version 21400. I validated the latest backup that I had first tried to restore created another USB bootable media.
Now I was able to restore my backup and get back to work.
BIG WASTE OF MY TIME!!
I hope that it’s clear enough this time.
Now that I have calmed done from my frustration,
I would like to know from the gurus (which if I remember correctly never answer here) but hope they might, what happened that made TI recode backups and is there a fix on the way.
Thanks.
Zardoc, you have not provided any diagnostic information such as the logs from either the backup or recovery operations, or an Acronis System Report from when this issue was present, therefore there is just too little information to work with here.
I do not recall seeing anyone else reporting any recent topics for 'Corrupt index' and do not know what the context for this error message might be here, i.e. was it referring to the actual backup file or to the media on which the backup was stored, or the destination drive for the recovery etc?
I do not believe that there has been any 'recoding' done here, especially if you have backups that you created long before this issue started and which you have previously used without any problems.
Given the fact that reinstalling Windows 10 has resolved this issue and now your rescue media and recovery is working again, this would suggest that the root issue was on the drive rather than with the backup file(s) or rescue media.
Zardoc wrote:I would like to know from the gurus (which if I remember correctly never answer here) but hope they might, what happened that made TI recode backups and is there a fix on the way.
Zardoc, just an aside comment here.
Steve Smith and Enchantech are a couple of the most knowledgeable people in the ATI community. Definitely "Guru" status. But if you want to communication with an Acronis employee you will have to open a problem ticket. This is a forum of ATI users. A couple of Acronis people occasionally show up here, but this is not an official channel to them.
Steve Smith schrieb:Angesichts der Tatsache, dass die Neuinstallation von Windows 10 dieses Problem behoben hat und Ihr Rettungsmedium und die Wiederherstellung nun wieder funktionieren, würde dies darauf hindeuten, dass sich das Root-Problem auf dem Laufwerk und nicht auf den Sicherungsdateien oder Rettungsmedien befand.
He used build version 21400 from Ati. The buildversion 22510 causes his concern.
The buildversion 22510 causes his concern.
Sorry but where is this proven?
Steve Smith schrieb:Die Bauversion 22510 macht ihm Sorgen.
Entschuldigung, aber wo ist das bewiesen?
Is in his reports that he had no problems with the Build 21400 and with the Ati 2019 also no. I think it's very good that he reported the concerns here in the forum.
I'm using Windows 10 1909. I have images from TI 2019. All restored images are rebooting into Recovery console.
I even chose an imaged dated 6 months and the same thing happened.
He reported as above earlier in this topic. So the problem affected images created before ATI 2020 was even released for beta testing?
In post 4,
OK, as I imagined. In version 22510, a fatal error has occurred. All my pictures newly coded.
I reinstalled Windows, then installed TI 2019, validated and restored an older image. Then in 2020 I installed 21400 validated as the last image and was able to recover.
What a nightmare. Guys, you made a mistake with this update.
in post 7
That’s when I suspected that TI 2020 had recoded my backups.
So, I reinstalled Windows, reinstalled TI 2020 but used version 21400. I validated the latest backup that I had first tried to restore created another USB bootable media.
There are some issues, for some users, with ATI 2020 #22510 but all that we can do in these forums is talk about them.
Any user who believes that they have found a code issue needs to raise this directly with Acronis by either opening a Support Case or else submitting Feedback coupled with sending an Acronis System Report along with a link to their forum topic for more detailed information.
Zardoc wrote:
'll try to keep it simple. I created an image with TI 22510 2 days ago. I decided to restore that image. I used a USB bootable media. When came time to select drive to recover to (Which should be C) I got a ‟CORRUPT INDEX” MESSAGE. Nevertheless, restore went ahead. When I tried to reboot to windows, all I got was a first message to choose a Keyboard language and then I ended up in the Winre (Windows recovery environment) AKA Recovery console.
This sounds to me like WinRE from a Recovery Partition. I question which partition is being triggered. My suspicion is the Recovery partition on the disk that was recovered. That lends me to think that Windows 10 could not start so WinRE sprang into action.
Usually when that happens the recovery utilities will run diagnostics on the the boot files, memory, etc. in an attempt to remedy the issue. Generally if let run the machine will restart on its own after attempted repairs have been made. If those repairs wer successful then Windows boot successfully.
None of this has anything to do with ATI or the recovery of the image by ATI. Since Zardoc reinstalled Windows we will never know now. Had Zardoc selected the keyboard language and proceeded with the WinRE repair attempt the problem may have been resolved for any or all of the restore attempts.
Enchantech wrote:This sounds to me like WinRE from a Recovery Partition. I question which partition is being triggered. My suspicion is the Recovery partition on the disk that was recovered. That lends me to think that Windows 10 could not start so WinRE sprang into action.
Usually when that happens the recovery utilities will run diagnostics on the the boot files, memory, etc. in an attempt to remedy the issue. Generally if let run the machine will restart on its own after attempted repairs have been made. If those repairs wer successful then Windows boot successfully.
None of this has anything to do with ATI or the recovery of the image by ATI. Since Zardoc reinstalled Windows we will never know now. Had Zardoc selected the keyboard language and proceeded with the WinRE repair attempt the problem may have been resolved for any or all of the restore attempts.
Enchantech,
That's right, It started the recovery Partition if you want to call it like that. And YES, I tried a repair and it was a no go. I also checked the drive with WD Lifeguard. The drive is a WD Black, on of the best mechanical drives on the market. It had no issues. Wasn't the drives because there was no corruption or malfunction of the drive before restore.
Patrick O'Keefe wrote:Zardoc, just an aside comment here.
Steve Smith and Enchantech are a couple of the most knowledgeable people in the ATI community. Definitely "Guru" status. But if you want to communication with an Acronis employee you will have to open a problem ticket. This is a forum of ATI users. A couple of Acronis people occasionally show up here, but this is not an official channel to them.
Patrick,
I have a lot of respect for forum support guys. They aren't paid and bear the brunt of annoyed customers.
I was a 7 year MS MVP and did support just like Steve and Enchantech. As you can see, I am not a newbie to ATI. Been a user since Drive Image sold their soul to Symantec for Ghost.
Eset has a very good policy with their customers. Two specialists that intervene in the forums when they notice an unusual bug. Often a solution is given without wasting a bunch of time with support staff that is outsourced and relies on a KB database to answer your questions.
For many years ATI has had a lack of transparency with their customers. Take the cloud issue with files lost. No excuses or comments whatsoever. But he guys here, I respect them.
Steve Smith wrote:Zardoc, you have not provided any diagnostic information such as the logs from either the backup or recovery operations, or an Acronis System Report from when this issue was present, therefore there is just too little information to work with here.
I do not recall seeing anyone else reporting any recent topics for 'Corrupt index' and do not know what the context for this error message might be here, i.e. was it referring to the actual backup file or to the media on which the backup was stored, or the destination drive for the recovery etc?
I do not believe that there has been any 'recoding' done here, especially if you have backups that you created long before this issue started and which you have previously used without any problems.
Given the fact that reinstalling Windows 10 has resolved this issue and now your rescue media and recovery is working again, this would suggest that the root issue was on the drive rather than with the backup file(s) or rescue media.
Steve, How could I have done that ? I couldn't recover any of my backups. I have 14 backups, none of which I could restore. Now if the drive was broken, why did they all work again after I reinstalled 2020 21400? The corrupt index was showing up when trying to select drive to recover to.
Now, are you going to tell me for sure that a new version of ATI that uses a new extension changes the format and size of backups does not recode parts of older backups in order to read them ? You might be right but NOT PROVEN like you said.
Zardoc wrote,
That's right, It started the recovery Partition if you want to call it like that. And YES, I tried a repair and it was a no go.
What option(s) did yo choose to run as a repair?
Did the target disk have data on it? Was it the original source disk of the backups image files used in recovery?
Enchantech wrote:What option(s) did yo choose to run as a repair?
Did the target disk have data on it? Was it the original source disk of the backups image files used in recovery?
Startup-Repair
Yes, the disk had data. it's an M.2. No it was not the original source.
Steve Smith wrote:There are some issues, for some users, with ATI 2020 #22510 but all that we can do in these forums is talk about them.
Any user who believes that they have found a code issue needs to raise this directly with Acronis by either opening a Support Case or else submitting Feedback coupled with sending an Acronis System Report along with a link to their forum topic for more detailed information.
Yes Steve, the forum is the wrong way to express a concern where we cannot solve. Let's see if the developers will have more success with the new build, but for me it was that with Ati at the moment because I can only save offline under the 2020 version.
Zardoc,
I your post #2 you said that all the backup image files you were attempting to recover were created with TI 2019 and all images restored (successfully I assume) however, when attempting to boot you WinRE Recovery began. This is all correct?
Prior to these boot attempts did you remove the bootable Recovery Media from the machine?
Did the target drive have the same OS installed prior to your recovery of these images?
Were you using Recovery Media created with the Simple method which results in a WinRE media to build the Recover Media in TI 2020 version 22510?
I assume you used the Automatic Repair option of the WinRE Startup Repair option?
Enchantech wrote:Zardoc,
I your post #2 you said that all the backup image files you were attempting to recover were created with TI 2019 and all images restored (successfully I assume) however, when attempting to boot you WinRE Recovery began. This is all correct?
Any image that I tried to restore gave me an «INDEX CORRUPT» message when I was trying to select C drive to restore image. All images whether they be from TI 2019 or TI2020 restored except when i exited the TI recovery and rebooted to Windows That's when I ended up in WinRE
Prior to these boot attempts did you remove the bootable Recovery Media from the machine?
NOPE.
Did the target drive have the same OS installed prior to your recovery of these images?
YEP
Were you using Recovery Media created with the Simple method which results in a WinRE media to build the Recover Media in TI 2020 version 22510?
I tried a bunch of recovery tools. Even the MVP tool to no avail. Same results.
I assume you used the Automatic Repair option of the WinRE Startup Repair option?
YEP
Zardoc,
Thanks for answering the questions I asked. Based on those answers I would say that the Index Corrupt message is coming from the TI application on the booted recovery media. It indicates that the File System contained in the backup is corrupted. The only way to fix that is to run chkdsk /f on all partitions in the backup file. This is a good example of why verification of a backup file prior to a recovery attempt is important as that verification is likely to have failed had it been run. You could verify this by running validation on the backup images you have. If validation does fail on those images then this suggests that the file system was corrupted on the disk from which these backups were created. I have been recommending chkdsk /f being run on disk partitions on a regular basis because of this.
Can you save your backups if they are found to be corrupt? Possibly. You would need to mount each partition of each backup image in read/write mode and run chkdsk /f on each to fix the issue. This would be a rather slow and arduous procedure and probably not worth the effort at this point. If you find the need to try be aware that the 2020 product does not support mounting of tibx files. It does support mounting of tib files to my understanding however, be also advised that it does not mount images in read/write mode. That feature was removed beginning in the TI 2015 version so you would need to use TI 2014 and have a tib file to work with to have any success.
Enchantech wrote:Zardoc,
Thanks for answering the questions I asked. Based on those answers I would say that the Index Corrupt message is coming from the TI application on the booted recovery media. It indicates that the File System contained in the backup is corrupted.
Enchantech,
How could that be? The message appears all the time when I use the TI application. The backup was restored after a new version of Windows was installed. If that were the case, a corrupted backup is corrupted no matter were you use it it will fail. Check my image. These are the same backups that were there before I reinstalled Windows. I validated all of them. As you can see, no issues. I will try a restore again just for the sake of it since I am running on a restored backup that you say is supposed to be corrupted.
I included images that show the ATI USB Tool version 2016 Linux, 2019 Winpe, 2020 Winpe. As you can see the «Corrupt Index» shows on all but usually I can recover despite the messages except for the last attempt.
Zardoc,
I cannot explain why you are able to recover the image even though you get the error message that the index is corrupt.
What I will say is that ATI is finding and showing you this exists.
Have you tried running chkdsk /f on this partition after you restored it? If chkdsk comes up clean doing that then all I can say is that the restore is able to correct the issue whatever it is and that issue must be very minor in nature, not enough to affect the restore to the point of it not working. Nevertheless, the fact is that the original disk these backups came from have the error on that partition.
Enchantech wrote:Zardoc,
I cannot explain why you are able to recover the image even though you get the error message that the index is corrupt.
What I will say is that ATI is finding and showing you this exists.
Have you tried running chkdsk /f on this partition after you restored it? If chkdsk comes up clean doing that then all I can say is that the restore is able to correct the issue whatever it is and that issue must be very minor in nature, not enough to affect the restore to the point of it not working. Nevertheless, the fact is that the original disk these backups came from have the error on that partition.
Enchantech,
Since I am not one to think that I have the solutions to all the problems I face, I followed your suggestions. I ran a validation on all backups. They all passed without problems.
Then I decided to follow up on your suggestion of checking the system file drive. I asked myself «could my reliable Samsung Pro M.2 really have a corrupt section?»
Well the answer is YES. It did. It wasn't TI that recoded my backups, it was my defective drive that was not running the restored backups properly because of a defective sector.
So, not being one to fringe on adventure, after the chkdisk cleanup, I decided to reinstall the latest TI version 22510.
I created a backup and then tried a restore. No more corrupt index message. Like I had mentioned, I had the corrupt index message for a while and had always been able to restore backups. I thought that it was just an issue with latest version of Acronis and the the problem would go away as it had in the past with new versions of TI that had shown similar problems.
GREAT JOB! That's why I'd rather find solutions on forums rather than support tickets. Your patience and follow-up on this issue is impeccable.
Don't knock down the support on forums. Submit your arguments and follow-up on suggestions and comments. You never know, you just might learn something new. :)
Thanks.
Zardoc,
Thanks for reporting back. Glad to see that you were able to solve the issue. Thanks for marking the thread solved as well!
Edit: If you care to post back, did you note what chkdsk fixed? I would guess that one of the two MFT's on the drive had errors.
No, I'm sorry I didn't. I should have but I just wanted to fix this issue because I have a lot of work and my backups are very important for me. I wouldn't be surprised if it was the MFT's.
BTW, I tried the restore from the Windows desktop, works real nice. Especially when you test all kinds of software and Windows settings.
Next time, if I remember: get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
Will post
Thanks again.
Yes indeed, that would capture the output nicely. Thanks for that!