Direkt zum Inhalt

ATI 2010 Seems to Have Corrupted Our ATI 2009 Archive

Thread needs solution

I'm not completely sure why I'm posting this. The situation seems hopeless. Perhaps it's a way to express extreme disappointment that Acronis Support has not bothered to reply to the ticket that we submitted over three weeks ago. Maybe it'll spare someone else from the grief of data loss that we've suffered.

The full content of our support ticket follows, but to summarize:

  • Upgraded our son's motherboard, CPU, and RAM for Christmas
  • Switched from Windows XP 32-bit to Windows 7 64-bit
  • Installed ATI 2010 Trial to access our son's ATI 2009 archive
  • When attempting to mount, ATI 2010 gave a "Cannot assign a drive letter..." message
  • Searched Google regarding the problem and read a suggestion to mount in read/write mode, which worked
  • Copied some files over to the Win 7 hard drive (the only bright spot in this story)
  • Unmounted the archive and successfully ran a validation
  • Several days later the archive reported as corrupt. All attempts to mount/explore/recover/validate fail, using two different builds of 2009 as well as 2010 build 6053.

Thanks for reading this far. We've researched and tried just about everything, but any suggestions are welcome.

If only I had known then what I know now. Painful lesson learned: Don't store data files solely in a proprietary, compressed format like Acronis.

[Case 00462743] Need Help with "Corrupt" Archive

Greetings,

We've been using True Image Home 2009 to make incremental backups of my son's entire Windows XP Pro hard drive. The backup drive is a Western Digital "My Passport" USB 500GB hard drive. It's formatted as FAT32 and has .tib files numbered from 1 - 50.

We upgraded some of his hardware last week and did a clean install of Windows 7 64-bit.

Before upgrading his computer and wiping the hard drive we successfully validated his True Image backup several times in Win XP. There were no problems with the archive.

After doing a fresh install of Windows 7 64-bit, we downloaded the Trial version of True Image Home 2010 from your Web site to check out the new features before upgrading. We attempted to mount the archive but received an odd warning, something about "Could not assign a drive letter...". We received that several times. We then chose the option to "Mount the backup in read/write mode", and that seemed to solve the problem. We copied a few files over and then unmounted it.

For safety's sake, we chose then to do another validation on the archive with the True Image Home 2010 Trial under the new Win 7 64-bit environment and it was successful.

Now, a few days later, we are receiving "The file is corrupt" messages, both when trying to mount the archive or when using Windows Explorer on it. This happens on my son's Windows 7 64-bit system and with my Windows XP Pro 32-bit system. It also happens when using the Linux recovery CD on either computer. We receive the "corrupt file" messages and cannot access the archive.

We've run "chkdsk" several times on the backup drive and there are no problems with the physical media.

How did an archive that validated successfully numerous times suddenly become "corrupt"? Did mounting it in read/write mode with the True Image Home 2010 Trial somehow break something? We wouldn't have tried that if we knew this was going to happen.

Please help. My son is devastated over the possible loss of his data. We don't need a full restore, we just need to access it one time to copy over some precious data and can then start over.

Is there a way to make True Image (with a command-line option or something) disregard errors in the checksum process and just open the archive to retrieve pieces of data? Even if parts of the data are flawed we can accept that. Or do you have any tools to work with "corrupted" .tib files? Are there any other Acronis products that can help us?

We are very patient and are willing to try any suggestions you may have. We're very hopeful that you can help us get our data back.

Thanks very much.

0 Users found this helpful

Mike,

Have you tried separating the new Incremental image file created when you mounted the image in Read/Write mode from the previous image files in the "set"?

It's possible that the new Incremental is what's causing the problem.

For example, if you had MyBackupFile49.tib as the last one and mounting added MyBackupFile50.tib, rename that file to something else (tempMyBackupFile50.ti_, for example) and see if TI can then successfully validate the original set.

You should be able to tell which is the new Incremental file by the date. It should only be one file since I doubt you added 4GB of data when it was mounted.

Hello Mike and MudCrab,

Mike, I'm really sorry for the delays with the response. I have contacted the responsible person and your case will be handled as soon as possible.

Once again, please accept our profound apologies for the difficulties you have experienced.

Thank you.

Hi MudCrab,

Thanks very much for the reply. I've seen your name a lot over the last month while scouring the Internet for a solution.

We actually don't have a new incremental file, probably because we only did a read and not a write. The last set looks like:

AlexsNewHardDrive48.tib    12/19/2009    11:08 PM    4,194,304 KB
AlexsNewHardDrive49.tib    12/19/2009    11:12 PM    4,194,304 KB
AlexsNewHardDrive50.tib    12/19/2009    11:15 PM    3,476,652 KB

Using a data recovery program I can see a deleted file named "AlexsNewHardDrive51.tib" dated 12/21/2009 that's about 200 MB. I read somewhere that it's probably a temp file that ATI used while mounting in read/write mode. I can only recover the first 32 bytes of the file, not that it would have helped.

Anyway, thanks again for your time.

Hi Ilya,

Thank you for the courtesy of a reply, and for escalating my case.

I received an e-mail this morning from support. Their solution to my problem was a free upgrade to 2010, which is ironic since it's my belief that 2010 caused our 2009 archive to become corrupt. I'll continue working with your support team and will hope for the best.

It would be great if your company provided a tool to be able work with corrupt archives, if only to be able to salvage a file or two. I hope it's something your company will consider.

Mike,

Do you have room to create a copy of the backup image set? If so, it wouldn't hurt.

You can still try separating the Incrementals (start with 48, 49, and 50, as in your previous post) from the set one at a time and seeing if you can then access the image (go by the dates and make sure to rename all the files associated with that Incremental backup).

Just keep working backwards. Maybe the corruption isn't too far back and you'll be able to get the files out.

MudCrab,

Yeah, out of paranoia I made a sector-by-sector copy (not with Acronis) of the original USB drive to another USB drive so that I can experiment on the .TIBs without worrying about the originals.

I'll try your incremental set removal method... that's a fascinating idea.

Thank you again.