Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Carbon Copy Cloner - Unsupported for patched systems.
- Thread starter lovely666
- Start date
- Sort by reaction score
Speaking of Monterey, does anyone know what is the last 12.x.y version-number for which CCC6.1.1 is able to successfully create a Legacy Bootable clone of the active volume that (important) is actually treated as the original rather than a copy by the OS (i.e., won't have reduced permissions or other restriction, such as full access to system updates)? (This is for non-silicon systems.)
I've been running OCLP Monterey on my Mac Pro 5,1 2009 for a couple of years and it's been rock solid but now out of the blue I'm suddenly having startup disc problems. I have a system backup SSD in the DVD caddy space which I update from time to time with Carbon Copy Cloner. Of course I realise I can't actually boot from this but nonetheless it has saved my bacon on a few occasions and I'd like to keep it. Trouble is now this backup drive now seems to be appearing as my startup drive and the actual OCLP drive isn't even an option. I can't update OpenCore either because the updater wants to update the back up drive which it thinks is my startup drive. Booting with control key doesn't bring up the boot picker as it used to so I'm a bit at a loss.
Anyone else seen this before?
Anyone else seen this before?
I've always used OPTN to bring up the bootpicker, since the G4. Is OPTN what you meant? As far as I know, the CTRL key does nothing at boot.
Actually the control key thing turned out to be an intermittent problem with the the keyboard. I've swapped it out now and I get there boot picker again but it doesn't help because the disk that Opencore is installed on is not an option. I know that sounds crazy but that's what's happening. I get four options: The cloned system disk created by Carbon Copy Cloner (which obviously can't be booted to), 2 identical EFI Boot options and 'Recovery-10.11.6'
I've just noticed that I now have a folder at the top level of my actual system folder called 'Previous Content' which contains a folder call 'boot' which contains 79 .im4m files (eg. boot.efi.j132ap.im4m).
I can no longer update Opencore either because when it comes to 'select target disc' it defaults to the cloned drive and won't accept the actual system drive. Also in system prefs the cloned drive is the only available option.
Essentially Opencore doesn't seem to know which disk it's running on. Baffling. I don't know whether to take out the cloned drive and see what happens. Bit of a chore since it's in the old DVD bay but also I'm a bit wary of screwing the OS all together as I have a fairly big project to finish next week.
I've just noticed that I now have a folder at the top level of my actual system folder called 'Previous Content' which contains a folder call 'boot' which contains 79 .im4m files (eg. boot.efi.j132ap.im4m).
I can no longer update Opencore either because when it comes to 'select target disc' it defaults to the cloned drive and won't accept the actual system drive. Also in system prefs the cloned drive is the only available option.
Essentially Opencore doesn't seem to know which disk it's running on. Baffling. I don't know whether to take out the cloned drive and see what happens. Bit of a chore since it's in the old DVD bay but also I'm a bit wary of screwing the OS all together as I have a fairly big project to finish next week.
You have stated this twice now. Why do you believe a CCC cloned disk can't be booted❓ I have used CCC for a few years. I'm now on Tahoe Beta with my M2 Ultra Mac Pro. When done properly, a CCC backup of the Start-Up disk will boot just fine. As I said, I've been doing it for years 👍
Lou
I believe it because that's what a rep from Bombich told me some time ago (at least from Monterey and later as I recall). That's why I didn't think it was worth the paid upgrade because that's pretty much all I used it for. From what you say they've solved that problem. Thanks, I'll check with them to confirm.
Well it certainly didn't work for me as booting from the clone consistently gives me a white screen crash and forced reset.
According to the below the legacy code used for macOS cloning is the same as I have in my version. I remember the rep told me the limitation was something to with "blessing" the system install. I'll check out the firmware discoverability Troubleshooting steps noted below.
"The macOS System resides on a "Signed System Volume". This volume is cryptographically sealed, and that seal can only be applied by Apple; ordinary copies of the System volume are non-bootable without Apple's seal. When you configure a CCC backup task using the Legacy Bootable Copy Assistant, CCC will automatically use Apple's proprietary APFS replication utility (ASR) to make a block-for-block exact copy of the source. If that does not produce a bootable volume, and if you have exhausted the Firmware Discoverability Troubleshooting steps below, then we recommend that you install macOS onto the backup. If that does not produce a bootable device, then the device is not suitable for functioning as a bootable device on your Mac."
According to the below the legacy code used for macOS cloning is the same as I have in my version. I remember the rep told me the limitation was something to with "blessing" the system install. I'll check out the firmware discoverability Troubleshooting steps noted below.
"The macOS System resides on a "Signed System Volume". This volume is cryptographically sealed, and that seal can only be applied by Apple; ordinary copies of the System volume are non-bootable without Apple's seal. When you configure a CCC backup task using the Legacy Bootable Copy Assistant, CCC will automatically use Apple's proprietary APFS replication utility (ASR) to make a block-for-block exact copy of the source. If that does not produce a bootable volume, and if you have exhausted the Firmware Discoverability Troubleshooting steps below, then we recommend that you install macOS onto the backup. If that does not produce a bootable device, then the device is not suitable for functioning as a bootable device on your Mac."
^^^^You may want to read this thread:
Lou
Lou