Corrupt Archive with TI9 bld 2337

Discussion in 'Acronis True Image Product Line' started by robognome, Feb 5, 2006.

Thread Status:
Not open for further replies.
  1. robognome

    robognome Registered Member

    Feb 5, 2006
    I am now running True Image 9.0 build 2337.
    Environment: windows 2k Pro sp4. AMD Sempron processor.
    The archive is stored with "normal" compression.

    My first attempt to restore my C: drive using an older build of TI9 rescue disk (build 2302) resulted in the "corrupt archive" message and additionally it completely deleted my c: partition.

    Since my installed copy of true image was destroyed when the partition was deleted I went to a 2nd pc and installed the latest build 2337 and used that computer to build a brand new rescue CD. I checked the image file in question from the windows environment (check archive) and found no errors - I also mounted the image and browsed through it without problems.

    Inserted the rescue CD (from the 2337 build) into the first computer and proceded to restore accross the network from the 2nd pc above. About 30 minutes into the restore it reported a "corrupt archive". I mounted the image locally on the first pc and used Check Archive. It immediately reported "corrupt archive". I double check the build in the rescue cd about box and it said build "2337".

    The image is stored on a DVD ROM. When I copied it to the hard drive on 2nd pc the ran Check Archive in the windows environment it reported no problems. I was also able to mount the image and browse it.

    Only thing I can think to do is to install the hard drive from the 1st pc into the 2nd pc as a second drive then us the Windows native version of TI9 (2337) to restore the partition there, then reinstall the hard drive back into the 1st computer. This may result in some odd drive letters, but I cant think of anything else to try.

    Will the above work or will my MBR be completely mangled? Your suggestions or help would be welcome at this point.
  2. Acronis Support

    Acronis Support Acronis Support Staff

    Apr 28, 2004
    Hello robognome,

    Thank you for choosing Acronis Disk Backup Software.

    Could you please do the following?

    - Copy your image archive from DVD to the second computer's hard drive;

    - Install this hard drive into the first computer as a second (slave) disk;

    - Boot the first computer from Bootable Rescue CD created using the latest build (2337) of Acronis True Image 9.0;

    - Try to restore\verify the image archive once more and inform us about the result.

    Please boot the first computer from Bootable Rescue CD created using the latest build (2337) of Acronis True Image 9.0 once more and create Linux system information (sysinfo.txt) as it is described in Acronis Help Post;

    Please also create Acronis Report in the way described below:

    - Download and run Acronis Report Utility;
    - Select the "Create Bootable Floppy" option;
    - Insert a blank floppy disk in the A: drive and proceed with creation of the bootable floppy;
    - Boot the computer from this diskette and wait for report creation process to finish;
    - Collect the report file from the floppy.

    Please submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with the solution.

    Thank you.
    Alexey Popov
  3. robognome

    robognome Registered Member

    Feb 5, 2006
    Thank you Alexy. I ended up solving this one. My system crash was not cause by a corrupted file system as I originally though.

    It turns out the motherboard/cpu was damaged - giving me intermittant errors, reboots and "corrupt" file.

    I replaced the motherboard and cpu and I was able restore the disk image on the first try (this morning), reading it accross the network (I took about 7 hours)

    Now I'm considering gigabit ethernet. Heh.
Thread Status:
Not open for further replies.