True Image 2013 is not clonning/recovering/backingup correctly.
Hi folks!
I´m trying to clone my system HDD, and TI2013 (Bootable media and from Windows) isn´t getting to clone it. It pass for the whole process, but after plugging the clonned HD, it remains as the old status from the destination. So it seems that instead of reading the source TI2013 is reading the destination and cloning to destination. I have tried directly from the Windows, and also created a bootable media. From both ways it didn´t work and kept the same issue. Tried also to change the SATA and the issue remains. Even removing partitions from the destination from Bootable CD TI2013 didn´t solve. The destination continues in the old status after cloning.
By attempting the clone from Windows, after restarting and after starting Acronis loader... I get the pop-up warning:
Acronis Bootable Agent is waiting for removable devices:
One or more of you removable disks may not have started at the moment. Click 'YES' to wait for full startup of the devices (recommended). Click 'NO' to ignore uninitialized devices and continue. Click 'CANCEL' to stop the current operation. Do you want to wait for the devices startup?
By clicking YES, keeps trying but goes back to this message
By clicking NO or CANCEL, goes back to Windows and nothing happens.
So, none of the options starts the clone process.
It seems that TI2013, doesn´t recognize the same brand/model HDD or other issue.
It seems that TI2013, doesn´t recognize the same brand/model HDD or other issue.
My disk 1: Samsung ST500DM002 (Source)
My disk 2: Samsung ST500DM002 (Destination)
Any idea what is wrong withTI2013 on w764b for clonning?
Is anybody else facing the same issue?
Is there some way that Acronis can provide me a downgrade of 2012 and/or 2010 to test if the same is happening in old versions?
Thanks
Clone is riskier than Backup and Restore. Truly, almost no one should use Clone. While Clone saves a step and saves a bit of time compared to Backup and Restore, it comes with risks as if you don't do it correctly you can end up with a non-booting system.
- It isn´t only a step and time saves, it is a different work-flow for different users. By having a clone, you just unplug and plug the other and keep working. While the backup is a larger process. Well, each one has it owns work-flow that fits best for your needs. ;0)
Regarding noon-booting system happens because for some reason the TI2013 changes the active partition and/or BIOS boot order after shutdown/rebooting. So, by checking booth and activating the correct partition, you have it back. It is something that Acronis shall review and fix!
Clone should be used only by advanced users who know what they are doing. It is riskier and can result in a loss of data and a failed system. Use a full disk backup and restore, as it's far safer.
- The full disk backup and restore is having the same issue as mentioned above. So, it isn´t a solution in this case. Anyway, thanks for your input.
Updating the case...
Tries that DIDN´T WORK and the issue remains:
a) Wipping partition from TI2013 bootable CD to see if destination would erase and stop copying/cloning destination from destination;
b) Unplugg the 3rd HDD (Sata External);
c) Unplugged all USB (USB card reader internal/external, printer, anything that has card slots etc);
d) Removed the destination HDD from the Rack Mount Drawer (hot-swap/hot-plug) and plugged directly from SATA cable and energy cable;
e) Changed from SATA 6G/s to 3G/s and also tried different SATA ports.
So, all above didn´t work.
In sum, what I think it is really an issue with TI2013 which in the FINISH step on the CLONE option, isn't reading the source to destination and is showing before/after from destination to destination content instead. The source content just show right on the previous steps.
New tries of the day that didn´t work:
>>> Clone Disk from TI2013 bootable media CD or from Windows (Source on C: and Destination on rack):
- Clone mode: Manual
- Source Disk: Disk 1 (Samsung ST500DM002)
- Destination Disk 8 (Samsung ST500DM002)
- Move method: Manual
- Change disk layout: Shows the source disk 1 as I want to be the destination.
From Bootable CD results: Clone disk operation failed! (No more info)
From Windos results: Clone disk operation failed! (No more info)
>>> Try RECOVER from TI2013 bootable media CD or from Windows (Source on C: and Destination on rack):
If I check sector by sector, the destination HD is grayed out, so don´t get to select.
If not checked I get to recover, but it doesn't recover as Source status as should, and recover the destination status! Prety weird.
Btw,
Another weird thing is that The FINISH source/destination shows weird too when cloning or recovering.
Source (partitions): [95MB NTFS SYSTEM RESERVED] [C:\ 496GB Windows, etc]
Destination : [100MB FAT32] [C:\ 496GB Windows, etc]
So, the destination should show exactly as source. I mean, the 100mb fat32 should be [95MB NTFS SYSTEM RESERVED] and it isn't happening.
I´ll try to upload some screenshots here.
Ok here goes some screenshot to show the issue on RECOVER:
On attachment 1 you can see that on the RECOVER 3rd step I want to recover the whole DISK 1 (MBR track + 95MB NTFS System reserved + 465.7 GB NTFS Windows 764b), until here it is ok, now on attachment 2, it is the destination disk I want to recover the whole DISK 1 (MBR track + 95MB NTFS System reserved + 465.7 GB NTFS Windows 764b). The destination disk was DISK 2 (100MB FAT32 + 465.7 GB NTFS Windows 764b). Now on the FINISH step on attachment 3, you see in the summary that item 1 is deleting 100MB fat 32, and item 3 is creating AGAIN a partition FAT32 100MB, instead of creating the 95MB NTFS System reserved from the source!
With that, it results in a wrong recover. I keep with the same old data from my HD. Prety weird!
Ok here goes some screenshot to show the same issue on CLONE option:
On attachment 1 you can see that on the CLONE 2nd step I want to clone the source DISK 1 (95MB NTFS System reserved + 465.7 GB NTFS Windows 764b), until here it is ok, now on attachment 2, it is the destination disk I want to recover the whole DISK 1 (95MB NTFS System reserved + 465.7 GB NTFS Windows 764b). The destination disk was DISK 2 (100MB FAT32 + 465.7 GB NTFS Windows 764b). Now on the FINISH step on attachment 3, you see in the summary that item "After:" is keeping/creating AGAIN a partition FAT32 100MB, instead of creating the 95MB NTFS System reserved from the source as shown on attachment 1!
With that, it results in a wrong recover. I keep with the same old data from my HD. Prety weird!
IMPORTANT:
What I noticed also is that to keep the latest way is my source/clone I need to FLAT my Rollback (create a baseline). But, TI2013, doesn't keep my ROLLBACK history (snapshots) or even keep Rollback working after windows restart. Even using the settings in TI2013 such as backup sector-by-sector, recover MBR or other option.
IMHO if I bought a product TrueImage 2013 that says CLONE AS IS, it should do it without needing extra magicians! OR even FULL BACKUP where I select the whole disk 1 (MBR + 95MB NTFS System reserved + 465.7 GB NTFS Windows 764b), it should RESTORE what I have backed up!
So, how to really CLONE / Duplicate my HD and keep my Rollback snapshots and everything intact as it should be? I just bought TI2013 for it and want to have it working as supposed to do. I have already spent too much time on it!
I would suggest that you take an extra step and use the tool "add a new disk" from the Rescue Media to create a (blank) target drive with the same partitioning scheme. (You would specify MBR, but you do not need to create any partitions, just initialize the disk as MBR)
It appears in your screen captures that the source disk is MBR, and the target disk is GPT. This could really be an issue since the product is wiping the partitions, but not converting the disk.
You can also use DISKPART in Windows to do the conversion to MBR on the destination disk before the clone.
I would suggest that you take an extra step and use the tool "add a new disk" from the Rescue Media to create a (blank) target drive with the same partitioning scheme. (You would specify MBR, but you do not need to create any partitions, just initialize the disk as MBR)
It appears in your screen captures that the source disk is MBR, and the target disk is GPT. This could really be an issue since the product is wiping the partitions, but not converting the disk.
You can also use DISKPART in Windows to do the conversion to MBR on the destination disk before the clone.
Hi James F, It is TrueImage that is converting to GPT. Anyway, I did your suggestions. Here is the report:
Considering DISK1 as source and DISK3 as destination:
1. By adding a new disk from Rescue Media as MBR with not creating any partitions, in the finish step the summary shows exactly how it should be:
Source Disk1 - Destination: Disk 3
Before: [Unallocated 465.8GB]
After: [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc]
So, really the clone. But when processing, it results in error pop-up "Clone disk operation failed:", with no more info.
Another try adding new disk with partitions...
2. By adding a new disk from Rescue Media as MBR and creating partitions on disk 3 as [H: 95MB NTFS Pri, Ac] [J:\ 465.7 GB log], in the finish step the summary shows exactly how it should be:
Source Disk1, Dest.: Disk 3
Before: [H: 95MB NTFS] [J:\ 465.7 GB]
After: [100MB FAT32] [C:\ 465.7 (Basic GPT)]
So, NOT really the clone from Disk1 what should be [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB NTFS Windows, etc] instead of [100MB FAT32] [C:\ 465.7 (Basic GPT)] as it is showing on after.
In try number one above, did you review the log file after receiving the error to determine why the failure occurred?
Can you open Windows Disk Management and capture the screen(s) and post here?
Capture the screen when it opens, and then select View/Top/Disk list and capture that one as well.
These two screens may help with determining what is happening here.
Hi James, I have already changed the status of the HDD after that, actually if not wrong I just formated it, so the screenshot won't help you I think. Anyway, I'll try later, because right now I can't use the computer because it is performing CHKDSK on DISK1, because I tried the try #1 from Windows instead of Bootable CD, and from Windows the log has more info and in sum it told me that the cloning fails was “Error code: 10 'File system error is found' with extended code: 458,776 'MFT bitmap corrupted”, and the link is that: http://kb.acronis.com/content/40642
So, after finishing the CHKDSK, I'll take the screenshot you requested and try again #1 and post the results here.
If H: and J: are both on your "Disk 1", be sure you run chkdsk /r on each drive letter.
Hi James, thanks for your feedback.
Well, H: and J: are on DISK3 destination, not on 1 which is the source. After the chkdsk on Disk1, the issue remains. Regarding CheckDisk, I guess it was done in the whole DISK1 once it was schedule by windows to do after the reboot because the DISK1 was the system HD with the 95MB reserved by the system but with no driver letter.
I tried to add new disk/clone again from Bootable media and from Windows (Build 6514) and the same error occurred as before. Error 10 as posted above. Attached is the screenshot requested. Pay attention, the DISK1 mentioned here is "Disco 0" in this screenshoot/Windows, and DISK 3 is "Disco 2".
Using Windows Disk Management, right click on the 95MB NTFS partition on your disk , and temporarily assign a drive letter to the System Reserved partition. You then will be able to run chkdsk on that drive letter. (A reboot will have to be performed to do so - you will be prompted to schedule it at boot time.)
Be sure to use the chkdsk /R option to scan (and fix) the entire file system in that partition. If you didn't use the /R parameter on the OS partition, do that as well.
If errors are found and corrected, using Windows Disk Management, remove the temporarily assigned drive letter and try the clone again from the Rescue Media.
Good morning James. Thanks for the tip, I appreciated that.
Ok, done chkdisk /r on both partitions (Disk1 - Source), after that started the steps... Add new disk (MBR w/ no partitions) on disk3 as you requested + clone disk (disk1 to disk3) and the results after finishing the cloning process from:
Windows: MBR Error 1
After getting such error, I went to Windows Disk Management to see what was the Disk3 status (destination HDD) and found out that it seems that nothing was done by TrueImage because the HD is still as Unallocated 465.76 GB! No both partitions created, no data cloned, no nothing!
Maybe after adding new disk it must be formatted. Not sure. If it is the case, programmers should add a warning that the HD isn't formatted and TI should stop the process. Well, now I'm going to try the same without formatting from Bootable CD and I'll post the results soon.
Ok, now the results from Bootable CD after that started the steps... Add new disk (MBR w/ no partitions) on disk3 as you requested + clone disk (disk1 to disk3).
Here, it was different the layout than mentioned before (1), now the summary is:
Before: [Unallocated 465.8GB]
After: [100MB EFI] [C:\ 465.54 (Basic GPT)]
And FOR ME it should be as a clone:
Before: [Unallocated 465.8GB]
After: [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc]
and the results after finishing the cloning process from Bootable CD was:
No error, but the HD wasn't really cloned from DISK1 to DISK3. I mean, what I got was:
DISK1 (Source): [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc]
DISK3 (Destin.): [100MB EFI] [C:\ 465.54 (Basic GPT)]
So, no CLONE at all! The Bios I got DISK3 [Windows Boot Manager], if I select in the bios just DISK3 it doesn't start as the SOURCE does! Besides that ALL my ROLLBACK info is lost and ROLLBACK doesn't work. It just clone Windows and not the whole HD as it should be!
Lucato,
It seems Acronis is trying to force an EFI partition on the disk as well as make it GPT partitioned.
In your computer firmware setup (BIOS or UEFI settings), check to see if there is an option to switch the firmware mode to Legacy BIOS instead of UEFI. If so try changing the firmware mode to Legacy, and then boot to the Rescue Media and try the clone again (be sure to "add a new disk" as MBR on the target again).
You may also have the ability to boot in Legacy Mode or UEFI mode from your boot options menu (also in the firmware). Some systems will allow you to select the boot device by pressing a key (usually an "F" key, i.e. F10) on the keyboard during system power on self test (POST).
What brand of computer/motherboard do you have?
Hi James, good morning.
The mother board is an Asus P8P67 B3 rev 3.0 with the latest BIOS updated 3602. More info:
http://www.asus.com/Motherboards/P8P67/
James, it seems that you are completely right. I mean, on my BIOS on the boot order, there are two ways to chose to boot the CD driver:
1. [UEFI] P4: "Bootable Media"
2. P4: "Bootable Media"
I think the option 2 is the normal "Legacy" you mentioned.
So, By choosing option 1 [UEFI] it starts the CD with "Starting Acronis UEFI Loader..." and results partitions as EFI or FAT32 instead of the NTFS as in the source.
Now, by booting without UEFI (option .2), starts the CD with "Starting Acronis Loader..." and results partitions NTFS as in the source so the summary is:
Before: [Unallocated 465.8GB]
After: [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc]
The program should recognize it and never allow to format different if not requested!
Well, the results after cloning as it should be:
First attempt again MFT bitmap corrupted. Tried the chkdsk in both [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc] and again MFT bitmap corrupted. Tried to use TestDisk instead of Chkdks to fix MFT and didn't work. The MFT error remains as: "C:\" MTF 0x70018 tag=0X89D94B01B483DCA9.
So, one part of the issue one clone was found out, the UEFI start/boot or not. IMHO something that must be revised by programmers.
Now I'm going to try to fix the MFT in some way. If you have some suggestion, they're welcome.
P.S.: Btw, instead of trying CLONE way and trying the Back-up/Recovery method... Add new disk + recover bkp of DISK1 ( MBR + [95MB NTFS SYSTEM RESERVED] [C:\ 465.7 GB Windows, etc] ) + checked to recover signature or not, after rebooting I get the Windows error 0xc000000e, but this one I'll create a new topic to don't mess with the CLONE issue here.
Well just updating this topic, I have downloaded and installed the SnapAPI 1088 driver, reboot the machine and after restarted the computer I've created the new bootable media.
I'm still getting the annoying MFT bitmap error message 0x70018 tag=0X89D94B01B483DCA9 while performing cloning. I'd like to know, what is exactly such error code and why I am getting it even updating the SnapAPI driver (1088).
Have a nice week.
Acronis recommend using SNAPAPI build 2140 for this problem with TI 2013.
Hi Colin B, thanks for your reply. I appreciated that.
Just one question. Should I go to Windows uninstall programs and uninstall the previous SnapAPI before installing this 2140 or should I install overwritting/updating?
Thanks in advance.
Lucato,
Just run the downloaded setup file, it will overwrite the old settings.
If for some reason both versions appear in Add/Remove programs, remove the old one from the list.
Check this before rebooting.
Hi Colin, good morning and thanks.
Well just updating this topic, I have downloaded and installed the "latest" SnapAPI 2140 driver as you suggested, reboot the machine and after restarted the computer I've created the new bootable media.
I'm still getting the annoying MFT bitmap error message 0x70018 tag=0X89D94B01B483DCA9 while performing cloning or backup from windows or bootable media.
I'd like to know, what is exactly such error code and why I am getting it even updating the SnapAPI driver (2140). The only think I can imagine is due RollBack installed because I have read that you need to uninstall it before cloning. But it is ridiculous I have to uninstall a software to make TrueImage works. I'll try that later and check if the problem is it. Not sure if MFT is related to Rollback.
Have a nice day.
Clone is riskier than Backup and Restore. Truly, almost no one should use Clone. While Clone saves a step and saves a bit of time compared to Backup and Restore, it comes with risks as if you don't do it correctly you can end up with a non-booting system.
Clone should be used only by advanced users who know what they are doing. It is riskier and can result in a loss of data and a failed system. Use a full disk backup and restore, as it's far safer.
tuttle, given that Acronis recommend ALWAYS creating a backup to an external HDD before attempting to clone to a second internal drive, isn't it true that backing up to an external HDD and then restoring to the second internal drive takes no longer and is safer in that one now has both a backup and a clone of one's source drive?
There's rarely a need to clone, since backup and restore accomplish the same goal. As clone entails the risk of wiping out the system drive, I think only advanced users should clone. Virtually everyone else should backup and restore. I'm an advanced user, yet I would still backup and restore rather than clone.
@George T
IMHO, the software wasn't developed for advanced users, it was intended to be used like easy as a single click to clone or backup. If it doesn't clone 100% doesn't call it CLONE. Can you imagine clone Dolly sheep as a half horse and half sheep and call it as a clone? ;0) As I said before, if it is true, it is ridiculous that I have to uninstall RollBack to make TrueImage works. It is likewise request to uninstall Chrome, Firefox to get to install Internet Explorer. No sense!
@Tuttle
If it worked would be wonderful, just use the Bootable media and recover the backup! But it also doesn't work as I'm going to post in a new topic soon regarding Backup issues in TI2013 w/ RollBack.
Just a quick errors list:
- MFT error even with the latest SnapAPI 2140 or 1088 when trying to clone/backup;
- After restart when restarting windoes error 0x0000000e;
- Lots of time to load/Start Windows and shows "preparing desktop..." if got to make a backup and recover;
- Blue desktop screen after restarting Windows with no bars icons and so on.
Is running chkdsk /r on both drives also reporting the same problem?
Thanks Colin! The running chkdsk /f couple times in all partitions seems to solve.
The ONLY way that clone worked on here was by:
1. uninstalling Rollback;
2. DO NOT boot CD from UEFI to avoid getting different summary from source/destination partitions;
3. Passing CHKDSK in all SOURCE partitions to avoid MTF error;
4. Cloning from bootable media and not from TI in Windows.
5. Changing bootable order in BIOS.
So, IMHO:
a) it is ridiculous I have to uninstall one software to make TI works;
b) It isn't what the software is supposed to do to any basic customer knowledge. Too hard for any low knowledge user;
c) CHKDSK should be implemented in the True Image Bootable media. It is a pain after getting the error, have to reboot, change CD, pass to all recovery windows process to get the command prompt and so
Well, just suggestions to improve it. ;0)
Thanks to all for all help here. I'll have to remind all that steps, next time I'll have to clone again!
Thanks Colin! The running chkdsk /f couple times in all partitions seems to solve.
You should run chkdsk /r, not just chkdsk /f. chkdsk /f won't check for disk errors, just file errors.
Thanks for the tip Tuttle. I´ll keep that in mind. Not sure if /f can mess Rollback RX or registration keys.
Well, just adding my previous post how I got to "clone", actually the clone results weren't great...
After cloning I went to check the cloned HD and the CLONE didn't work as expected.
By checking the others software installed a bunch of them lost the registration key and other I had to reinstall. So, there is no way to call it as a clone! TI doesn't clone at all, otherwise it should be a true image.
By using clone or back-up the same happened! The only way I got to make a "clone" doesn't lose the registration keys was by doing a BACK-UP and selecting SECTOR-BY-SECTOR and recovering also sector-by-sector, but in all cases it don't keep my ROLLBACK RX installed working and nor its snapshots. So, I had to uninstall and install over ROLLBACK RX. So, once again, there is no way to call and say the TRUE IMAGE is a "TRUE IMAGE"! TI doesn't clone or really back-up the real image or state of the HD as it should.
The company and developers must urgent fix the registration key loses and RB RX that isn't cloned as it should be.
The day I get to use TRUE IMAGE software and its clone tool and it really get to clone my HD with not losing any registrations keys or stop working some programs that I have to reisntall and keeping my ROLLBACK RX installed and with all snapshots as it, I'll really say that the program can be called TRUE IMAGE! Now a days, it isn't TRUE!
Have a nice day,
Luis
Luis,
Some software uses the disk signature and serial number as part of the activation procedure. The disk signature can be cloned as that is just an entry in Windows registry at the Windows end and an entry in the bootsector of the hard drive, but, the serial number can't be, if the serial number changes software that uses it as part of their activation procedure will need reactivating.
I haven't used Rollback RX, so I don't know if it keeps it's information in a hidden folder.
Personally where an OS drive is concerned, I much prefer to make a complete disk image and then restore that image to a new drive.