Image Corrupt when Using Rescue CD but Fine when Checked in Windows?

I have been using TI 9 B2337 doing HD to HD images and restores with no problem for a while. Last night I made an image of C while in Windows to my second SATA HD. I always Verify. Using the CD version B2337 I reloaded an old image of C and ran it.

Today I booted up the CD to restore the verified image I made last night. I did not do a Verfiy before restore since I verified the image last night but I ticked the other box to check the file system after restoring (or something like that). I started the restore and went away to do something else. I came back and I had the infamous archive corrupted message on my screen. I then verified the image using the CD version and it was OK. I then started the restore from the CD again but this time I requested a verify before restoring. The C partition showed as unallocated so it had been wiped by TI. Since I wasn't paying attention to my PC I don't know exactly when the corrupted archive box appeared. I successfully restored the partition.

I subsequently restored this same archive again later in the day with the CD version with no problem. I did a verify before restore for good measure.

Somethings a little flakey somewhere.

 

Hello msanto,

I can assure you that at least the issue with the incorrect image restoration scenario has certainly been fixed. The point is that if you select the "Check backup before restoration" option an older builds of Acronis True Image 9.0 used to create the following scenario: Deleting partition, Check Archive, Restoring partition while the correct one is as follows: Check Archive, Deleting partition, Restoring partition. The latest build (2337) of Acronis True Image 9.0 always creates a correct image restoration scenario (both from under Windows and in rescue mode). However, there is still a chance to accidentally loose a partition that is being restored. To be more precise, the problem may arise if you have not selected the "Check backup before restoration" option prior to starting the image restoration process. In this case Acronis True Image 9.0 may "find out" that the image archive is corrupt while being in the middle of the image restoration process and thus having already deleted the destination partition.

Thank you.
--
Alexey Popov

 

There are at least two (2) issues with Acronis v9.0.

1. It does not restore correctly to SATA drives.

2. It consistantly says archives are corrupt when restoring from
external usb Hard Drives when in fact the image is not corrupt.
I proved this by copying the image to a second internal IDE
hard drive and then doing a restoe with no problems.

Most versions of Acronis since V6 have had problems. The design of
the software is fine, but the actual usefullness in restoring is sub par.

Technical support consistantly asks users of their product to do
the testing and debugging for them. Testing and debugging is
the responsibility of the software creator.

I have been unable to restore to a SATA drive and boot the restored
image. I have tried this 3 times on three different machines.

The following is the message I get attempting to boot from
a restored SATA drive;

"Windows could not start because of a computer hardware configuration problem.

Could not read from selected boot disk. Check boot path and selected hardware.

Please check the windows documentation about hardware disk configuration and your hardware reference manuals for additional information."


When attempting a restore to an IDE drive from a USB hard drive
I consistantly get the following message;

Image corrupt

If I copy the image to a slave internal hard drive, the restore
functions properly.


Since TI is unreliable, I will opt to stop using it.

 

Hi snifferpro,
I think you have already had some helpful replies in another thread which you had also Hi-jacked. I note that you have also started a new thread. This is perhaps what you should have done in the first place as it makes queries easier to follow and answer.

Perhaps a Moderator will combine your postings and answers in one thread so we can all see where we are at?

Xpilot

 

Sorry to jump into this thread when I started another one with a similiar theme (Acronis TI 9.2337, disappointing results). I'm new to the forum and didn't see this thread

I have had similiar issues as follows:

Full image of my HD (probably not build 9337 since it was created a few months ago)---multiple incremental back-ups. My main 120GB drive failed this weekend...no problem since I planned for such a disaster. I decided to buy a new 160 GB drive. I used a boot disk (created with the latest build) to restore and resize the image to my larger drive...no luck as the "image is corrupted" I ran the boot disk and checked the image..no problems detected. I then had another 120GB drive and restored (without resizing) to that drive...success. I then cloned that drive to my larger 160 GB drive...success. What the heck?

I was therefore able to restore an image to a SATA drive as long as that drive had the same size partition as the image. Cloning across different sized SATA drives worked fine. Any explanation for these observations?

Rick

 

Where is that option? I can't find it. Of course, I don't want to go through an actual restore so maybe it's somewhere in that process.

 

Hello msanto,

Please note that you can find the detailed instructions on how to use "Check backup before restoration" option in chapter 5 and particularly section 5.3.10 of Acronis True Image 9.0 User's Guide.

Please also take a look at the attached screen shot.

Thank you.
--
Alexey Popov

 

Hello rborge,

Thank you for choosing Acronis Disk Backup Software.

Please take a look at my reply in this thread which you have started recently.

Please also try to avoid duplicate posting in the future.

Thank you.
--
Alexey Popov

 

hi Alexey Popov, i think i had the same problems as described here in this thread - and at first: sorry for my english, but i'm german.

this happened: only about 5 or 6 weeks ago i made a so called "sysprep"-image from a standard wxpp-sp2-workstation with a ti8german-937-rescue-cd (trial), because i often had to test systems like that. after much experiences with the at start so buggy version 9 from ti (which i then bought), german support recommend me at this time to use for security the ti 8 rescue cd - so i did; when i read here, that the last ti 9-german build 2337 seems maybe not as buggy as formerly 9er-builds, i switched to this version;

so a few hours ago i want again to restore this 8.0-937 sysprep-image on the workstation as i did it the last weeks so often; the image-file is on a dvd and it is only one file from 1.6 gb size (max. compressed with ti 8-937). on trying to restore this image with ti german 9-2337 rescue cd, ti says (after deleting all partitions, which i want, but surely not in this way) ..."archiv beschaedigt!" (image corrupted).

on my own workstation i installed ti 9-2337 german --> i could mount the image, could get files out of it and so on; best is, that with the ti 8-937 german rescue cd i then tried to restore exactly this dvd-image ...and it happened fine as it ever did...

i phoned german support and told him the story ...the supporter said: where is the problem, you must use for an image from version 8 the same version from the rescue cd or otherwise you first have to create a new image with the ti 9-2337 rescue cd and then it should work on restoring with the ti 9-2337 rescue cd... i ask him: so why i can restore an ti 7 (maybe 6!!??)-image with this ti8-937 rescue cd and not with the ti 9-2337-boot-cd!!?? and, for all, i bought only version 9 from ti and i don't want in future to take even all the time an image and the exact version from the rescue cd, which made this image ...some people called it downwards compatibility in such scenarios, for all with a backup software! ...he said, i MUST made at least all 4 weeks a new image, for all when using only rescue cd and when there is coming out a new release... i said could you please try to reconstruct exactly this bug on using the ti 9-2337 rescue cd ....and he says: with the ti9-2332 (or something like that) he could restore an ti8-image, to trying my scenario, he had not the time. best was, as i said: so could you please at least told the acronis developers, that in a future build the so called "abwaerts-kompatibilitaet" (downward compatibility in english!?) for images, made from different version and/or builds should be given, so that i could restore old images even with new ti-rescue cds... he really answered exact this:

"customers had not to tell our developers what should in acronis true image or not"!!!

it's really unbelievably!!!

as i said, when i could not absolutely reliably hold an old image/backup so why is it called a backup software!!?? as he told then: why is there for example a microsoft service pack 2 for windows xp, service pack 4 for windows 2000 and so on...

ok! could you please send me a mail when this problem with the ti 9-2337 rescue cd have solved, i said? he says: you are a registered user, and therefore you get automated notifications when there is a new build out ...but i don't think, that this feature, that you want, is implemented in future 9er-builds...

...i said: ok! i understand, you "pushed" me by all force in "ghost" direction or something like that ...and, nevertheless, have a nice day ...and i terminate this expensively (0.69 cent per minute!) telephon call.

a very very frustrated (formerly!!??) acronis ti user

 

I'm seriously looking at other options. Frankly, even restoring from network is buggy. I have found a FREE imaging program that uses BART's PE to boot; I think it's the Linux boot that causes the TI problems. The freeware program has no problem seeing the external hard drive.

Of course, there's no incremental backup, but I can live without that. I need something that works! Acronis should be embarassed that freeware can do what they can't.

 

hi msanto,
could you please send me a private message with informations about the FREE bartpe-plugin/the FREE imaging software!?

after my experiences i made the last 3-4 months ago with the acronis true image-software - and at first i was really pretty engaged on "betatesting" the version 9 of true image (especially rescue cd), in cooperation with the german acronis-provider, and i spend a lot of my WORKING-time with evaluating failures, insufficiencies, bugs and so on, to make sysinfos by sysinfos, although for this "betatesting" for a paid licence i ever used on this time the same virtual pc-envirenment and installation... ...after all this experiences i gave up.

ti 8 since about build 850 and for all later builds is (but in ost cases only the rescue cd) in relation to what it costs, a really, really great and helping software, especially for developers, testers and so on. since the new version 9 - and especially on using the rescue-/linux-boot-cd, you could also play lottery, gamble. and this really for each new build, what rolls out!

acronis did a great job over all for 2-3 years ...but now: sharp descent!

it's a pity

 

I found a solution for my situation and wanted to share it with you.

My system is an ASUS A8N-SLI Mother board using an AMD 3800 chip bios version 1001. True Image version 8 or 9.2337.

For several months the system would crash (blue screen) for various unrelated reasons. It happened more and more as time went on. I was guaranteed a crash if I used True Image AND verified the backup. All backups were labeled as corrupted. However, in a pinch I had to restore and it worked fine from CD.

For various reasons I began to realize that the problem might on the mother board (memory or chip set, possibly video but not likely). I downloaded memtest (http://www.memtest86.com/) and always was able to find errors with memory. I then replaced the RAM, same errors. This meant that it wasn't memory.

I finally, took a risk (to me) and updated the bios and now, no memtest errors, no crashes, I can backup and the backups don't appear currupted. Everything is working perfectly.

Here is what I suspect happened. Some time during one of the 2005 Windows updates, windows started using some kind of programming in the I/O that caused the bios on my computer to fail.

NOTE TO SUPPORT: I've been going back and forth with you for several months on this issue (ticket 406094). You obviously are not aware of this problem. Hopefully this will help others overcome this problem.

 

Ummm, as I recall, Bios 1001 is not compatable with an Athlon 3800. You were gradually creating more and more corruption in your Windows Installation and enjoying the benefits of system instability along the way.