Skip to main content

TI2018 system cloning under Rescue Media

Thread needs solution

Windows 10, 64 bit, 16Gig RAM TI2018

I have two identical Samsung SSD 850 EVO's... 500GB.  One is my current system drive, and the other is an external USB clone of that same drive. Should my functioning system take a dive, I can throw in the clone and keep going.

However, since TI2018 I've hit a wall.  Under the Rescue Media Builder environment, TI2018 will not successfully clone my system drive.  I've tried multiple times, it always gets about 95-98% done, and throws an error.  (Yes, I should know what it is, but I don't right now).  One odd thing I did note is that the program indicates it is going to make the cloned disk GPT.  I didn't request that, and my live system disk is NOT GPT!

The other part that is confusing me is this... I can successfully (and much more quickly I might add) clone the drive using a TI2014 Rescue Media Build CD.  And I can clone it using EASUS.  CHKDSK shows no errors on the system drive.  Has anyone else had issues cloning a system drive under TI2018?

0 Users found this helpful

Craig, there are several different methods of cloning that can be used with ATI 2018, but if you are seeing this when using the Rescue Media it is because you are booting that media in UEFI mode which will convert the clone target drive from MBR to GPT.  If your Windows OS boots in Legacy mode (as shown by running the msinfo32 program) then the Rescue Media needs to be booted in the same way to preserve your MBR drive format.

With ATI 2018 you should be able to do a live clone using the Windows ATI GUI but when doing this, your target drive should not already have a Windows OS on it as otherwise a restart will be required to continue the clone action.

I would recommend downloading / using the MVP Log Viewer tool (available via the Community Tools) to get access to the logs involved for most ATI operations.  If you are using the Rescue Media then the Log can be saved to a drive or USB stick while you are still in the standalone environment.

In reply to by truwrikodrorow…

Wow, that explains absolutely everything except for the error. I was cloning from the Rescue Media as I thought it would be "cleaner"... no open/locked files on the system drive.  Here I was making it worse!  Who would have thought.  Is this spelled out somewhere that I should have known?  If so, I apologize for wasting everyone's time...

Odd, however, that ATI2014 and EASUS don't throw errors or force this conversion to GPT.  Me thinks things have gotten too complicated.  Either that or I need to study more...

Thanks!!

In reply to by truwrikodrorow…

I looked at the logs associated with my attempted clones.  Below is the text.  Am I supposed to be doing something in admin mode??

 

[20180407-140221-290][tnd][T] build: 2410, process: 12708, 'C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe'
[20180407-140221-290][tnd][T] 2018.04.07 14:02:21 UTC
[20180407-140221-290][tnd][T] 2018.04.07 10:02:21 LOCAL
[20180407-140221-290][tnd][T] Initialize Tnd API
[20180407-140221-290][tnd][E] Failed to open control device '\\.\Global\TndControl2410': status 2
[20180407-140221-290][tnd][E] Failed to initialize: error 0x2
[20180407-140221-290][tnd][E] SetLastError: Error 0x97003a
| line: 0x911b812852306f5e
| file: k:\2410\kernel\win\tnd\dll\api.cpp:81
| function: Kernel::Tnd::Api::CheckAdminRights
| $module: tnd_driver_api_vs_s_2410
[20180407-140221-290][tnd][E] Failed to open control device '\\.\Global\TndControl2410': status 2
[20180407-140221-290][tnd][E] Failed to initialize: error 0x2
[20180407-140221-290][tnd][T] Free buffer 07DA9D68
[20180407-140221-290][tnd][T] TndSetSessionStateChangedCallback
[20180407-140221-290][tnd][T] TndSetSessionLowFreeSpaceCallback

Craig, please see KB 60870: Acronis True Image 2018: Active Cloning which describes the new Active Cloning feature introduced with 2018.

ATI in general normally needs to be run from an Administrative level account in order to have all the correct privileges to perform the operations needed.