Run List Corrupted when restoring .tib file

Attaching acronis report.

*EDIT* I was advised via the live chat support feature to run a snapAPI update, then reboot, then attempt to restore the backup via the Acronis version in Windows rather than the bootable version. I did that, the recovery starts for a few seconds, then lets me know it needs to reboot in order to continue.

That doesn't make any sense. SnapAPI is used for backup not for restore. Installing SnapAPI potentially change your backups.
Recovery is always better done from the recovery CD. If Acronis were to recommend to do in Windows, people wouldn't be able to restore their system after they lost their disks...

The runlist corrupted points at some disk issues. Try to find a disk diagnostics tool from your disk manufacturer, boot on a CD with the tool on it and let it run a full analysis of the disk.

I beat my head against a wall a second time with the chat support. He said I should just run chkdsk again. He suggested that I just move the backup to another external drive. I told him I don't own another drive large enough to hold it. I only own one backup drive.

He then said to try running memtest. When I told the analyst I ran it a short while ago because my RAM is brand new and I ran it immediately after installing it he became rude and said well if you're not going to follow our steps I can't help you I need to send a ticket to the next level of support. He claimed that the version linked on Acronis' site (which links to memtest.org) is a "special exclusive" version. I can't believe anyone would attempt to insult someone's intelligence like that. I'm not someone that thinks computers run on magical pixie dust. Don't treat me like that.

Pat, thanks for the post. What they said didn't make any sense to me either, but I followed the "support" instructions because I assumed the people running them would have at least basic knowledge of how the product works. My backup was not stored on my C drive, so would SnapAPI still risk changing the backup? I hope not.

It's a stock HP ENVY m6-1105dx laptop. The only thing I've done is take out the manufacturer 6GB RAM and put in 16 GB of corsair RAM. It's also only about two months old.

But for the sake of argument, let's say I go buy a brand new hard drive for my laptop. Will this backup even restore to it or is it locked to the original drive?

I'm actually going to start manually reinstalling and reconfiguring everything now because I've given up hope of a full restore. So far this has left a horrible impression on me for Acronis as a product. Had the backup validation tool thrown any errors, I would have known not to go ahead with the factory reset just yet. Oh well. I won't make the mistake of trusting this company for anything again.

There is no way installing snapapi would change an existing backup or file. It is just a driver that Acronis uses. This is why the instructions of the support agent don't make sense to me.

When the backup is on the backup disk, and you hook up this disk to another computer with ATI installed, can you double click on the image and explore it normally? Can you mount the image? If you can, your backup is fine. The suspect would be the original disk.

With a disk and partition backup you create an archive with the entire image of the disk, provided you have included all the partitions in the backup. You can restore this to a new disk on the same computer and your computer is as before.

Yes I can mount the image and get to any files without issue, even on the original laptop it was taken on. So that's a good sign that the backup is fine. My issue isn't with the data files (they're backed up elsewhere), it's the installed applications, OS, configurations, etc. I spent a good amount of time on that and re-doing it I'd likely miss a bunch of things and be tinkering with it for weeks until it felt right again.

I found a HDD scanning utility from Hitachi (yes the drive is a Hitachi) which has been running for the past few hours. It has a few different tests so I'm going to run each one of them, then ANOTHER chkdsk /r on my local C drive, and then try the backup again. This will probably take at least 2 days because I won't be home most of tomorrow. If all of this fails I'm going to get back with HP and get them to send a new HDD too. Their wifi card was already screwy, now it seems like the HDD isn't worth anything either, which is really a shame since I thought I found a good laptop.

Thanks for the help Pat. I'll post here again with an update.

There are some hidden partitions on the disk, if the problem is in one of them, that might be the source of the problem.

hitachi's tool told me there's no errors, ran chkdsk again overnight, tried the restore again and failed again. same error.

A guy at work has the MRI disc that geek squad uses which is a pretty good diag tool. I'll run that to test the HDD when I can.

I actually did try restoring one partition at a time, every one of them restored successfully but the C drive, so the problem isn't likely on the hidden partition sections.

Yes I can mount the image and get to any files without issue, even on the original laptop it was taken on. So that's a good sign that the backup is fine

It it's not. It may have had a filesystem error that went unnoticed into the .tib during backup, or had something that to the Trueimage looks now like filesystem error after the backup but really isn't. Mounting works because it doesn't access all the files - only the ones you try to access. As you can recover your data this way it seems that you will give up and reinstall your applications before you get this recovery issue resolved by Acronis.
You may try to mount this backup in r/w mode, run chkdsk on the mounted drive, unmount it (you will get a new incremental backup to it but to be sure I'd make a copy of it before) and then try to recover from the resulting increment. But there is a chance you get the same error when chkdsk access the problematic place.

dev-anon wrote:

It it's not. It may have had a filesystem error that went unnoticed into the .tib during backup, or had something that to the Trueimage looks now like filesystem error after the backup but really isn't. Mounting works because it doesn't access all the files - only the ones you try to access. As you can recover your data this way it seems that you will give up and reinstall your applications before you get this recovery issue resolved by Acronis.
You may try to mount this backup in r/w mode, run chkdsk on the mounted drive, unmount it (you will get a new incremental backup to it but to be sure I'd make a copy of it before) and then try to recover from the resulting increment. But there is a chance you get the same error when chkdsk access the problematic place.

Crap. Bad news all around. Good suggestion though, thank you.

I'm running the chkdsk on the image of the backed up C drive now. We'll see how it goes.

RECOVERY SUCCESSFUL!!!

chkdsk on the mounted backup did it! it found some errors in the boot sector of the image and repaired them. next backup attempt worked flawlessly. you saved me so much you have no idea. thank you thank you thank you!!!