HDD clone issue
Hi, I hope this is the correct place for this query..
I'm assisting a friend to clone his existing 160gb HDD to new 1tb HDD(s) (x 2), so advised him to setup online backup using your system, which he's done.
We are now trying to clone his original HDD to his 2 new drives, one for use and the other for backup in the future. Your online backup service having been used as an additional safety measure.
The problem is that cloning to the first of the 2 new drives went like clockwork, but not the second. repeated attempts and even a full reformat of the 2nd new drive results in the same problem, after requested reboot the first 2 checks go fine, but the 3rd step produces "33% check error: index corrupted.
We originally believed we could alternatively use your online backup system to recover the drive if cloning failed, we now realise we can only recover the data not the dirve in it's entirety!
So, the question is, what does the error mean? We've seen the forum suggestion from Oleg Lee to "chkdsk Disk:/r" (where "r" is the drive letter..but the new drive does not yet have a drive letter!
Any other suggestions would be nice, as would a clue as to which drive is responsible for the index error?
Thank You
Samuel
My suggestion would be to check the source (in use) disk for errors. Any errors on the host disk will be transferred to the new larger disk via the clone procedure.
CHKDSK C: /R
Inside my signature below is a comment about cloning which you may find helpful.
An alternate to cloning would be to do a full disk backup to include all partitions and then restore the backup to one of the new disks.
It also might be in order to run a memcheck on the memory sticks. This test for memory errors should run overnight or at least for several hours.
http://www.memtest.org/
Version 10 is quite old and 1 Terrabyte drive were not around when that software was released. I don't know whether this could be an issue but it it something to be aware of.
When you run the clone again, before doing so, boot from the Rescue CD and use the Acronis Add disk option to delete the existing partitions on the new disk so the next tries are to unallocated space.
Hi and thanks for those pointers, unfortunately I've replaced the new HDD in case it was faulty, as the original 160gb HDD was and still is OK and does not have this problem, however the new replacement HDD came up exactly the same after cloning, though as stated the error does not occur on the original HDD, so not a transferred problem.
It seems fairly pointless having a software package to clone disks which (rather than just gliching occasionally) has a repeatable issue with at least some disks, but if this is so knowing why would be nice!
I've also replaced the RAM, no change, I've also replaced the Graphics card, no change.
I didn't think V10 was that old, and 1tb have been around a while I also thought, but will consider that and research same. However as it's not circa 1990, I would expect it to do what it says on the tin and successfully clone a provably working HDD?
Thanks again
Samuel & Harry
Hmm, whilst I appreciate your attempts to help GroverH, I think there may be some confusion here..I said version 10, when I should have said 2010, assuming there is a difference in capability, as version 10 was released I think in 2006, and 2010 in 2009.
1tb HD's have been arround since Hitachi launched the first in quarter 1 2007, whereas ATI Home 2010 was launched quarter 3 2009. I suspect this means ATI 2010 should indeed be able to deal with a 1tb HD, and it was 2010 we used, not 10 or some other similarly named product.
Despite the poor level of support from Acronis, I've resolved the initial issue ("33% check error: index corrupted) with the help of an Acronis competitor, shameful but true.
However we now have the second problem..whilst the cloning went ok to two new drives, which boot and run fine, the system hangs BSOD with hardware failure and memory parity error warnings, can only shut down by holding in the power button, no such problem with original HD.
THIS IS NOT A TRANSFERRED ERROR AS ORIGINAL DISC STILL OPERATES FINE.
It's not a problem with the new HD, as a second has also been tried with same result. RAM all changed, HD changed, Graphic card changed, same problem. Replace original drive in system, no problem, fit and test original drive in second system, no problem, either of the 2 new cloned drives exhibits the same problem in both systems.
This has to be an Acronis problem with the version used, but from the lack of responses obtained so far I do not anticipate resolving it.
Accordingly I have obtained a copy of EASEUS and completed the task without problems on one drive, will keep the other in it's current erroneous state in case Acronis ultimately find the time to respond with a fix, I can then test it and report back for the benefit of others.
By way of product comparison, I had an error on the first cloning attempt with EASEUS, after completion it infinitely looped on the XP startup screen. One post on the EASEUS forum and a response from EAEUS received within a couple of hours fixed the problem in 2 minutes.
Guess who's software we'll be using for cloning and backup going forward?
Samuel & Harry
Harold,
Another possibility would be to boot from the TI Rescue CD and perform a new clone but use the Manual cloning option and choose the "move" method to be the "as is" option.
This will cause all the new larger space to be unallocated at the end but that can be easily handled if the clone procedures produces a successful booting disk without errors.
Other procedures are possible but this might be the easiest solution.
Grover
Hello Harold and Grover,
Thank you for posting and your assistance Grover.
Harold, this issue needs to be investigated. I would appreciate if you could contact our Support team directly with this report so that we can properly troubleshoot and resolve this issue.
I apologize for any inconvenience and if you have additional questions please let me know.
Thank you.
Thanks but no thanks, I simply want a fix for the problem, I have no desire to spend yet another week accomodating the inadequacies of Acronis software. The procedure completed successfully, so obviously there's an error within the new file structure which is caused by Acronis, as all other factors were and have been accommodated:
The original drive to be cloned ran for 3 years without incident.
It runs perfect on two systems, however the two new cloned drives exhibit the same fault on shutdown, on two systems.
To be sure we changed everything other than the motherboards on the systems, but two motherboards on two systems exhibited the same error, so as good as changing the motherboard to all intents and purposes.
The original drive was cloned using the reccommended procedure to 2 NEW HD's, both of the same make and model, both had the same problem after completion, they functioned but exhibit the same BSOD lock up error on shutdown.
An alternative program from another company does not have the same problem, when using the same original HD and cloning to one of the same two new drives it operates perfectly, albeit there was a different issue, which as per previous post was dealt with in short shrift and resolved the issue to perfection in a couple of minutes, unlike the scenario with Acronis to date. So to summarise, after re-cloning one of the two new drives with alternative software from another company, the error on shutdown dissapears, and that's cloning straight on top of the errored Acronis cloning!
If the software cannot cope with what is surely an ideal scenario for the task to hand, and alternative software in a degraded situation (on top of the Acronis cloned drive as opposed to a new, clean drive) then it's unfit for purpose.
I could have lived with this had I received the same level of knowledgeable response from Acronis that I did from EASEUS. I haven't and it looks like I won't be, so the package will be returned for a full refund from the supplier, who will receive a full copy of this conversation and a detailed rundown of the operation to date.
Finally, in addition to being unfit for purpose in the operational stakes, the software is non compliant with international standards. It has proved to be almost impossible to uninstall from the systems, either via the standard XP interface procedure or via Revo uninstaller. It either crashes and states it encountered an error, or leaves hundreds of files on the system which continue to cause consequential errors ongoing.
This happens on both systems, we have now manually removed all leftover files from the registry and the windows system etc on one machinme, but will preserve the other for reference.
It's obvious from the level of problems and complaints that this software is no longer compiled or maintained by competant staff who fully understand the internal workings of same. During the last week we have found 4 FREE programs which do a far superior job and without the same hassles or pathetic support.
It's the latter which really seals the fate of the software IMHO, knowledgeable support is the essence of any business, without which it's downhill all the way. As the incident with the looping in XP startup after cloning with a competing product shows, the support should be able to nail any of the many issues raised on this forum in minutes, EASEUS did, they immediately specified a file to remove from the Windows system folder, did so, problem gone away, that's how it should be done to ensure success.
In summation, a totally useless product unfit for purpose, based on both our own experiences and supported by the ludicrous number of unresolved, perpetual issues found here and elewhere.
We will retain one of the two HD's with the error on our secondary system for posterity and reference. We certainly will not be using the software in the future, even were it free, there are far easier and less stressful ways to do the same tasks, including free software which is far more efficient. Acronis would have to work incredibly hard to have any affect on our thinking on this one, and at this juncture I doubt they have either the will or the capability, the evidence on this forum alone indicates they are out of their depth and flunking it.
May you reap what you sow
Aitch