

You can update now or select another startup disk. Booting from an external volume works fine in general, but if your external disk is formatted using Apple's legacy HFS+, "Mac OS Extended" format, enabling FileVault on that volume will render it non-bootable, producing an error message like this on startup:Ī software update is required to use this startup disk. Our testing has confirmed that Macs with Apple's T2 controller chip cannot boot from an encrypted, "Mac OS Extended"-formatted, external volume. T2-based Macs can't boot from encrypted HFS+ volumes "Full Security" is the default setting, and that setting is compatible with bootable backups.

Please do not, however, change the Secure Boot setting for the purpose of booting from a backup. Apple describes the procedure in this Kbase article:
Apple carbon copy cloner pro#
a 2018 MacBook Pro or an iMac Pro) from your CCC bootable backup, be sure to configure your Mac to allow booting from an external hard drive. If you are attempting to boot a Mac with an Apple T2 controller chip (e.g. T2-based Macs disable booting from an external disk by default I found the following in the Knowledge Base for CCC.

This use case is served well with advent of most dynamic data/content/files on my OS being Internet-served-and-synced (git repos, IMAP server, Dropbox/GDrive, etc) across my multiple MacBooks.
Apple carbon copy cloner how to#
How to Disable System Integrity Protection on a Mac (and Why You Shouldn’t).

More detailsĪ source told me CCC is "T2 chip incompatible" (or some such) and advised that Migration Assistant is the only (or at least only supported?) way to go. Nonetheless, I'm open to any and all pitches for MA. Every time I'm tried an Apple-native solution (namely TimeMachine) to thoroughly and comprehensively capture all data/settings/content in a filesystem it's always failed me.I could not get MA to see my 40-gigabit Thunderbolt link between MacBooks (it kept wanting to talk over WiFi).I have decades of trust with rsync (which is what CCC employs) across many OSes (Unix, Linux, *BSD, macOS, Windows). I do not yet trust MA, as it's completely new to me.Comparison with Apple/macOS Migration Assistant (MA) I do not yet see why a copy/clone to a FileVault-ed MacBook that's running Target Disk Mode (and for which I have the FileVault/disk/login password) will not work. Assuming no OS incompatibilities between hardware, will a Carbon Copy Cloner (CCC) file/ rsync-based copying/cloning from a MacBook source (regardless of T2) to a T2 MacBook work - and why or why not? I want to copy my entire OS/volume/disk (which is FileVault-ed) from on MacBook to another, whose volumes(s) are also FileVaulted.
