We're happy to help you troubleshoot your bootability problems. Before you ask for help, please try the troubleshooting steps below. If you're having trouble with the steps or have run out of options, please let us know how far you got, or how far your Mac gets into the boot process.
Troubleshooting firmware discovery problems
When you boot your Mac while holding down the Option key, your Mac's firmware will display a list of available startup devices. Using only device drivers that are stored on your Mac's firmware chip, the firmware will scan all of your SATA, PCI, USB, Firewire, and Thunderbolt busses for hard drive devices, then read those hard drive volume headers to determine if a macOS system is available on each volume. Ordinarily, a CCC bootable backup volume will appear in this list, but occasionally your Mac's firmware may have difficulty discovering the hardware that hosts your backup.
If CCC's Task Plan didn't report any configuration concerns for your backup volume and you are having trouble booting from it, try the following troubleshooting steps (in order).
Rule out generally incompatible configurations and filesystem anomalies
If you are using an external hard drive enclosure, see whether your enclosure is listed at the bottom of this page as an enclosure that we've seen problems with in the past. Also, for good measure, use Disk Utility's "First Aid" utility to verify and repair any filesystem problems that may be present on the destination volume.
Troubleshoot discoverability issues in the Mac's Startup Manager
- Reboot your Mac while holding down the Option key.
- Wait about 30 seconds to see if the backup volume appears. If your backup volume appears at this step and the boot process proceeds past the Apple logo, skip to the next section below.
- Detach, then reattach the backup volume's Firewire, USB or Thunderbolt cable from/to your Mac and wait up to another 30 seconds. If your backup volume appears, select it and proceed with the startup process.
- If the backup volume still does not appear as an option, shut down your Mac completely. Then start it up holding down the Option key, waiting another 30 seconds for the volume to appear.
- Repeat the steps above, but using another interface (e.g. USB if you tried Firewire, Firewire if you already tried USB) and see if the volume appears.
- If the hard drive enclosure is bus powered, try plugging in its DC power supply before starting up your Mac. Bus powered enclosures often take a bit longer to spin up or simply don't make themselves available that early in the boot process.
Additional USB device troubleshooting
Macs' support for booting from USB volumes has always been second class to Apple-invented interfaces such as Firewire and Thunderbolt. We strongly recommend using Firewire or Thunderbolt for your bootable backup; those interfaces are consistently more reliable when it comes to bootability. If you have a USB-only device in hand, though, here are a couple additional steps you can perform to try to get your Mac to "see" it early in the startup process.
- Reboot your Mac while holding down the Option key.
- If your Mac has multiple USB ports, try attaching your destination disk to each port (and be sure to use the ports on your Mac directly — not a hub, keyboard, or display)
- If you are using a USB 3.0 enclosure, try using a USB 2.0 cable (yes, it will work!). USB 3.0 devices are backwards compatible to USB 2.0, but they don't always play well with the older USB device drivers that are embedded within your Mac's firmware. Using a USB 2.0 cable elicits different behavior from the enclosure that often works around compatibility problems that are only exposed when using the Mac's firmware USB drivers. Here are some pictures that show what the ends of USB 2.0 and USB 3.0 cables look like:
Reset the Mac's Parameter RAM
Lastly, try resetting your Mac's parameter RAM. PRAM maintains settings related to starting up your Mac, and it's possible that invalid settings are interfering with your Mac's discovery of the external enclosure. To reset your PRAM:
- Hold down Command+Option+P+R on startup
- Hold down those keys until you hear the second startup chime.
- Release all but the Option key after you hear the second startup chime.
Definitively rule out an incompatible enclosure
If the volume still won't boot, it may be impossible for your firmware to detect your enclosure (despite that macOS, once booted and having access to far more device drivers, can see the enclosure just fine). The Golden Litmus Test for bootability would be to install macOS directly onto the volume. If that fails to make the disk bootable, then it definitely isn't going to happen. Please report these enclosures to us so we can assemble a list of troublesome enclosures.
There are several visual hints that can indicate how far your backup volume is getting in the startup process:
- Apple logo: The "booter" file was found and executed.
- Spinning progress indicator: The OS "kernel" was executed and now has control over the startup process. The kernel will load kernel extension caches, mount the startup disk, then execute "launchd" which kicks off all of the other system processes.
- Blue screen: The WindowServer has loaded, so the system is ready to start loading regular applications or the loginwindow.
- Loginwindow or your Desktop: The system has finished loading, and is ready for user interaction
If your backup volume showed up in the Option key startup disk selection screen, but doesn't display the Apple logo when you choose to start from it, then your Mac is having trouble finding the "booter" file on this volume. This can occur due to hard drive enclosure interference, due to filesystem corruption on the backup volume, or due to the volume being improperly "blessed" (blessing a volume stores certain information about the startup files in the volume's header, and your Mac uses that information to start the boot process).
- Repartition the backup disk in Disk Utility, then reclone your startup disk to the destination.
- Try booting from the backup volume again.
If you see the universal "No access" symbol after selecting your startup disk
This indicates that the kernel cannot load the kernel extension cache, or that it cannot mount the startup disk. This could be due to trying to run an incompatible operating system on your Mac, or due to an extension conflict with the enclosure you are trying to boot from.
We see this quite frequently when trying to boot from a USB 3.0 enclosure, especially on Macs that do not have native support for USB 3.0. We also see this more frequently on Yosemite when a critical kernel extension's code signature is invalid. This can happen, for example, when using something like TRIM Enabler to modify macOS Storage drivers.
- If you are booting a different Mac than what the backup volume was cloned from, try installing macOS directly onto the cloned volume while booted from the Apple Recovery volume.
- If you're booting the same Mac from which you created the backup, try booting into Safe Boot mode (hold down the Shift key as you start your Mac, after selecting the backup volume as the startup disk).
- If you used a third-party utility to modify macOS software (e.g. TRIM Enabler), undo that modification, then run the backup task again.
If your Mac never progresses past the spinning progress indicator (below the Apple logo) or stalls at the blue screen while booting from the backup volume, there is probably a problem with some of the system files that are called early in the startup process. The system log on the backup volume can be very useful in troubleshooting these problems. To view the system log:
- Boot your Mac from its usual startup disk while holding down the Shift key. This will start your Mac in Safe Boot mode, and will cause macOS to rebuild the kernel cache on the startup disk.
- Run your backup task again, then try again to boot from the backup volume. If the same problem occurs, reboot from your regular startup disk and proceed to the next step.
- Choose "Go to folder" from the Finder's Go menu.
- Type "/Volumes/Backup volume name/var/log" (no quotes, and substitute the actual name of the volume) and click the Go button.
- Double-click on the system.log item in this folder.
Look for any error messages, indications of crashes, etc., or simply attach the system.log file to a support request on the Bombich Software Help Desk.
"unapproved caller. security agent may only be invoked by apple software" message appears on startup
This message generally appears when the volume you are trying to boot from is full or nearly full. You can remove items from the _CCC SafetyNet folder (or the entire folder itself), then empty the Trash to free up some space before trying to boot from that volume again. macOS should be given at least 2GB, preferably 5-10GB of free space to accommodate the creation of cache and virtual memory files on startup.
- Some Western Digital enclosures cannot boot Macs
- Hands Off! and possibly Little Snitch may prevent a cloned volume from booting
- Some Macs have trouble booting from USB 3.0 enclosures
- Some MacBook Pros can boot from a disk in an enclosure, but not when it is installed internally
- Some MacBook Pros can boot from a disk in an enclosure, but not when it is installed internally (asks to be reinitialized)
- Cannot boot from a hard drive installed in some optical bay replacement kits
- Reports indicate that, contrary to its published documentation, the NewerTech Voyager Dock enclosure is not bootable via Firewire.
- We have received a report that the Nexstar 6G USB 3.0 hard drive enclosure is not bootable due to a discoverability issue. The Nexstar TX from Vantec was bootable (using the same internal hard drive).
- We have received a report that the CineRAID Home CR-H212 USB 3.0 Bus Powered Dual Drive RAID/JBOD Portable Enclosure may provide inconsistent bootability results. In at least one case, only one of the hard drives in the enclosure was discoverable by Mac firmware, and it appeared to be position-dependent within the enclosure.
- We have received a report that the Orico 3588US3 USB3 enclosure is not bootable due to a discoverability issue.