Disk Cloning fails on format and copy of master boot record
Been using True Image 2019 all year to close the system drive of my Mac without any problem. Suddenly today it starts failing, so I upgrade the 2020 in the hope that will resolve it. Nope.
It starts the clone, begins the format and then fails and the destination drive remains uninitialised. I have a 256GB SSD system drive APFS volume. The destination is an external USB SSD. I have tried a different external drive, cable, USB port, so it's not hardware - same result.
Any ideas?


- Se connecter pour poster des commentaires

Hi Steve
I am running it from within Mac OS, as I've always done.
Below is the most recent error log:
2019-10-21T18:01:46:971+02:00 4618446272 I00000000: ——
2019-10-21T18:01:46:971+02:00 4618446272 I00000000: ATI Demon started. Version: 24.4.1.21810.
2019-10-21T18:01:46:978+02:00 4618446272 I013C0006: D9BC6651-EB22-47C5-AF42-C8A972FE9886
2019-10-21T18:01:46:990+02:00 4618446272 I00640002: Operation Clone Disk started manually.
2019-10-21T18:01:47:279+02:00 4618446272 I000101F8: Pending operation 53 started: 'Clearing disk’.
2019-10-21T18:01:47:294+02:00 4618446272 I000101F8: Pending operation 53 started: 'Clearing disk’.
2019-10-21T18:01:47:309+02:00 4618446272 I000101F8: Pending operation 53 started: 'Clearing disk’.
2019-10-21T18:01:47:324+02:00 4618446272 I000101F8: Pending operation 14 started: 'Copying and merging partitions’.
2019-10-21T18:01:47:355+02:00 4618446272 E000101F6: Error 0x101f6: A format/resize error.
| trace level: error
| line: 0x65b5eb7011094703
| file: /private/bs_hudson/workspace/master/1221/product/processor/diskadm/da_commit.cpp:348
| function: OnDaError
| line: 0x65b5eb7011094703, /private/bs_hudson/workspace/master/1221/product/processor/diskadm/da_commit.cpp:348, OnDaError
| $module: ti_demon_macia64_21810
|
| error 0x2160008: A format/resize error.
| line: 0xc75257350ce0fa60
| file: /private/bs_hudson/workspace/master/1221/product/core/da_api/context_context.cpp:1312
| function: Flush_
| line: 0xc75257350ce0fa60, /private/bs_hudson/workspace/master/1221/product/core/da_api/context_context.cpp:1312, Flush_
| $module: ti_demon_macia64_21810
|
| error 0x7000e: Directory is corrupted.
| line: 0x6b426cba4c49b6db
| file: /private/bs_hudson/workspace/master/1221/product/core/resizer/fat/fs_fat.cpp:569
| function: CheckFilterBitmap
| line: 0x6b426cba4c49b6db, /private/bs_hudson/workspace/master/1221/product/core/resizer/fat/fs_fat.cpp:569, CheckFilterBitmap
| $module: ti_demon_macia64_21810
2019-10-21T18:01:47:356+02:00 4618446272 I000101F8: Pending operation 17 started: 'Creating partition’.
2019-10-21T18:01:47:393+02:00 4618446272 I000101F8: Pending operation 62 started: 'Copying MBR’.
2019-10-21T18:02:16:540+02:00 4618446272 E00000000: Failed to get map of partitions to clone using disk numbers
2019-10-21T18:02:16:832+02:00 4618446272 E01EF0036: Error 0x1ef0036
| trace level: error
| line: 0x8ac4ae6694498032
| file: /private/bs_hudson/workspace/master/1221/product/products/imager/archive/impl/operations/disk_operation_clone.cpp:274
| function: RetrieveDiskPartitions
| line: 0x8ac4ae6694498032, /private/bs_hudson/workspace/master/1221/product/products/imager/archive/impl/operations/disk_operation_clone.cpp:274, RetrieveDiskPartitions
| $module: ti_demon_macia64_21810
2019-10-21T18:02:17:651+02:00 4618446272 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bced6
| file: /private/bs_hudson/workspace/master/1221/product/products/imager/demon/main.cpp:736
| function: main
| line: 0x9f2c53c72e8bced6, /private/bs_hudson/workspace/master/1221/product/products/imager/demon/main.cpp:736, main
| $module: ti_demon_macia64_21810
- Se connecter pour poster des commentaires

Ian, thanks for the log information, the format/resize error is normally caused by a problem on the source drive that prevents the resizing of a partition.
I would recommend doing a verify disk for the source drive to see if it throws up any errors that can be corrected.
What is the size of your target drive here given the source is 256GB?
- Se connecter pour poster des commentaires

Thanks Steve.
The target SSD drive is 240GB but only 70GB is used on the source drive. As I say this target drive has been working 100% for the past 9 months with not a single issue.
I have also tried a 500GB HDD target drive and it made no difference.
I currently have no backup of my system drive drive because of this fault, so a little nervous to be messing around with the system drive before I have a backup. Are you suggesting First Aid in Disk Utility, or what kind of verify disk operation?
Have there been any updates to True Image 2019 in the last month that would have caused this problem? I'm now on 2020 in the hope that it would resolve things, but just checking.
- Se connecter pour poster des commentaires

Ian, as mentioned earlier I am not a Mac user - the verify disk is from First Aid in the Disk Utility but found when I did a google search for the Mac equivalent of Windows CHKDSK.
One obvious (to me) question is to ask why you are doing a clone here and not making an Acronis disk backup of your source drive?
Cloning is normally more sensitive to disk issues than is backup, plus backup should allow you to make multiple backup images of just the used data size from your source drive.
- Se connecter pour poster des commentaires