ACronis True IMAGE 9 and backup corrupt message

Discussion in 'Acronis True Image Product Line' started by Emolle, Dec 7, 2005.

Thread Status:
Not open for further replies.
  1. Cat-21

    Cat-21 Registered Member

    Feb 7, 2005
    I have been seeing this problem with many users including myself. Testing on 4 different machines I became concerned because none could restore and archive, all images reported corrupted. I had only 4 machines in the test, 1 Gateway, 2 Dell, 1 White-box, If you google it, you will find many other users talking about it.

    Again, I wouldn't change any hardware until this release matures a few versions. These users have no other problems with these PC's other than using TI 9, doesn't that seem a little odd? Usually when I'm having hardware issues more than one area show signs of deterioration, not just TI.

    TRY THIS TEST: If you have another PC, test TI 9 on it. If you find that your other PC also fails on restore, chances of multiple PC's with bad RAM/mobo seems far-fetched. If you find instead that the other PC succeeds in restoring, then check into the hardware. Wouldn't it upset you if you bought a new mobo and/or RAM and found that your image was still corrupted? Be safe than sorry, it doesn't hurt anyone to wait for the next release.

    DECIDE FOR YOURSELF: Use the forum search above and check "image corrupt". There are many more users with this problem unlike what was said in the previous message, check for yourself, don't take my word for it. Also the previous message is not accounting for users like myself who called support on the phone. What angers me is this "head in the sand" attitude about it. Admit there's a problem and move on to "fix" the problem. The frustration created by people telling users "nothings wrong, you're all are crazy, just swap out your RAM and Mobo and reinstall Windows" really angers me. Read the messages in this thread alone, I'm not the only one saying this. Why am I the "bad guy"?
    Last edited: Apr 1, 2006
  2. MSprecher

    MSprecher Registered Member

    Sep 22, 2005
    What is really annoying is that even though I had been in close contatc with Acronis Support from September 05 to February 06, having sent them all information about my hard- and software as required in

    "Could you please do the following?

    - Open Start\Programs\Accessories\System Tools\System Information;
    - Select System Information;
    - In Action menu choose Save As System Information File;
    - Send us the file created.

    Please also make a new sysinfo.txt file and send it to us."


    " Could you please boot from the Acronis True Image rescue disc and

    press F11 key when the "Starting Acronis Loader..." message appears? After you get the "Linux Kernel Settings" prompt, please remove the "quiet" word, click on the "OK" button and wait for # prompt to appear. Please insert a diskette into a floppy disk drive and issue the following commands:

    cd tmp
    mkdir mntdir
    mount /devfs/floppy/0 mntdir
    sysinfo > mntdir/sysinfo.txt
    umount mntdir

    Send us the sysinfo.txt file from the diskette."

    Nobody was able to give an explanation of the strange behaviour (Corrupt image report) of TI 9 when checking images.

    It was myself who by incident found out that the background process of Symantecs Internet Security Professional 2002 was the reason for all.

    I would recommend to customers and Acronis to have a closer look at the software fiddeling around in the background of the systems during the backup AND verifying process. Never ever I would replace hardware in a system for TI when memtest is ok and everything else is working fine.

    It is high time for an update of TI 9 where the issues in question are resolved.

    Matthias Sprecher
  3. seekforever

    seekforever Registered Member

    Oct 31, 2005
    Nobody said you were the bad guy. I obviously don't know the content of all the posts on this forum but I don't recall swapping out the motherboard to be a common recommendation at all.

    We both know that the corrupt image problem can only be software or hardware. Software can either be the TI implementation or it can be other vendor's software causing conflicts.

    My only point is that when somebody has a problem then don't rule out the hardware. In your specific case of having multiple machines fail, I agree, I would not put hardware at the top of my list as a probable cause. However, TI runs on my 2 PCs with no software problem and I often backup and restore while trying new software. The problem I rarely had seems to have been a SATA cable. I have also tested it on my old PC and it worked fine on it too.

    The recommendation to run the machine with Memtest86+ or other memory diagnostic doesn't constitute running down to the store and buying new RAM. Trying one stick at a time if possible also doesn't mean running out an buying new RAM. I have seen recommendations to test but I don't recall any, and I don't know them all, to advise the person to buy new RAM just to try.

    I have been around computers of varying sizes too long to say that memory problems always show up no matter what you are running. It just isn't so particularly on systems where a lot of it isn't excercised often. At the risk of repeating myself, a bad bit in a jpg, mpeg or other data file is not likely to ever be noticed. A single bad bit in an image will give a corrupt message.

    Do I think TI itself is error-free - absolutely not. Did they blunder releasing it too soon -darn right. Do I think there are aspects suffer from weak design, yes, the Linux environment and its lack of USB drivers is certainly an area. Interestingly, TI8, which is often held as the gold-standard for backups seems to have its own share of corrupt archive problem as well.

    All I am saying is don't rule out hardware as a potential cause not that the software implementation is perfect.
  4. Menorcaman

    Menorcaman Retired Moderator

    Aug 19, 2004
    Menorca (Balearic Islands) Spain
    Well said seekforever :).

    I agree that it's highly unusual for a motherboard to be the reason for corrupt images but, as this <much earlier post by gwilki> proves, it can't be ruled out altogether. Mind you, I'm not saying that this is the case for Cat-21!!

  5. Cat-21

    Cat-21 Registered Member

    Feb 7, 2005
    thanks guys, when I first started to post about these errors, it was blown off a "wild speculation" but then days after I made the comment, messages of users with my same corrupt image issue began popping up left and right. I agree that I wouldn't rule out Hardware 100%, I just worry that when you have novice users entering a forum where alot of ideas are thrown around, one of these ideas could become misunderstood.

    I wouldn't want one of these newbie-types to waste his hard earned money on hardware until sure. I work in I.T. and if you do as well, you know that users can take something you tell them and do exactly the opposite as they're inexperienced in dealing with complex matters concerning computers. I really hope they fix these problems as the potential for what could be is immense, and that is what motivates CAT-21 to write the things I write, sorry if it's currently "anger".
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.