Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Carbon Copy Cloner 7 - Users Thread

I have not gotten any comments on the proposed method of creating a “Bootable Backup”. Since I am not a computer person and don’t know if what I am doing is right, I wrote to Mr. Bombich and asked him. Below is his reply:

“Only two comments:
He didn’t say the method is wrong, so I assume it is correct, but he said that “I expect that the destination will eventually not be bootable, e.g. perhaps after an update is applied to the source”.

But I think that this method is different as it does not involve copying the system volume source and does not use apple’s ASR and , as a result, it should remain bootable and backuptable after update/upgrade.

To prove the method remains “bootable and backuptable after update/upgrade”, I would need to do an update/upgrade. My problem is that I have a 10-year-old Mac, the latest OS it could support is Mohave. I am using OCLP to run 14.7.2 and 15.2. Whenever I tried update or upgrade, the mac would get stuck at the progress bar and fail. But this may be because the Mac is just too old.

My income is limited and couldn’t justify to buy a new mac for this purpose.

In the interest of satisfying curiosity, I sincerely hope that some members with a newer Mac could try this method on 14.7.2 then see if the bootable backup could be upgraded to 15.2 and remains functional after the upgrade.
 
dai-leung said:
I have not gotten any comments on the proposed method of creating a “Bootable Backup”. Since I am not a computer person and don’t know if what I am doing is right, I wrote to Mr. Bombich and asked him. Below is his reply:

“Only two comments:
He didn’t say the method is wrong, so I assume it is correct, but he said that “I expect that the destination will eventually not be bootable, e.g. perhaps after an update is applied to the source”.

But I think that this method is different as it does not involve copying the system volume source and does not use apple’s ASR and , as a result, it should remain bootable and backuptable after update/upgrade.

To prove the method remains “bootable and backuptable after update/upgrade”, I would need to do an update/upgrade. My problem is that I have a 10-year-old Mac, the latest OS it could support is Mohave. I am using OCLP to run 14.7.2 and 15.2. Whenever I tried update or upgrade, the mac would get stuck at the progress bar and fail. But this may be because the Mac is just too old.

My income is limited and couldn’t justify to buy a new mac for this purpose.

In the interest of satisfying curiosity, I sincerely hope that some members with a newer Mac could try this method on 14.7.2 then see if the bootable backup could be upgraded to 15.2 and remains functional after the upgrade.
Click to expand...
You have been told multiple times to forget about a bootable drive. Asking the same thing over and over isn’t going to change the answer and people will stop responding.
 
  • Like
Reactions: eldho, gilby101 and Realityck
Your point is well taken. So sorry, will stop asking questions on that topic and sorry to waste all your time! I thought, by mistake, it was a topic of interest My apology.
 
dai-leung said:
I have not gotten any comments on the proposed method of creating a “Bootable Backup”. Since I am not a computer person and don’t know if what I am doing is right, I wrote to Mr. Bombich and asked him. Below is his reply:

“Only two comments:
He didn’t say the method is wrong, so I assume it is correct, but he said that “I expect that the destination will eventually not be bootable, e.g. perhaps after an update is applied to the source”.

But I think that this method is different as it does not involve copying the system volume source and does not use apple’s ASR and , as a result, it should remain bootable and backuptable after update/upgrade.

To prove the method remains “bootable and backuptable after update/upgrade”, I would need to do an update/upgrade. My problem is that I have a 10-year-old Mac, the latest OS it could support is Mohave. I am using OCLP to run 14.7.2 and 15.2. Whenever I tried update or upgrade, the mac would get stuck at the progress bar and fail. But this may be because the Mac is just too old.

My income is limited and couldn’t justify to buy a new mac for this purpose.

In the interest of satisfying curiosity, I sincerely hope that some members with a newer Mac could try this method on 14.7.2 then see if the bootable backup could be upgraded to 15.2 and remains functional after the upgrade.
Click to expand...
I think the era of bootable backup drive is over because the hardware is so different.

It used to be that hard drives failed, and we’d buy a new one and restore from backup. Or we’d boot from the backup and just use that.

But today we boot from soldered SSD’s and if they fail the computer is toast, because also the motherboard has a soldered security chip. The OS boots from a signed partition for security.

So all these things converge to make boootabl backup drives a thing of the past. It’s also made removable storage a thing of the past, which most people really hate.
 
I don’t have a modern Mac thus, lack the experience of using one, but appreciate your explanation!

Alameda said:
But today we boot from soldered SSD’s and if they fail the computer is toast,
Click to expand...

So for the new Macs, it either works or does not work. When the Mac fails, “we’d buy a new one and restore from backup”. Just wondering if my understanding is correct.

"It’s also made removable storage a thing of the past…” —- don’t quite understand what you meant. Have time to explain?
 
dai-leung said:
I don’t have a modern Mac thus, lack the experience of using one, but appreciate your explanation!



So for the new Macs, it either works or does not work. When the Mac fails, “we’d buy a new one and restore from backup”. Just wondering if my understanding is correct.

"It’s also made removable storage a thing of the past…” —- don’t quite understand what you meant. Have time to explain?
Click to expand...
I meant, removable internal storage. It used to be that you could just pull a hard drive or SSD card out of a laptop and replace it. But with current Macs, that is no longer the case.

What I’m trying to say is that there are good reasons for backup, but not really for a bootable backup because of how Apple security and their hardware work now.
 
Would anyone care to share their thoughts on backing up the Photos library?
I use iCloud Photo Library with 'Download Originals to the this Mac'.
I use CCC to create a clone, with snapshots, of the whole Data volume.

If my machine died, I could login to a new machine and either:
Login to iCloud and let my library redownload
Restore from the CCC backup using migration assistant

If my iCloud account was locked out/iCloud Photo Library was lost, I could restore the Photos Library file from the CCC backup and upload it to a new iCloud account or reupload it to my existing account.

Soon I plan to do a test restore of the Photos library (which has been updated with many snapshots over the previous 3 years) to a fresh local user account (with iCloud disabled).

I don't have any ideas on detecting corruption/deletion of individual photos in the library.
 
Been neglecting checking for CCC updates because there wasn't any for weeks.

CCC 7.1-b3 (8111) is now available — This is a pre-release update of CCC 7.0.4 (8082)
  • This version of CCC embraces new macOS functionality that allows us to avoid installing the CCC helper tool into Macintosh HD > Library > PrivilegedHelperTools. The helper tool will be "registered" with macOS, but will remain inside of the CCC application bundle. This new practice resolves a long list of complications that have arisen over the years with the legacy LaunchDaemon configuration as Apple has improved macOS platform security.
  • New
    CCC includes a new Privileged Activity Registration Assistant. While there are numerous benefits to the new SMAppService approach to registering CCC's helper tool, the new subsystem has its own quirks. Most of these quirks are limited to macOS Ventura, and typically folks should only see the registration assistant when installing CCC for the first time. Re-registration is required, however, when the CCC application is moved. CCC usually handles that automatically as well, although, on Ventura, some additional interaction with System Settings is required. If you have an interaction with the Helper Tool Registration Assistant window, please share your feedback if it could have gone better. Choose "Report a problem" from CCC's Help menu to share your feedback. That isn't necessarily a "problem", but we're aiming for "minimal required interaction" for existing installations of CCC, and we really, really want this to go smoothly once it is rolled out to hundreds of thousands of existing CCC users.
  • New
    Full Disk Access is no longer required separately for CCC's helper tool. CCC's coaching around this procedure has been updated to reflect the new requirement. No changes should be required for current CCC installations.
  • New
    CCC offers new UI in Settings > Advanced to specify the authorization requirements for a variety of CCC activities. For example, you may wish to require an admin user for CCC task changes, but allow non-admin users to start/stop tasks. Now you can configure that with ease in Advanced Settings.
  • Changed
    If a task is configured to restart or shut down the system "after a 60 second delay", that delay will no longer be applied when the screen is locked. In those cases macOS will not present the restart/shutdown dialog at all, so CCC proceeds directly to the request instead. This does not affect the fate of unsaved documents. If an application requires attention before it can quit, that application will cancel the restart/shutdown request even if the screen is locked.
  • Changed
    The "MobileSoftwareUpdate" folder is now hidden by default on the destination. This folder is technically not hidden at the root of the startup disk, but it's not exposed via a firmlink, and it exists exclusively on the Data volume, so it effectively does not appear in the Finder.
  • Changed
    Added wildcard and regular expression support to the Snapshot Comparison Browser search field.
  • Changed
    In the Tasks tab of the CCC Dashboard application, the "Defer…" option is now available for any scheduled task even when that task is not running. This allows the user to proactively defer a task before its scheduled run time rather than having to wait until the task is actually running.
  • Fixed
    b2: Fixed a CloneKitService crasher.
  • New
    b2: Spotlight will now be disabled by default when selecting the option to use a destination volume exclusively for the CCC task in the Backup Volume Setup Assistant. Users can also select a volume in the sidebar and disable (or re-enable) Spotlight via a switch. This change will hopefully address the interference that Spotlight and its mediaanalysisd buddy are causing with regard to unmounting the CCC destination volume.
  • Fixed
    b2: Fixed an issue in which CCC would report problems with setting attributes on files larger than 1GB when backing up to and from an SSD.
  • Fixed
    b3: Fixed a stall that could occur when attempting to copy 0-byte sparse files.
  • Changed
    b3: Added feedback for non-admin users when they try to perform a task for which they are not authorized. The dialog will explain which privilege is required for the activity, and will prod them towards the Settings UI where the privilege requirements can be modified.

The system requires enabling a second CCC helper to be enabled after update for CCC to work immediately.
 
Last edited:
flowrider said:
Is this True:

www.powerpage.org

Apple repairs possible Replicator bug in macOS Sequoia 15.3 update, eases path for third-party utilities to create bootable backup volumes

Apple seems to be getting closer to fixing a bug that allows for third-party utilities to create bootable backup volumes. Per SuperDuper! developer Dave Nainan, Apple’s recently-released macOS Sequoia…
www.powerpage.org www.powerpage.org

Hasn't affected me with my 7,1 Intel Mac Pro, but understand AS Macs had a problem.

Lou
Click to expand...
I verified this was fixed in the 15.3 public release yesterday on a 16” M1 Max MBP and a 14” M4 Pro MBP. The legacy bootable snapshot is back to how it was before 15.2.
 
CCC 7.1-b4 (8115) is now available — This is a pre-release update of CCC 7.0.4 (8082)
  • This version of CCC embraces new macOS functionality that allows us to avoid installing the CCC helper tool into Macintosh HD > Library > PrivilegedHelperTools. The helper tool will be "registered" with macOS, but will remain inside of the CCC application bundle. This new practice resolves a long list of complications that have arisen over the years with the legacy LaunchDaemon configuration as Apple has improved macOS platform security.
  • New
    CCC includes a new Privileged Activity Registration Assistant. While there are numerous benefits to the new SMAppService approach to registering CCC's helper tool, the new subsystem has its own quirks. Most of these quirks are limited to macOS Ventura, and typically folks should only see the registration assistant when installing CCC for the first time. Re-registration is required, however, when the CCC application is moved. CCC usually handles that automatically as well, although, on Ventura, some additional interaction with System Settings is required. If you have an interaction with the Helper Tool Registration Assistant window, please share your feedback if it could have gone better. Choose "Report a problem" from CCC's Help menu to share your feedback. That isn't necessarily a "problem", but we're aiming for "minimal required interaction" for existing installations of CCC, and we really, really want this to go smoothly once it is rolled out to hundreds of thousands of existing CCC users.
  • New
    Full Disk Access is no longer required separately for CCC's helper tool. CCC's coaching around this procedure has been updated to reflect the new requirement. No changes should be required for current CCC installations.
  • New
    CCC offers new UI in Settings > Advanced to specify the authorization requirements for a variety of CCC activities. For example, you may wish to require an admin user for CCC task changes, but allow non-admin users to start/stop tasks. Now you can configure that with ease in Advanced Settings.
  • Changed
    If a task is configured to restart or shut down the system "after a 60 second delay", that delay will no longer be applied when the screen is locked. In those cases macOS will not present the restart/shutdown dialog at all, so CCC proceeds directly to the request instead. This does not affect the fate of unsaved documents. If an application requires attention before it can quit, that application will cancel the restart/shutdown request even if the screen is locked.
  • Changed
    The "MobileSoftwareUpdate" folder is now hidden by default on the destination. This folder is technically not hidden at the root of the startup disk, but it's not exposed via a firmlink, and it exists exclusively on the Data volume, so it effectively does not appear in the Finder.
  • Changed
    Added wildcard and regular expression support to the Snapshot Comparison Browser search field.
  • Changed
    In the Tasks tab of the CCC Dashboard application, the "Defer…" option is now available for any scheduled task even when that task is not running. This allows the user to proactively defer a task before its scheduled run time rather than having to wait until the task is actually running.
  • Fixed
    b2: Fixed a CloneKitService crasher.
  • New
    b2: Spotlight will now be disabled by default when selecting the option to use a destination volume exclusively for the CCC task in the Backup Volume Setup Assistant. Users can also select a volume in the sidebar and disable (or re-enable) Spotlight via a switch. This change will hopefully address the interference that Spotlight and its mediaanalysisd buddy are causing with regard to unmounting the CCC destination volume.
  • Fixed
    b2: Fixed an issue in which CCC would report problems with setting attributes on files larger than 1GB when backing up to and from an SSD.
  • Fixed
    b3: Fixed a stall that could occur when attempting to copy 0-byte sparse files.
  • Changed
    b3: Added feedback for non-admin users when they try to perform a task for which they are not authorized. The dialog will explain which privilege is required for the activity, and will prod them towards the Settings UI where the privilege requirements can be modified.
  • New
    b4: Added an option to the ccc command-line utility to perform snapshot thinning and pruning on a specified volume according to its current Snapshot Retention Policy.
  • Changed
    b4: Addressed a race condition that could cause CCC to fail a task, claiming that the destination is unavailable, despite having just mounted it.
  • Changed
    b4: Addressed a scenario where CCC may not quit upon request if CCC snapshots are mounted.
  • New
    b4: CCC Dashboard's "Suspend all tasks" dialog now offers a date picker option.
 
  • Like
Reactions: flowrider
CCC 7.1-b5 (8117) is now available — This is a pre-release update of CCC 7.0.4 (8082)
  • This version of CCC embraces new macOS functionality that allows us to avoid installing the CCC helper tool into Macintosh HD > Library > PrivilegedHelperTools. The helper tool will be "registered" with macOS, but will remain inside of the CCC application bundle. This new practice resolves a long list of complications that have arisen over the years with the legacy LaunchDaemon configuration as Apple has improved macOS platform security.
  • New
    CCC includes a new Privileged Activity Registration Assistant. While there are numerous benefits to the new SMAppService approach to registering CCC's helper tool, the new subsystem has its own quirks. Most of these quirks are limited to macOS Ventura, and typically folks should only see the registration assistant when installing CCC for the first time. Re-registration is required, however, when the CCC application is moved. CCC usually handles that automatically as well, although, on Ventura, some additional interaction with System Settings is required. If you have an interaction with the Helper Tool Registration Assistant window, please share your feedback if it could have gone better. Choose "Report a problem" from CCC's Help menu to share your feedback. That isn't necessarily a "problem", but we're aiming for "minimal required interaction" for existing installations of CCC, and we really, really want this to go smoothly once it is rolled out to hundreds of thousands of existing CCC users.
  • New
    Full Disk Access is no longer required separately for CCC's helper tool. CCC's coaching around this procedure has been updated to reflect the new requirement. No changes should be required for current CCC installations.
  • New
    CCC offers new UI in Settings > Advanced to specify the authorization requirements for a variety of CCC activities. For example, you may wish to require an admin user for CCC task changes, but allow non-admin users to start/stop tasks. Now you can configure that with ease in Advanced Settings.
  • Changed
    If a task is configured to restart or shut down the system "after a 60 second delay", that delay will no longer be applied when the screen is locked. In those cases macOS will not present the restart/shutdown dialog at all, so CCC proceeds directly to the request instead. This does not affect the fate of unsaved documents. If an application requires attention before it can quit, that application will cancel the restart/shutdown request even if the screen is locked.
  • Changed
    The "MobileSoftwareUpdate" folder is now hidden by default on the destination. This folder is technically not hidden at the root of the startup disk, but it's not exposed via a firmlink, and it exists exclusively on the Data volume, so it effectively does not appear in the Finder.
  • Changed
    Added wildcard and regular expression support to the Snapshot Comparison Browser search field.
  • Changed
    In the Tasks tab of the CCC Dashboard application, the "Defer…" option is now available for any scheduled task even when that task is not running. This allows the user to proactively defer a task before its scheduled run time rather than having to wait until the task is actually running.
  • Fixed
    b2: Fixed a CloneKitService crasher.
  • New
    b2: Spotlight will now be disabled by default when selecting the option to use a destination volume exclusively for the CCC task in the Backup Volume Setup Assistant. Users can also select a volume in the sidebar and disable (or re-enable) Spotlight via a switch. This change will hopefully address the interference that Spotlight and its mediaanalysisd buddy are causing with regard to unmounting the CCC destination volume.
  • New
    b4: Added an option to the ccc command-line utility to perform snapshot thinning and pruning on a specified volume according to its current Snapshot Retention Policy.
  • New
    b4: CCC Dashboard's "Suspend all tasks" dialog now offers a date picker option.
  • Changed
    b5: Improved the capturing of space savings on the destination when files have been duplicated on the source (e.g. in the Finder).
  • Changed
    b5: The macOS Installer Media Assistant now requests 18GB when "borrowing" space for installer media. This accommodates the larger requirement for macOS Sequoia 15.3.1.
  • Changed
    b5: The "Legacy Bootable Copy Assistant" functionality is now merged into the Backup Volume Setup Assistant.
  • Changed
    b5: When a task is configured to make a legacy bootable copy of the source, the task is no longer automatically converted to a "Standard Backup" configuration after the cloning procedure has completed. When you subsequently run the task again, CCC will erase the destination and repeat the legacy bootable copy procedure.

Nice!

b5: When a task is configured to make a legacy bootable copy of the source, the task is no longer automatically converted to a "Standard Backup" configuration after the cloning procedure has completed. When you subsequently run the task again, CCC will erase the destination and repeat the legacy bootable copy procedure.
Click to expand...
 
Last edited:
  • Like
Reactions: flowrider
CCC 7.1 release. Read carefully before update:

1) https://bombich.com/blog/2025/03/31/celebrate-world-backup-day-with-ccc-7.1 which is mostly about icons!

2) Release notes: https://support.bombich.com/hc/en-us/articles/20686469389719-CCC-7-Release-Notes

3) What's new (lots of changes) shown when running "Check for Updates..." in the current app. Here it is:
  • New
    For Sonoma and Sequoia users, CCC now offers an option to set a custom icon on locally-attached source and destination volumes. Select an image of your own, or get creative with Apple's new Image Playground. Click on CCC's Source or Destination selector to find the new "Set custom icon" options. Apple's Image Playground requires an Apple Silicon Mac that supports Apple Intelligence and macOS Sequoia 15.2 or later.
  • New
    This version of CCC embraces new macOS functionality that allows us to avoid installing the CCC helper tool into Macintosh HD > Library > PrivilegedHelperTools. The helper tool will be "registered" with macOS, but will remain inside of the CCC application bundle. This new practice resolves a long list of complications that have arisen over the years with the legacy LaunchDaemon configuration as Apple has improved macOS platform security.
  • New
    Full Disk Access is no longer required separately for CCC's helper tool. CCC's coaching around this procedure has been updated to reflect the new requirement. No changes are required for current CCC installations.
  • New
    CCC offers new UI in Settings > Advanced to specify the authorization requirements for a variety of CCC activities. For example, you may wish to require an admin user for CCC task changes, but allow non-admin users to start/stop tasks. Now you can configure that with ease in Advanced Settings.
  • Changed
    The Snapshot Comparison Browser search field now supports wildcard and regular expression searches.
  • New
    CCC Dashboard's "Suspend all tasks" dialog now offers a date picker option for those cases where the pre-set intervals are not flexible enough.
  • Changed
    In the Tasks tab of the CCC Dashboard application, the "Defer…" option is now available for any scheduled task even when that task is not running. This allows the user to proactively defer a task before its scheduled run time rather than having to wait until the task is actually running.
  • Changed
    If a task is configured to restart or shut down the system "after a 60 second delay", that delay will no longer be applied when the screen is locked. In those cases macOS will not present the restart/shutdown dialog at all, so CCC proceeds directly to the request instead. This does not affect the fate of unsaved documents. If an application requires attention before it can quit, that application will cancel the restart/shutdown request even if the screen is locked.
  • Fixed
    Fixed a logic issue in the Dashboard that was causing the "Shutdown if previously off" feature to not work.
  • New
    Spotlight will now be disabled on the destination by default when selecting the option to use a destination volume exclusively for the CCC task in the Backup Volume Setup Assistant. Users can also select a volume in the sidebar and disable (or re-enable) Spotlight via a switch. This change will hopefully address the interference that Spotlight and its mediaanalysisd buddy are causing with regard to unmounting CCC destination volumes.
  • New
    Added an option to the ccc command-line utility to perform snapshot thinning and pruning on a specified volume according to its current Snapshot Retention Policy.
  • Changed
    Improved the recapturing of space savings on the destination when files have been duplicated on the source (e.g. in the Finder).
  • Changed
    The macOS Installer Media Assistant now requests 20GB when "borrowing" space for installer media. This accommodates the larger requirement for macOS Sequoia 15.3.1.
  • Changed
    The "Legacy Bootable Copy Assistant" functionality is now merged into the Backup Volume Setup Assistant.
  • Changed
    When a task is configured to make a legacy bootable copy of the source, the task is no longer automatically converted to a "Standard Backup" configuration after the cloning procedure has completed. When you subsequently run the task again, CCC will erase the destination and repeat the legacy bootable copy procedure.
  • Changed
    The "Present an alert dialog for reminders" Dashboard setting is now only applied to reminders, not to "Prompt before proceeding" task prompts.
  • Changed
    The "MobileSoftwareUpdate" folder is now hidden by default on the destination. This folder is technically not hidden at the root of the startup disk, but it's not exposed via a firmlink, and it exists exclusively on the Data volume, so it effectively does not appear in the Finder.
  • Changed
    Build 8132 addresses a regression around the handling of large sparse files when determining whether there is enough free space for a file. It also addresses an edge case in which CCC would request that the user grant full disk access to CCC despite that it was already granted.
 
  • Like
Reactions: buggz, MacBH928 and Weaselboy
I am finally back from being on travel, just a few days from it arriving.

I am waiting on Apple shipping their fastest Ultra chip with 32-core CPU, 80‑core GPU option also. , 32-core Neural Engine Mac to arrive to replace it May 20 -22. Yes I hope it becomes annual but really who cares seriously, not like it matters. :cool:
 
Last edited:
basslik said:
Is it possible to clone a 5,1 with OCLP?
Click to expand...
Assuming you want a bootable clone - not as single step. After cloning (there are caveats as to whether/when this is possible), you would need to apply OCLP to the external bootable.
Note: I have not attempted this - my reply is based on what I know about how CCC and OCLP work. So try it.
 
  • Like
Reactions: basslik
My Experience with CCC7.1.1 and MacOS26 (Tahoe) Developer Release:

Tried to make a start-up clone from my Tahoe Boot SSD to a Back-up SSD (Samsung 970 Pro on a PCI card). Went through the steps and appeared to make a successful clone. However, try as I might, it would not boot my 14,8 Silicon Mac Pro. I blessed it with my user password, I reduced the disk's security at startup, and no dice. I tried making another clone, and same outcome.

I have four boot SSDs on my Mac. Two for Sonoma and two for Tahoe. I booted to Sequoia from my Sequoia boot disk, and lo and behold, it booted fine. The Sequoia boot disk was created with CCC in OS Sequoia.

Since the Sequoia Boot disk booted fine, I booted back into Sequoia. I opened CCC and cloned the Tahoe boot SSD (the OEM Apple SSD) to my backup Samsung SSD. I then rebooted to the Tahoe Back-up SSD, and voila, it worked. So, CCC made a bootable Tahoe Backup when booted in Sequoia, but not when booted in Tahoe❓

Took me a couple hours 🤔

Lou
 
Last edited:
flowrider said:
My Experience with CCC7.1.1 and MacOS26 (Tahoe) Developer Release:

Tried to make a start-up clone from my Tahoe Boot SSD to a Back-up SSD (Samsung 970 Pro on a PCI card). Went through the steps and appeared to make a successful clone. However, try as I might, it would not boot my 14,8 Silicon Mac Pro. I blessed it with my user password, I reduced the disk's security at startup, and no dice. I tried making another clone, and same outcome.

I have four boot SSDs on my Mac. Two for Sonoma and two for Tahoe. I booted to Sequoia from my Sequoia boot disk, and lo and behold, it booted fine. The Sequoia boot disk was created with CCC in OS Sequoia.

Since the Sequoia Boot disk booted fine, I booted back into Sequoia. I opened CCC and cloned the Tahoe boot SSD (the OEM Apple SSD) to my backup Samsung SSD. I then rebooted to the Tahoe Back-up SSD, and voila, it worked. So, CCC made a bootable Tahoe Backup when booted in Sequoia, but not when booted in Tahoe❓

Took me a couple hours 🤔

Lou
Click to expand...
Why whisper at the end?

Anyway, I would wait for a new OS till I made sure all my 3rd party stuff would run on it.
(how?)
;JOOP!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back