Salta al contenuto principale

File I/O backup errors

Thread needs solution

I am running True Image Home 2009 build 9796 on an Win XP SP2 machine. The program seemed to run automatic backups fine early on, but fails consistently now for the better part of the last 6 months. It either fails to do the backup at all (usually) or completes it with errors. It also seems to do full rather than incremental backups (the backup files are huge every time) and a couple times it filled up my 500mb external backup drive. This software looks amazing in its potential but in reality has been difficult to get it to work successfully. I'm hoping it's a simple fix from someone who knows the software better than I do. The latest error message from the log is attached.

0 Users found this helpful

Replacing my previous and deleted comment...

I am either running into issues with the new AVG antivirus 9, or with the drivers for the USB2 on my backup computer system. Here is the weird thing. TrueImage was failing with I/O errors while trying to backup to an external USB2 hard disk. I thought that the problem was with TrueImage. So instead I had TrueImage back up to the computer's internal hard disk and that both completed and verified successfully. So then I tried copying the 4.7GB tib files from the internal hard disk to the USB2 external hard disk. Guess what? Copying failed. So its either a need to update the USB2 drivers for the motherboard, or I need to update its BIOS, or both. Or, of course, it could just be that the motherboard itself (SiS chipsets) is crappy.

Note that this testing is on a new motherboard and new internal and external hard drives onto which I want to build up a clean XP system and then reinstall only the software and data which I actually use. I am going to do more testing of TrueImage (I have 2009) on other computers which I have, just to see what the root cause of any I/O error message issues are. Right now I am suspecting that it is not TrueImage2009 which is causing my failed backup error messages. Instead I think it is related to the underlying hardware and OS drivers.