Clone process failing on new 120gb SSD MX 500 - Please help
Hi All,
I need help please, I am trying to run TI to clone my HHD with just 88gb on it onto my new Crucial MX500 120gb SSD drive. It failed half way through at 50% (1hr 17 mins).
At 1st when I tried to kick off the clone process it warned me i needed to clear up space, so I did that and tried again and the second time around I didnt get that error, so I thought ok great thats the space issue dealt with.
As far as I can see there are 3 partitions that need to be copied, they are
c: 88gb
h: 12gb recovery
forgot the drive letter: 160 mb
So I should have enough space on the target SSD 120gb drive.
these were the warnings I saw in the ti_console0.log:
2018-12-24T11:40:03:734+00:00 7964 E019203F3: Error 0x19203f3: Cannot determine Sync Agent service state. Restart your computer.
| trace level: error
| line: 0xcaf802b9a1d59e52
| file: k:\3301\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:690
| function: SyncAgentApi::SyncAgentApiMan::SubscribeRemote
| line: 0xcaf802b9a1d59e52, k:\3301\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:690, SyncAgentApi::SyncAgentApiMan::SubscribeRemote
| $module: sync_agent_api_vs_3301
|
| error 0x1920021: Cannot determine Sync Agent service state. Restart your computer.
| line: 0xcaf802b9a1d59d21
| file: k:\3301\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:385
| function: SyncAgentApi::SyncAgentApiMan::EnsureSyncAgentIsRunning
| line: 0xcaf802b9a1d59d21, k:\3301\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:385, SyncAgentApi::SyncAgentApiMan::EnsureSyncAgentIsRunning
| $module: sync_agent_api_vs_3301
|
| error 0x192001d: Cannot determine Sync Agent service state. Restart your computer.
| line: 0xfc280cab9aba1bd6
| file: k:\3301\products\imager\home\sync_agent\impl\api\syncagent_start_error_provider.cpp:54
| function: SyncAgentApi::SyncAgentStartErrorProvider::GetIsRunningError
| line: 0xfc280cab9aba1bd6, k:\3301\products\imager\home\sync_agent\impl\api\syncagent_start_error_provider.cpp:54, SyncAgentApi::SyncAgentStartErrorProvider::GetIsRunningError
| $module: sync_agent_api_vs_3301
|
| error 0xfff0: The specified service does not exist as an installed service
| line: 0xbd28fdbd64edb8d9
| file: k:\3301\common\error.cpp:283
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8d9, k:\3301\common\error.cpp:283, Common::Error::AddWindowsError
| code: 0x80070424
| $module: sync_agent_api_vs_3301
Please can someone help me
Thanks
Pat
ps. I have tried to attach the AcronisSystemReport.zip report but at 6mb its says its too large.
pps.. I have managed to attach the logs..

- Log in to post comments

I am trying to run TI to clone my HHD with just 88gb on it onto my new Crucial MX500 120gb SSD drive.
The log in the zip file is the only one that is helpful for this issue and this shows a format/resize error being reported during the clone operation.
It also shows that you are cloning from a very much larger HDD drive with a C: partition size of 451.2 GB to your new 120 GB SSD drive.
The log shows:
24/12/2018 11:40:59 :223 Operation Clone Disk started.
24/12/2018 11:40:59 :223 Operation description: Clone Disk 1. Clearing disk Hard disk: 3
2. Clearing disk Hard disk: 3
3. Clearing disk Hard disk: 3
4. Copying partition Hard disk: 1 -> 3 Drive letter: - File system:
NTFS Volume label: SYSTEM Size: 100 MB
5. Copying partition Hard disk: 1 -> 3 Drive letter: C: File system:
NTFS Volume label: OS Size: 451.2 GB -> 98.95 GB
6. Copying partition Hard disk: 1 -> 3 Drive letter: D: File system:
NTFS Volume label: HP_RECOVERY Size: 14.40 GB -> 12.64 GB
7. Copying partition Hard disk: 1 -> 3 Drive letter: - Type: 0x27 (Windows RE Hidden; PQ; MirOS) File system:
FAT32 Volume label: HP_TOOLS Size: 101 MB -> 106 MB
8. Copying MBR Hard disk: 1 -> 3
1 of 2 - Acronis Universal Restore Use operating system drivers : Yes .
24/12/2018 11:42:40 :374 Pending operation 52 started: 'Clearing disk'.
24/12/2018 11:42:40 :374 Pending operation 52 started: 'Clearing disk'.
24/12/2018 11:42:40 :390 Pending operation 52 started: 'Clearing disk'.
24/12/2018 11:42:40 :390 Pending operation 14 started: 'Copying partition'.
24/12/2018 11:43:22 :900 Pending operation 14 started: 'Copying partition'.
24/12/2018 12:58:03 :187 Pending operation 14 started: 'Copying partition'.
24/12/2018 12:58:03 :515 Error 0x101f6: A format/resize error.
24/12/2018 12:58:03 :515 Pending operation 14 started: 'Copying partition'.
24/12/2018 12:58:04 :186 Pending operation 61 started: 'Copying MBR'.
24/12/2018 12:59:00 :736 Error 0x13c0005: Operation has completed with errors.
The above shows that the clone operation will need to resize from an OS Size: 451.2 GB -> 98.95 GB which is 10 GB more than the 88 GB you quoted.
If you want to go ahead with this clone, then you will need to shrink the size of the Source drive data, especially as you need to leave some free space on your new 120 GB SSD drive if you want to have any benefit from making this change!
- Log in to post comments

Thank you for your prompt response Steve, I will delete approx 10gb on my old HDD and try again.
Merry Xmas! :)
Pat
- Log in to post comments

Hi Support,
I tried what you said, I got my C drive space down to 67gb (from 98gb), and my recovery partition is only 14gb, so this should fit fine onto my 120gb MX500 drive
But it has failed again, I have attached he logs can you please check whats going on?
Thanks
Pat
Attachment | Size |
---|---|
484161-162223.log | 117 bytes |
484161-162226.log | 2.25 KB |
484161-162227.log | 38.88 KB |
484161-162228.log | 4.52 KB |
484161-162230.log | 4.52 KB |
484161-162233.log | 1.22 KB |
484161-162236.log | 150 bytes |
484161-162238.log | 87 bytes |
- Log in to post comments

As a further update, I have just examined the partitions of the ssd drive in the clone disk tool and its still shows the C: is using 98gb.. despite the fact we have got the c: on the old disk down to 67gb usage..how can this be resolved?
- Log in to post comments

Pat, thanks for the new logs, again, only the ti_demon log is of any value here, the others are just incidental.
The clone task log simply shows the exact same as the earlier log.
28/12/2018 10:15:13 :751 Operation Clone Disk started.
28/12/2018 10:15:13 :751 Operation description:
Clone Disk
1. Clearing disk Hard disk: 3
2. Clearing disk Hard disk: 3
3. Copying partition Hard disk: 1 -> 3 Drive letter: -
File system: NTFS Volume label: SYSTEM Size: 100 MB
4. Copying partition Hard disk: 1 -> 3 Drive letter: C:
File system: NTFS Volume label: OS Size: 451.2 GB -> 98.95 GB
5. Copying partition Hard disk: 1 -> 3 Drive letter: D:
File system: NTFS Volume label: HP_RECOVERY Size: 14.40 GB -> 12.64 GB
6. Copying partition Hard disk: 1 -> 3 Drive letter: - Type: 0x27 (Windows RE Hidden; PQ; MirOS) File system: FAT32 Volume label: HP_TOOLS Size: 101 MB -> 106 MB
7. Copying MBR Hard disk: 1 -> 3
1 of 2 - Acronis Universal Restore Use operating system drivers : Yes .
28/12/2018 10:16:59 :449 Pending operation 52 started: 'Clearing disk'.
28/12/2018 10:16:59 :449 Pending operation 52 started: 'Clearing disk'.
28/12/2018 10:16:59 :465 Pending operation 14 started: 'Copying partition'.
28/12/2018 10:17:49 :931 Pending operation 14 started: 'Copying partition'.
28/12/2018 11:16:10 :250 Pending operation 14 started: 'Copying partition'.
28/12/2018 11:16:10 :530 Error 0x101f6: A format/resize error.
28/12/2018 11:16:10 :530 Pending operation 14 started: 'Copying partition'.
28/12/2018 11:16:11 :279 Pending operation 61 started: 'Copying MBR'.
28/12/2018 11:17:05 :099 Error 0x13c0005: Operation has completed with errors.
This suggests that although you have reduced the size of your main OS partition, this is not being picked up by ATI as it is still saying that it can only reduce the OS C: partition to 98.95 GB.
If you haven't already done so, please try doing a full restart of Windows, then use the Disk Cleanup function for your drive C: (right-click on C: in Explorer, open the Properties then look for Disk Cleanup). The drive may also need to be defragmented.
Another option here may be to consider using a free partition tool such as MiniTool Partition Wizard to shrink your C: drive partition manually - this would allow you to see what the minimum size is that can be achieved.
Note: when adding logs to the forum, please zip them and add just a single zip file where the files inside the zip will keep their original names instead of being renamed as above.
- Log in to post comments

Hi Steve,
Since it looked like the c: had been copied onto the SSD via the clone utility I decided to unplug the old HDD and wire up the new SSD drive, and I was very happy when the windows login prompt came up (in 3 seconds!!).
I have since tried running all my apps that I use regularly and it appears to all be working fine albeit in turbo mode! :)
I'm happy with this , I am assuming that the errors may be relating to the recovery partition.. which I can live without to be honest..
Do you think I may encounter problems further down the line because the clone disk feature didnt 100% complete?
Kind regards
Pat
- Log in to post comments

Pat, if the new SSD is working and booting into Windows OK then I would suggest keeping your old HDD aside 'as is' while you do further general testing with the new drive, plus make a new disk backup of the SSD for good measure.
- Log in to post comments