Can't make a good backup on USB connected hard disk

Using True Image Home 2010. Win7 64bit. Hard drive (PATA) in a USB 2.0 attached case.
I've been trying to get a backup archive onto the external disk that will also validate. I got one base to validate twice (yesterday) but the incremental would not. And today the same base will not validate. Flakey interface? Chkdisk says the external disk is fine.
So I upgraded to ATI Home build 7046 but it agrees that the existing base and incremental do not validate and a new base created with v7046 also does not validate.
I have an incremental archive on the System disk and it validates just fine.
In all cases I have been using the on-line application to create the archives and to validate them.
I believe I read somewhere that I should try creating the backups and do the validations with the bootable recovery disk.
Is that really something to try?
Since I updated to a newer version of ATI, do I need to create a new recovery disk?
--Larry

- Se connecter pour poster des commentaires

Well, since none of the backups I've done on the external disk will validate, I will try some things:
--Create a new recovery disk
--Try validating the existing backups on the external disk running from the recovery CD.
--Try creating and validating new backups on the external disk running from the recovery CD.
Larry
- Se connecter pour poster des commentaires

I decided to try a different external disk that I have been using successfully for years on my other PC.
I got a full backup and it validated. That's good.
I'll validate it again tomorrow to make sure it stays good. I'll do that because one of the backups on the other external disk validated OK one day but failed repeatedly the next day. I'm thinking the external disk (likely the enclosure) that I've been trying to use is flaky so I will replace it.
I did today's work using the on-line application, not the recovery disk.
--Larry
- Se connecter pour poster des commentaires

Be aware that flaky memory chips can be one of the major causes of failed validation.
- Se connecter pour poster des commentaires

I forgot to mention that I ran more than one pass of memtest86+ V4 yesterday on that PC. No problems!
- Se connecter pour poster des commentaires

Larry,
I am the first to admit that I do not know what the solution might be for you. I can only suggest things to look for.
1. Plug the cable into the rear of computer directly into motherboard. Do not use a hub. If possible, disconnect other usb devices.
2. Try a different usb cable.
3. Under the backup options, one option controls the write speed used during the backup. You may have some success reducing the write speed.
4. A memory check usually needs to run overnight or at least for several hours.
5. A backup validated via the TI REscue CD has the best chances of a successful restore.
6. Try a different usb enclosure. Check item 7G inside my signature index below.
- Se connecter pour poster des commentaires

larrymcg wrote:I forgot to mention that I ran more than one pass of memtest86+ V4 yesterday on that PC. No problems!
With memtest, the word is that sometimes you have to run it overnight before problems show up. I've never had to run memtest at all ... just going by what I read.
- Se connecter pour poster des commentaires

The more you run it, or any diagnostic program for that matter, the more confidence you have that there are no problems. Running a diagnostic program is usually not the same as running the OS. In the case of Memtest, there is no concurrent disk activity, data for exotic graphics being written to the video system, more draw on the power supply, etc.
I have had bad memory detected after several good passes which be due to getting everything up to certain operating temperature.
My belief is that for a very intermittent fault it is more likely to be detected by random data tests than the various bit patterns.
It's pretty easy to fire up the test and let it run overnight for good measure.
- Se connecter pour poster des commentaires

I've done another incremental on the new external disk and it validates too. I'm pretty sure it is the flaky external enclosure on the other one.
I've always been a bit suspicious of it -- it is quirky in multiple ways. For example, it take a long, long time to mount (show up in Windows Explorer) after connecting it. And if you start or restart the system with it connected and powered up, it doesn't show up at all and once Windows got bent out of shape and tried to resinstall drivers for it after a restart and then claimed the device was failing and ......
So, I'm throwing that turkey OUT! and will get a new enclosure.
--Larry
- Se connecter pour poster des commentaires