Acronis True Image 9.0

[kuba]

Whenever I check my image of the HD made, i get an error message of 0x70020, and that it's corrupt.
Anyone else have this problem?
Apparently Acronis' response time to this issue, isn't all that great.
Anyone know a why this error message occurs or how to get around it?

 

[BlueWeasel]

Did you backup the image to a different partition on the same HD, a different HD, or CD/DVD?

 

[kuba]

Differnt HD...and also made a copy to my external...guess i'm better off leaving it on my crive, then taking the copy to my external?

 

[dunkster]

I had the same problem - image verification indicated bad image - though I use Terabyte imaging software.

The problem was caused by a bad sector on my hard drive.

In my instance (WD hard drive), WDDIAG utility found and repaired a bad sector.

Hope this helps!

 

[weeber]

kuba,

I've had the same problem with TrueImage. If find that if I do a backup and try to use the computer for something else (like surf the web, email, etc.), it will sometimes come up as corrupt. I usually end up just letting the backup go overnight and it comes out OK.

 

[BlueWeasel]

Alternatively, have you tried creating the image outside of Windows using the TI boot CD?

 

[kuba]

Dunkster funny enough I remember you posting about Terabyte imaging before in a previous thread I had made.
I'm definitely going to look into it, so thanks again.
Forgot to mention Dunkster, that I 0-wrote my WD HD with their diagnostic tool, then formatted (full, not quick NTFS).
So I didn't have any bad sectors, whatsoever.

Weeber, I found out the problem, when doing the compression, make it either normal or none, that's it.

BlueWeasel, but isn't that the point of TI, to be able to do all this without a bootable? Acronis shouldn't make claims if it's not going to work right. hehe
But I'll try doing a backup through the bootable as well.

Do you guys recommend I save the backup on the same drive, that I'm ghosting? Or is copying it to my other internal drive okay?

 

[BlueWeasel]

Originally posted by: kuba
BlueWeasel, but isn't that the point of TI, to be able to do all this without a bootable? Acronis shouldn't make claims if it's not going to work right. hehe
But I'll try doing a backup through the bootable as well.

Do you guys recommend I save the backup on the same drive, that I'm ghosting? Or is copying it to my other internal drive okay?

Actually, I always do all of the backup and restoring using the bootable CD. It's probably overly anal, but it's just a habit that goes back to when I ran Norton Ghost off a floppy disk. *shrug*

Save the backup wherever you prefer...it shouldn't make difference. I prefer to have the backup on a different HD (for speed) or optical media.

 

[dunkster]

Zero-writing does exactly what you would expect - writes zero to over-write everything on the drive.

Zero-writing does nothing to check for bad sectors - it simply writes zeros to all sectors with no attempt to confirm whether a sector can be read successfully.

A drive with a bad sector (weak read/write magnetic properties) will still have that bad sector, after a zero-write.

 

[kuba]

Did not know this...so how does one check for bad sectors?
During the full NTFS format?

 

[aidanjm]

I switched from Acronis to Paragon Drive Backup.

 

[dunkster]

At the WD site, download the 'Western Digital Data Lifeguard Diagnostics' for DOS.

Read instructions for installing on either bootable floppy or CD/DVD.

The diagnostic will test magnetic read/write properties of every sector on the drive. If a weak sector is found, the utility will attempt to read data from the sector, write the data to known-good sector, and mark the bad sector to prevent re-use of the bad sector.

Hope this helps!

 

[Auric]

I don't want any doubt that an image will be good so do not trust doing so from Windows. Indeed, after trying Acronis I continue using ye olde Binary Research/DOS based Ghost. Imaging volume C: to +RW only takes minutes anyway. For disc checking, manufacturer provided utilities may be useful, but Windows chkdsk command does the job. For bad sector scan with recovery, run:

chkdsk c: /r

However, a file system check is a good idea and relatively quick so may as well be done at the same time by adding the /f parameter:

chkdsk c: /f /r

 

[JackMDS]

I thing that TrueImage is a great program, however, I notices that when the program backup to a slow medium (like CD ROM) or restores from a slow medium too many times it generates corrupted files.

Thus as a policy I use a computer with two HD Mobile racks. I put the HD to be backed or restore as a secondary drive and use the main drive for the File storage. When not actively needed I burn the .tib image to a CD/DVD and delete it from the HD. That adds some time to the process, but for for the long run it is more secure and saves time.

:sun:

P.S. I also notice that while Restoring through a Network works well, Backing up through a Network yields many times corrupted files.

:sun:

 

[dunkster]

CHKDSK does a decent job - and also does some file-structure checks that WDDIAG does not do. WDDIAG tests magnetic read/write properties only.

However, in the bad sector instance that I noted above, the sequence was like this:
- Repeated byte-for-byte image verification failures.
- CHKDSK utility reported the drive OK.
- Image verifications continued to fail.
- WDDIAG found and fixed a bad sector in the region of my Windows partition.
- Image verifications have been fine since (about a year).

I suspect the difference is that the WD utility has finer control of head-read-sensitivity (for a WD drive) than does the general Microsoft utility.

I suspect this is true for other utilities as well (Maxblast best for Maxtor drives, Seatools best for Seagate drives, etc.)