Easy Way to make a Bootable Clone of your macOS System Drive

[Blindedbythelights]

There's a couple of possible reasons why you got the "unable to lock the disk" error. If you were using a version of Acronis older than 2017 that does not support GPT drives or the person who created your dual boot may have partitioned the drive MBR instead of GPT. I don't know what they actually did so I would suggest you follow the HS or Mojave installation guide on this site and perform a clean installation to the M.2 drive from a Unibeast installer. Of course, you'll need to disconnect the dual boot Windows/macOS drive when doing this. All the info and tools you need are here to do this. Follow the guide for which version of macOS you need. You can create the Unibeast installer on your Macbook or boot from your CCC backup drive and use that.

View attachment 364259

In step 6 of the installation guide make sure that the partition scheme is GPT. It doesn't specifically say that, but check to make sure that is selected in Disk Utility.

6. For a new installation of macOS, you MUST erase and format the destination drive according to the following steps before continuing.
a. In the top menu bar choose Utilities, and open Disk Utility
b. Highlight your target drive for the Mojave installation in left column.
c. Click Erase button
d. For Name: type Mojave (You can rename it later)
e. For Format: choose Mac OS Extended (Journaled) Scheme: GUID
f. Click Erase
g. Close Disk Utility

View attachment 364312

Many of the moderators some of the members here do not even boot macOS with a Windows drive connected to their PC at the same time to avoid issues between macOS and Windows. Primarily file and EFI partition corruption and data loss.

Some will use hot swap bays and physically remove the HDD or SSD that the OS is installed upon. The other option is to simply disconnect the the sata cable from the drive you are not booting from before you power on the machine.

If you can't tolerate any down time that is the safest way to dual boot on the same machine. Especially if you use macOS for your work to earn a living.

Thanks for your input. So I'd heard that my issue which was boot would hang on "Start ReadKernelCache" seemed to be memory related, I tried reverting to some older BIOS settings.

Before I’d tried to do this backup task that failed, I was able to boot with igpu enabled, (using the multi monitor enable option in MSI bios) and I’d set the RAM to max which is 64mb only on my system. This had successfully enabled quick sync which I wanted.

However now it won’t let me boot with igpu enabled or maybe 64mb isn’t enough, even though whatevergreen is suppose to fix that and it did not have a problem with this before.

So I’m able to boot with multi monitor disabled.

Just find it odd that I used to be able to boot with igpu on, but now I can’t. I wonder what changed.

Anyway its good enough for now. Thank you.

 

[Blindedbythelights]

lastly, I've found I need "Above 4G Decoding" on in my BIOS so that I can boot with igpu on. So I'm all back to normal, no issues booting into both OS on same SSD. Will be sticking with only carbon copy cloner for now as this Acronis solution did not work for me on a single boot disk.

 

[Bob_the_Tomato]

Sooo, to add to this post....
I was about to recreated a clone of my boot drive using the same HDD from my previous effort but now ATI won't proceed...

So I tried to use CCC in OSX and CCC reports this error:

If you go to their website you get this:

That line about Do not use on a Hackintosh bothers me...


So now I have a backup/clone that doesn't boot and won't update with CCC.

Time to wipe the HDD and start over.

 

[colomb]

Using Win10XPE_1803R_180908_x64 and I can't get passed the exclude files portion of Acronis. Clicking the next button pops a window that disappears immediately. Trying an older version.

 

[themisses]

I have just cloned my nvme 1tb samsung drive to a 1tb samsung mechanical drive and then booted off the clone with the original boot drive (and all other disks) removed from pc.
I used Hirens boot cd PE x64 and specifically" Lazesoft Disk Image & Clone v4.0.0.1" after I had booted off the cd I had burned, so a free and simple solution. OS High Sierra Apfs, it took about two hours or so to clone.Hope this helps.

 

[trs96]

Easy Way to Clone your Boot Drive with Acronis 2019
​

With this newest version you don't need to use a WinPE external drive to make your clone of macOS. If you can buy the software on Amazon at a decent price it's definitely worth it for the sake of convenience and ease of use. This is a one time purchase, not a 1 year subscription, so you can use it for as many years as you'd like to.

Here's the link to get a free 30 day trial of Acronis T. I. 2019.
https://www.acronis.com/en-us/lp/personal/time-machine-backup/

This video is by Jeff Benjamin at 9 to 5 Mac. You can view the whole thing on their website if you'd like to learn more about what it can do. The incremental backups feature is nice to have too.

https://www.amazon.com/dp/B07GVW24MP/?tag=tonymacx86com-20

This is worth the 38 dollar investment if you are constantly testing new things or updating your Hackintosh often.

Newegg also sells it at the retail price of $49.99 if you prefer to shop there. Buy Acronis at Newegg

Here are some of the great features you get with Acronis 2019

​

NOTE: Do not buy the pirated ISO versions that some sellers on Ebay list for $3.99 to $4.99. Those are simply cracked versions you don't want.

 

[trs96]

UPDATE: How to make a bootable backup of your system drive with Acronis 2020​

I need to preface this with the fact that this approach is many times more complicated than simply buying a license to use the Cloning function via the Acronis Rescue USB. It's more confusing (for novices) and takes three times as much time to complete. If you have the money to buy the PC version of Acronis and make a bootable rescue USB that is the better way to go. Since any kind of backup is better than none. Only try this method if you can't get the technique in post #1 of this thread to work.

Many people choose CCC because it offers a free trial that can be used to clone your macOS system drive. There is now a way to make a bootable copy of your macOS drive for free with Acronis too. It takes a little more time and effort for those that have more free time than money at their disposal.

1. Download the Mac trial version of Acronis on your hackintosh and install it. An account is required.

Acronis Cyber Protect Home Office (formerly Acronis True Image) - Free 30-day Trial - Download

✅ 1 TB of Acronis Cloud included, ✅ Mirror imaging/full image backups, ✅ Individual file and folder backup, ✅ Boot media builder and recovery tool, ✅ Blockchain-based file authentication & More features

www.acronis.com

2. Make a complete backup image to another drive, preferably 120 GB or smaller SSD if everything fits. If your system drive size is slightly larger than 120 GB it will be compressed into a .TIB file so it will still fit on the 120 GB backup drive.

Important Point: Your backup image drive should not be formatted HFS+ or APFS - When you boot from the Acronis rescue USB (WinPE based) it won't be able to read either of those file formats. Best to use an EXFAT formatted drive because your image will certainly be over 4GB is size.

2.5 The .TIB file is not bootable as is. It needs to be recovered to a different drive.
The following steps will help to make a bootable drive that works the same way as a cloned drive.

3. Make a bootable Acronis rescue USB on a Windows PC. See: https://kb.acronis.com/content/61632
This of course requires the PC version of Acronis. Use the link from step #1.
Sign in with the same account you already created when installing the Mac version of Acronis.

You'll want to use either a Windows 8.1 or 10 PC that is booting UEFI to make your rescue USB.
This is because it's likely your hack is booting UEFI only also. Simplifies the whole process.
(The Mac version of an Acronis rescue USB is not bootable on a hackintosh, only on a Mac)

4. Next boot from the USB you just made on a PC on your hackintosh computer.

5. Now you need to recover the Disk backup image to a different drive. The drive that you will recover to must be as large or larger than the one you've initially backed up from. You'll want to connect the drive you are recovering to, to an internal Sata connection not to external USB.

Go to the Recovery tab. If you used a Cloud backup Click on Browse for Backups and sign into your Cloud storage account to locate the image.

6. Make sure to select "Recover the whole disk" Sector by Sector

7. You'll need to make sure to select (checkmark) the EFI partition as well as the APFS volume of your backup image.

8. After the recovery is complete connect only that drive in your hackintosh and test whether it boots.

See the Acronis Knowledge Base site for complete guides and tutorials on the whole process.

That's it. Even without the disk cloning option available in the paid version, you can create
the exact same kind of bootable drive for free. Enjoy !

 

[IanH]

Hi trs96

Following up from my posts yesterday... unfortunately we are completely Mac here, so I don't have access to a Windows machine to try the process in post #1.

A summary of where I am so far:

1 - Bought Acronis 2019 in January

2 - Disk cloning on System drive of my hack worked perfectly until around the middle of this year (can't say exactly because I was doing this infrequently) - this is by running Acronis 2019 on the system drive of the Hackintosh and using disk clone on a 240GB external USB SSD of my similar system drive.

3 - Disk cloning then stopped working, with the error log below.
- formatting seems to go ok
- then it says 'Coping MBR'
- and then it switches to 'Synchronising operating system' and throws out an error message: 'The disk you inserted was not readable' and the below error log...

4 - Upgraded to Acronis 2020 to no avail.

5 - Acronis support can't help at all. They say they haven't changed anything that would create this error.

Can anyone else confirm that disk clone of the system disk using Acronis 2019/2020 running on the same system drive is still working 100% for them and creating a bootable copy?

many thanks
Ian



2019-11-01T10:30:56:870+02:00 4814968256 I00000000: -----
2019-11-01T10:30:56:870+02:00 4814968256 I00000000: ATI Demon started. Version: 24.4.1.21810.
2019-11-01T10:30:56:877+02:00 4814968256 I013C0006: 0BEA245F-4E5F-40CE-AA65-8A84329735D9
2019-11-01T10:30:56:910+02:00 4814968256 I00640002: Operation Clone Disk started manually.
2019-11-01T10:30:57:240+02:00 4814968256 I000101F8: Pending operation 53 started: 'Clearing disk'.
2019-11-01T10:30:57:246+02:00 4814968256 I000101F8: Pending operation 53 started: 'Clearing disk'.
2019-11-01T10:30:57:251+02:00 4814968256 I000101F8: Pending operation 53 started: 'Clearing disk'.
2019-11-01T10:30:57:256+02:00 4814968256 I000101F8: Pending operation 14 started: 'Copying and merging partitions'.
2019-11-01T10:30:57:276+02:00 4814968256 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-11-01T10:30:57:276+02:00 4814968256 I000101F8: Pending operation 17 started: 'Creating partition'.
2019-11-01T10:30:57:299+02:00 4814968256 I000101F8: Pending operation 62 started: 'Copying MBR'.
2019-11-01T10:31:26:537+02:00 4814968256 E00000000: Failed to get map of partitions to clone using disk numbers
2019-11-01T10:31:26:700+02:00 4814968256 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-11-01T10:31:27:604+02:00 4814968256 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

 

[IanH]

OK, got the original Acronis off Time Machine and installed that, and it's definitely not an Acronis problem, because the same failure occurred.

Can anyone more savvy than me help here? It seems like there may be some kind of corrupt partition on my system drive, but I can't understand what. This is the error log from Acronis 2019:



2019-11-20T10:54:06:901+02:00 4553975232 I00000000: -----
2019-11-20T10:54:06:902+02:00 4553975232 I00000000: ATI Demon started. Version: 23.4.1.17000.
2019-11-20T10:54:06:904+02:00 4553975232 I013C0006: 26D43F23-411A-42D5-BFF7-E1B1369AF64B
2019-11-20T10:54:06:907+02:00 4553975232 I00640002: Operation Clone Disk started manually.
2019-11-20T10:54:09:958+02:00 4553975232 I000101F8: Pending operation 52 started: 'Clearing disk'.
2019-11-20T10:54:09:972+02:00 4553975232 I000101F8: Pending operation 52 started: 'Clearing disk'.
2019-11-20T10:54:09:986+02:00 4553975232 I000101F8: Pending operation 52 started: 'Clearing disk'.
2019-11-20T10:54:09:999+02:00 4553975232 I000101F8: Pending operation 14 started: 'Copying partition'.
2019-11-20T10:54:10:025+02:00 4553975232 E000101F6: Error 0x101f6: A format/resize error.
| trace level: error
| line: 0x65b5eb7011094703
| file: /private/bs_hudson/workspace/master/621/product/processor/diskadm/da_commit.cpp:348
| function: OnDaError
| line: 0x65b5eb7011094703, /private/bs_hudson/workspace/master/621/product/processor/diskadm/da_commit.cpp:348, OnDaError
| $module: ti_demon_macia64_17000
|
| error 0x2160008: A format/resize error.
| line: 0xc75257350ce0fac4
| file: /private/bs_hudson/workspace/master/621/product/core/da_api/context_context.cpp:1412
| function: Flush_
| line: 0xc75257350ce0fac4, /private/bs_hudson/workspace/master/621/product/core/da_api/context_context.cpp:1412, Flush_
| $module: ti_demon_macia64_17000
|
| error 0x7000e: Directory corrupted
| line: 0x6b426cba4c49b721
| file: /private/bs_hudson/workspace/master/621/product/core/resizer/fat/fs_fat.cpp:639
| function: CheckFilterBitmap
| line: 0x6b426cba4c49b721, /private/bs_hudson/workspace/master/621/product/core/resizer/fat/fs_fat.cpp:639, CheckFilterBitmap
| $module: ti_demon_macia64_17000
2019-11-20T10:54:10:025+02:00 4553975232 I000101F8: Pending operation 17 started: 'Creating partition'.
2019-11-20T10:54:10:048+02:00 4553975232 I000101F8: Pending operation 61 started: 'Copying MBR'.
2019-11-20T10:54:10:059+02:00 4553975232 E00000000: Source and destination partition counts are different
2019-11-20T10:54:10:080+02:00 4553975232 I00390007: Error 0x390007: Failed to detect GRUB loader.
| trace level: information
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
|
| error 0x390007: An invalid sector size.
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
2019-11-20T10:54:10:081+02:00 4553975232 I00390007: Error 0x390007: Failed to detect GRUB loader.
| trace level: information
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
|
| error 0x390007: An invalid sector size.
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
2019-11-20T10:54:10:081+02:00 4553975232 I00390007: Error 0x390007: Failed to detect GRUB loader.
| trace level: information
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
|
| error 0x390007: An invalid sector size.
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
2019-11-20T10:54:10:081+02:00 4553975232 I00390007: Error 0x390007: Failed to detect GRUB loader.
| trace level: information
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
|
| error 0x390007: An invalid sector size.
| line: 0x5186ab5c3563a8cd
| file: /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415
| function: Create
| line: 0x5186ab5c3563a8cd, /private/bs_hudson/workspace/master/621/product/core/products/oss/cfg_os/grub_supp/grub_internal.cpp:415, Create
| $module: ti_demon_macia64_17000
2019-11-20T10:54:10:379+02:00 4553975232 E01EF0032: Error 0x1ef0032
| trace level: error
| line: 0x8ac4ae669449809e
| file: /private/bs_hudson/workspace/master/621/product/products/imager/archive/impl/operations/disk_operation_clone.cpp:382
| function: Commit
| line: 0x8ac4ae669449809e, /private/bs_hudson/workspace/master/621/product/products/imager/archive/impl/operations/disk_operation_clone.cpp:382, Commit
| $module: ti_demon_macia64_17000
2019-11-20T10:54:11:182+02:00 4553975232 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcebf
| file: /private/bs_hudson/workspace/master/621/product/products/imager/demon/main.cpp:713
| function: main
| line: 0x9f2c53c72e8bcebf, /private/bs_hudson/workspace/master/621/product/products/imager/demon/main.cpp:713, main
| $module: ti_demon_macia64_17000

 

[rhhousehold]

I’ve been making successful clones of my 3 macs using spare / old SATA disks of various sizes that work for each SSD/NVMe drive — and manually copying over the EFI folders which is easy.

Never before did I think these old SATA disks would be so useful, but now there is a use for them. Almost pitched some as Ewaste.