cannot clone O/S hard disk using Acronus TrueImage

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

I cannot clone my O/S hard disk (1) as Acronus TrueImage reports errors.
TrueImage has trashed both backup destination hard disks (2 and 3) attempting to clone from hard disk (1); these disks now just appear as empty "Recovery" partitions in Windows explorer; so I have lost both old backups trying make a new backup. :(

It reports: "Acronis True Image failed to move your data because your new hard drive does not have enough free space to complete the operation. The reasons follow":
"1. Some of your partitions contain errors. We recommend you reboot your operating system and correct these errors"
"2. Your new hard disk is much smaller than the old one. Make sure have selected the correct old hard disk. If you have chosen the "As is" option on the previous page , go back and try to select another option"

1. I cannot run "chkdsk /f" (or C:, properties, tools, checknow... file and sectors) to fix errors as it reboots and reports "Autochk cannot run due to an error caused by a recently installed software package". I have no idea what software package it is talking about. I thought it might be Kaspersky but I installed that many months ago and have cloned the drive a few times successfully since then. Some users have reported this problem when using AVG and temporarily uninstalled it to get chkdsk to work.

1. I cannot run "sfc / scannow" to fix Windows 7 system files as it reports "Windows Resource Protection found corrupt files but was unable to fix some of them." i.e. CBS.log: "tcpmon.ini"; source file in store is also corrupted.

2. backup disk (3) (298GB formatted) is not smaller than source disk (1) (270GB used) so this is being mis-reported by TrueImage, unless it needs an extra 28GB or so for the cloning process!?

I've tried other TrueImage versions without any luck:
Acronis True Image WD Edition
Seagate DiscWizard

Apart from TrueImage, chkdsk and sfc not working; my computer is not showing any signs of problems or errors messages. Given the above problems, please can you suggest how I can:
1. clone my O/S hard disk so that I have a backup before I try anything else
2. repair my O/S hard disk by overcoming the chkdsk and sfc problems above

Thanks for your help :)

Mon, 07/22/2013 - 20:14
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 51
Comments: 3768

My best advice: Do not Clone! Instead, do one extra step and create a full disk Backup to an external drive. If ever you need to return to that image state, you would do a full disk Restore/Recovery.

There is rarely a need to Clone. Really, Backup is safer and more flexible. Many users encounter problems Cloning which they would not have if they had instead used Backup.

1. Don't use Clone. Do a full disk mode Backup, selecting the entire disk, and a Restore. The end result will be the same as Clone, but with many advantages.

2. Check out the many user guides and tutorials in the left margin of this forum, particularly Getting Started and Grover's True Image Guides which are illustrated with step-by-step screenshots.
29618: Grover's new backup and restore guides http://forum.acronis.com/forum/29618

A full disk backup, selecting the disk checkbox rather than individual partitions, includes everything. It includes everything that a clone would include.

The difference is that while a clone immediately writes that information a single time to another drive, a backup is saved as a compressed .tib archive. As such, multiple .tib archives may be saved to a single backup drive, allowing for greater redundancy, security and flexibility.

Once a full disk image .tib archive is restored to a drive, the result is the same as if that drive had been the target of a clone done on the date and time that the backup archive was created.

Clone is riskier because we've seen situations where users mistakenly choose the wrong drive to clone from and to, thus wiping out their system drive.

As you seem to have disk problems, you must run chkdsk /r (not just /f) on that drive(s).
Also run a drive checking utility from the drive manufacturer, as those sometimes catch errors missed by chkdsk.

Mon, 07/22/2013 - 20:32
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Many thanks for your advice. I will have a read up on this and give it a go :)

I've been using clone for a few years now and have not had a problem up to now. The advantage of cloning for me was being able to quickly swap drives whenever there was a problem (e.g. malware attack, boot failure, disk failure, windows corruption) and it would only take a few minutes for me to be back up and running again.

Mon, 07/22/2013 - 21:22
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

As I now have a new 500GB disk I decided to try that out first. I booted with the TrueImage 11 (2007) CD and Disk Clone Wizard successfully cloned the O/S disk to the new disk with no errors. :)

So I have a theory that TrueImage 2013 originally failed to estimate the required space for the target disk, and attempted to clone to it resulting in the error. It did this for both disks: first copying 266GB used to a 279GB formatted disk and then to a 298GB formatted disk). In theory it should have been able to clone (unless the clone process requires even more disk space?). The two target disks are now corrupt and no longer displayed by Windows explorer, so I guess I will have to format those somehow to use them for .tib Backups instead?

When I switched back to TrueImage 11 (2007) it reported problems with the corruption and target disk size and aborted the clone process before it started. Perhaps TrueImage 11 (2007) is better than TrueImage 2013 for cloning? It certainly has better error handling from what I've seen.

I can't run chkdsk /r (scheduled to run at boot up) on the O/S disk as it still reports "Autochk cannot run due to an error caused by a recently installed software package". I've paused Kaspersky and retried chkdsk but it still refuses to run. I guess I will have to contact Microsoft and Kaspersky to sort this out.

Thanks for help.

Tue, 07/23/2013 - 17:18