Skip to main content

Clone Failed NVME to NVME HPEnvy

Thread solved

I just upgraded (clean install, removed TI 2012) to True Image 2020 to clone Samsung an internal 512 NVMe to a Samsung 1TB 970 Evo Plus NVMe using a USB 3.1 NVMe SSD enclosure.  When I try to clone, it skips right to Step 3 of 3 and starts executing step 4 of 7 (Copying and merging partitions).  It eventually comes up with "disk cloning failed see log for details."  The log shows the following below.

I've been using True Image for a long time (since 2011) and this is the first time I've ever had an issue.  Any help would be appreciated!

Thanks,

 

2020-03-24T21:10:09:210-05:00 12844 I00000000: -----
2020-03-24T21:10:09:210-05:00 12844 I00000000: Monitor started. Version: 24.5.1.22510.
2020-03-24T21:10:09:257-05:00 12844 I00000000: Load qt resources
2020-03-24T21:10:09:288-05:00 12844 I00000000: GetDisplayInfo succeeded: DPI: 240, scaling: 250%. Monitors: Resolution: 3840x2160, work area: 3840x2060, physical DPI: 279. 
2020-03-24T21:10:09:288-05:00 12844 I00000000: EnableHiDpiScaling - use system scaling.
2020-03-24T21:10:09:304-05:00 12844 I00000000: Init GA events
2020-03-24T21:10:09:304-05:00 12844 I00000000: Stored GA client (application: ATI2020 module: monitor session: C464EB85-6713-412B-8F68-F82C540EE425
2020-03-24T21:10:09:304-05:00 12844 I00000000: Start GA requested but service is disabled
2020-03-24T21:10:09:398-05:00 7916 I00000000: ConnectSchedulerManagerOperation: Scheduler is connected - operation finished
2020-03-24T21:10:09:882-05:00 12844 I00000000: DeviceAttachChecker was created
2020-03-24T21:10:09:882-05:00 7152 I00000000: DeviceAttachChecker. Operation started
2020-03-24T21:10:09:882-05:00 12844 I00000000: Creating ransomware check operation
2020-03-24T21:10:09:882-05:00 7152 I00000000: DeviceAttachChecker. Connection to scheduler succeeded
2020-03-24T21:10:11:109-05:00 12964 E00000000: Unable to fetch activities from the Active Protection service: Error 0x2a6001c: Failed to connect to localhost port 6109: Connection refused
| line: 0x293f8225317bd407
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:307
| function: TrueImage::Managers::RansomwareManagerImpl::GetActivityPage
| line: 0x293f8225317bd407, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:307, TrueImage::Managers::RansomwareManagerImpl::GetActivityPage
| $module: ti_managers_vs_22510
|
| error 0x2a70002: Failed to connect to localhost port 6109: Connection refused
| line: 0xea0216fb17d38026
| file: c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284
| function: `anonymous-namespace'::RestClientImpl::PerformRequest
| line: 0xea0216fb17d38026, c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284, `anonymous-namespace'::RestClientImpl::PerformRequest
| $module: ti_managers_vs_22510
2020-03-24T21:10:12:325-05:00 5136 E00000000: Active protection. PollSettingsOperation. Getting Settings. Error 0x2a6000b: Failed to connect to localhost port 6109: Connection refused
| line: 0x293f8225317bd36b
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:151
| function: TrueImage::Managers::RansomwareManagerImpl::GetSettings
| line: 0x293f8225317bd36b, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:151, TrueImage::Managers::RansomwareManagerImpl::GetSettings
| $module: ti_managers_vs_22510
|
| error 0x2a70002: Failed to connect to localhost port 6109: Connection refused
| line: 0xea0216fb17d38026
| file: c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284
| function: `anonymous-namespace'::RestClientImpl::PerformRequest
| line: 0xea0216fb17d38026, c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284, `anonymous-namespace'::RestClientImpl::PerformRequest
| $module: ti_managers_vs_22510
2020-03-24T21:10:20:807-05:00 12844 I00000000: Active protection. Service connected
2020-03-24T21:10:20:807-05:00 12844 I00000000: Active protection: Start polling. PollType - 1
2020-03-24T21:10:26:832-05:00 12844 I00000000: Active protection: Start polling. PollType - 1
2020-03-24T21:10:41:027-05:00 13568 I00000000: Account info was updated. Executing checkers.
2020-03-24T21:10:41:027-05:00 13568 E00000000: No need to update Active Protection activities on account info updated 
2020-03-24T21:10:41:543-05:00 12964 E00000000: AccountInfoProvider. Unable to get used cloud size: Error 0x1900002: No Internet connection.
| line: 0x54350d6c76523663
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ob_manager\ob_manager_impl.cpp:530
| function: TrueImage::Managers::ObManagerImpl::GetTraveller
| line: 0x54350d6c76523663, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ob_manager\ob_manager_impl.cpp:530, TrueImage::Managers::ObManagerImpl::GetTraveller
| $module: ti_managers_vs_22510
2020-03-24T21:10:41:574-05:00 13568 I00000000: Account info was updated. Executing checkers.
2020-03-24T21:10:41:574-05:00 13568 E00000000: No need to update Active Protection activities on account info updated 
2020-03-24T21:10:41:722-05:00 12964 E00000000: cloud_usage_checker. Failed to execute: Used space in MonitorAccountInfo is not valid.
2020-03-24T21:10:42:042-05:00 12964 I00000000: LiveUpdateChecker. Update request is sent. Recheck in 10000
2020-03-24T21:10:42:368-05:00 12964 E00000000: cloud_usage_checker. Failed to execute: Used space in MonitorAccountInfo is not valid.
2020-03-24T21:12:01:361-05:00 12964 I00000000: Tray center: Failed to find history notification <active_protection_checker:state (48419892-759E-4F25-A5EE-A3EC47DBA6C8 @ 3/24/2020)> in list: notification was not found in list
2020-03-24T21:12:01:361-05:00 12964 E00000000: Unable to fetch activities from the Active Protection service: Error 0x2a6001c: Operation timed out after 10015 milliseconds with 0 bytes received
| line: 0x293f8225317bd407
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:307
| function: TrueImage::Managers::RansomwareManagerImpl::GetActivityPage
| line: 0x293f8225317bd407, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\ransomware_manager\ransomware_manager_impl.cpp:307, TrueImage::Managers::RansomwareManagerImpl::GetActivityPage
| $module: ti_managers_vs_22510
|
| error 0x2a70002: Operation timed out after 10015 milliseconds with 0 bytes received
| line: 0xea0216fb17d38026
| file: c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284
| function: `anonymous-namespace'::RestClientImpl::PerformRequest
| line: 0xea0216fb17d38026, c:\bs_hudson\workspace\23\home\http\client\impl\http_client.cpp:284, `anonymous-namespace'::RestClientImpl::PerformRequest
| $module: ti_managers_vs_22510
2020-03-24T21:15:01:754-05:00 12964 E00000000: Cannot get info on task A78FE22E-957D-493B-8A22-70C1C2D0C59D: Error 0x900010: Error while opening script file.
| line: 0x96edab22042dcec6
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1071
| function: TrueImage::Managers::TaskManagerImpl::Get
| line: 0x96edab22042dcec6, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1071, TrueImage::Managers::TaskManagerImpl::Get
| $module: ti_managers_vs_22510
|
| error 0x900004: Error while opening script file.
| line: 0x96edab22042dcf7e
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1255
| function: TrueImage::Managers::TaskManagerImpl::ParseScript
| line: 0x96edab22042dcf7e, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1255, TrueImage::Managers::TaskManagerImpl::ParseScript
| $module: ti_managers_vs_22510
|
| error 0x900005: Error while opening script file.
| line: 0x96edab22042dd0f8
| file: c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1633
| function: TrueImage::Managers::TaskManagerImpl::GetScriptFileName
| line: 0x96edab22042dd0f8, c:\bs_hudson\workspace\23\products\imager\home\managers\impl\task_manager\task_manager_impl.cpp:1633, TrueImage::Managers::TaskManagerImpl::GetScriptFileName
| $module: ti_managers_vs_22510
2020-03-24T21:20:10:466-05:00 12964 E00000000: cloud_usage_checker. Failed to execute: Used space in MonitorAccountInfo is not valid.
2020-03-24T21:20:10:607-05:00 12964 I00000000: LiveUpdateChecker. Update request is sent. Recheck in 10000
 

 

 

0 Users found this helpful

John, welcome to these public User Forums.

Please see KB 56634: Acronis True Image: how to clone a disk - and review the step by step guide given there.

Note: the first section of the above KB document directs laptop users to KB 2931: How to clone a laptop hard drive - and has the following paragraph:

It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

See also KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media 

If your working drive uses GPT then it must boot using UEFI mode and have the 'Windows Boot Manager' as the boot priority device.

The key to success here is to boot from the Acronis Rescue Media in UEFI mode with the new SSD installed inside the laptop and the original SSD connected externally.

Personally, having recently upgraded my own HP Omen laptop from a 128GB NVMe M.2 SSD to a 500GB Samsung 970 Evo Plus NVMe M.2 SSD, I would recommend making a full backup of the source SSD then swapping it out for the new EVO SSD and booting from the Acronis Rescue Media then recovering the backup to the new SSD without the need to use any external NVMe adapter etc.

Note: the log provided is not relevant for this issue and would suggest you are attempting this clone from within Windows too.  The relevant logs are either the ti_demon or backup_worker logs but again I would recommend not doing this type of migration from within Windows.

Steve, 

 

Thanks...I've read through everything.  I tried the NVMe to NVMe (source in USB holder and target in pci slot) and got Failed to Read data form disk errors (failed to read from sector xxxx....check using Check Disk).  Did Check Disk and still have errors.

 

Tried backup method you said, but couldn't figure out how to change partition size for target disk. The notes say to "change the settings as required before clicking next.   Changing the settings will be needed when recovering to the new hard disk of different capacity"   There was no ability to change settings.

 

https://www.acronis.com/en-us/support/documentation/ATI2020/index.html#13903.html

 

I was able to clone the 512 NVMe to 1TB NVMe, but the partitions were the same which defeats the purpose.

 

I'm really close.  Any ideas on how I can change sizes for target.

Thanks,

 

John

John, download a copy of the free MiniTool Partition Wizard software and use this to resize and/or move your partitions on the larger drive to achieve the best use of the space available.

ATI should try to do this automatically but often fails to do so for various reasons that are not obvious!

John,

In your linked user guide, have a look at item number 7.  In the screen image you will see in the work area at top left a check box next to Disk 1.  In the example shown that check box is empty. If you tick the check box then manual sizing of partitions is not required and the restore should proportionately fill all available disk space.

 

Steve and Enchantech,

THANKS.  I figured it out.  It's a really quirky interface.  If you click "select all" items, the "setting in partition" sub menu doesn't come up.  I finally just had to click on each partition and manually calculate how big C would be after all other partitions stayed the same.   Enchantech...it would have been easier if I did it your way.

Once again thanks for all the help I would have never got this far without you.

As a commentary, I've been cloning drives for years and have never had problems.  This was my first NVMe clone and it was a real pain.  True Image used to be so easy to use...click click click, TI reboots into standalone mode, does clone, swap drive and done.  I don't know why this is now so difficult.  I feel like I went 25 years back when you had to do everything manually.  Oh well.  I'm now up and running and learned a lot.

 

Thanks,

 

John
 

John,

With new advancements in bios implementations and hardware such as NVMe come growing pains.  It's just a consequence of the time we are in.  The future will bring easy of use again and then there will be another round on innovation to repeat the cycle.  Technology, gotta love it!

Glad to hear you got things squared away.