Skip to main content

Cloning Failed (Resizing Issue?)

Thread solved

Hello,

Not sure if this is the properly place to post this, but I've recently purchased a SSD and am trying to clone my laptop HDD to it, but get an error that the cloning failed. Below is the log I found but am unsure what to do about this issue. Looks like the issue is related to resizing, but I can't understand what I need to do to fix it.

Can someone point me in a direction to follow up on?

Source is my installed HDD with 200GB used
Destination is my SSD (500GB capacity) connected via USB.

2019-12-03T20:19:18:070-06:00 17544 I00000000: -----
2019-12-03T20:19:18:070-06:00 17544 I00000000: ATI Demon started. Version: 24.5.1.22510.
2019-12-03T20:19:18:195-06:00 17544 E00000000: Failed to get incomplete backup plan id: Error 0x108: Failed to retrieve last activity from storage
| line: 0x36d5a3604309455b
| file: c:\bs_hudson\workspace\23\products\imager\after_restore_actions\impl\fix_activities.cpp:40
| function: `anonymous-namespace'::GetLastActivity
| line: 0x36d5a3604309455b, c:\bs_hudson\workspace\23\products\imager\after_restore_actions\impl\fix_activities.cpp:40, `anonymous-namespace'::GetLastActivity
| $module: ti_demon_vs_22510
2019-12-03T20:19:18:195-06:00 17544 I00640002: Operation Clone Disk started.
2019-12-03T20:19:18:195-06:00 17544 I00640000: Operation description: Clone Disk1. Clearing disk Hard disk: 2
2. Clearing disk Hard disk: 2
3. Copying and merging partitions Hard disk: 1, 2 -> 2Drive letter: -, - -> -File system: FAT32Volume label: Size: 260 MB, 260 MB -> 260 MB
4. Copying and merging partitions Hard disk: 1, 2 -> 2Drive letter: C:, C: -> C:File system: NTFSVolume label: WINDOWSSize: 914.3 GB, 450.4 GB -> 450.4 GB
5. Copying and merging partitions Hard disk: 1, 2 -> 2Drive letter: -, - -> -File system: NTFSVolume label: Size: 573 MB, 573 MB -> 573 MB
6. Copying and merging partitions Hard disk: 1, 2 -> 2File system: NoneSize: 980 MB, 980 MB -> 980 MB
7. Copying and merging partitions Hard disk: 1, 2 -> 2Drive letter: D:, D: -> D:File system: NTFSVolume label: RECOVERYSize: 15.37 GB, 13.51 GB -> 13.51 GB
8. Copying MBR Hard disk: 1 -> 2
.
2019-12-03T20:19:35:503-06:00 17544 I000101F8: Pending operation 53 started: 'Clearing disk'.
2019-12-03T20:19:35:503-06:00 17544 I000101F8: Pending operation 53 started: 'Clearing disk'.
2019-12-03T20:19:35:503-06:00 17544 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-12-03T20:19:42:533-06:00 17544 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-12-03T20:52:02:260-06:00 17544 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-12-03T20:52:10:242-06:00 17544 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-12-03T20:52:23:739-06:00 17544 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-12-03T20:52:23:848-06:00 17544 E000101F6: Error 0x101f6: A format/resize error.
| trace level: error
| line: 0x65b5eb7011094703
| file: c:\bs_hudson\workspace\23\processor\diskadm\da_commit.cpp:348
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094703, c:\bs_hudson\workspace\23\processor\diskadm\da_commit.cpp:348, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_22510
|
| error 0x2160008: A format/resize error.
| line: 0xc75257350ce0fa60
| file: c:\bs_hudson\workspace\23\core\da_api\context_context.cpp:1312
| function: context::Flush_
| line: 0xc75257350ce0fa60, c:\bs_hudson\workspace\23\core\da_api\context_context.cpp:1312, context::Flush_
| $module: ti_demon_vs_22510
|
| error 0x70008: Resizing is unavailable.
| line: 0x5738609e19dfe54b
| file: c:\bs_hudson\workspace\23\core\resizer\ntfs\fs_ntfs_resize.cpp:211
| function: resizer::NTFSProcessor::CalculateParameters
| line: 0x5738609e19dfe54b, c:\bs_hudson\workspace\23\core\resizer\ntfs\fs_ntfs_resize.cpp:211, resizer::NTFSProcessor::CalculateParameters
| $module: ti_demon_vs_22510
2019-12-03T20:52:23:848-06:00 17544 I000101F8: Pending operation 62 started: 'Copying MBR'.
2019-12-03T20:52:24:739-06:00 17544 I001D0000: Fixing operating system bootability.
2019-12-03T20:52:24:770-06:00 17544 I001D0000: The operating system bootability has been fixed.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Fixing operating system bootability.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(E551EFE44E5FB3517FC9C4A99E9A2D47)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(96B58BD54D5F9726C61B0D960E080B5B)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(E35B9A8F467F47C525B8B8B8902BC471)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(FE0827A74ED20BC9E2472CBE0D6D36C2)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(61DE31CB48387F649D685A8E754C40E1)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(8F830A214A7842DEA35FEE8BF9324E92)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(C5649DED4007F21E4B47F7AB8EF16172)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(9F9CFFFE413488D208091AB0C0F0B04A)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: Updating boot caches on volume '\local\hd_ev\vol_guid(103527854B036AEA665E608E089865E4)'.
2019-12-03T20:53:15:696-06:00 17544 I001D0000: The operating system bootability has been fixed.
2019-12-03T20:53:17:976-06:00 17544 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bced8
| file: c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738
| function: main
| line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738, main
| $module: ti_demon_vs_22510

0 Users found this helpful

Andrew, 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.

Given the resizing error that the log is showing, this can suggest that there may be a filesystem issue on your source drive which then prevents the partitions from being reduced to a size that is required.

Please run CHKDSK /F against all the partitions on your source 1TB HDD then I would recommend going into Windows Disk Management and selecting the main C: OS partition then try using the option to Shrink the size of this partition to see if you can shrink it to around 400GB in size.  If the Shrink option shows that such a size cannot be achieved, then download a copy of the free MiniTool Partition Wizard software and try using this to resize that same OS partition to 400GB (leaving the free space as unallocated).

Once you have done the above, then retry doing the clone as per the recommended method above.

Hey Steve,

Thank you so much for the swift response will try this and post if this is the solution

Awesome. Problem solved.

 

When in doubt follow the documentation.

It's a little daunting to on a laptop, ran into a couple of boot issues with the bios but success in the end.

 

SSD FTW!

Andrew, thanks for the feedback and great that the problem is solved!