One long-standing and useful feature in OS X is its ability to boot from practically any mountable partition, including external drives. This allows for quick ways to test an installation, isolate different uses of your Mac to separate boot drives, troubleshoot aspects of your Mac’s hardware and internal storage, and create bootable backups of your Mac’s hard drive. While useful, there are times when your Mac will not boot to such partitions, even if they are perfectly healthy. If so, then here is what to do about it.
1. OS X version mismatch
First check if the version of OS X on the external drive supports your current Mac. You might have created the secondary boot drive using a prior Mac running older OS X software, and if so, then this may not boot properly (if at all) when used on newer Mac hardware. For full compatibility, be sure you have the OS X version that shipped with your Mac (or later) installed on the drive. To do this, you should be able to perform a reinstall of OS X onto the drive using the OS X Recovery utility without wiping it. As with a standard reinstallation, this should only replace and update the system software on the drive, and not affect any of your data on it.
When you boot OS X, you should be able to load the boot menu by holding the Option key when you hear the boot chimes; however, if you have a firmware password enabled then you may not see this menu and instead may see a password prompt. You will otherwise not be able to instruct your system to load the alternative boot drive at startup. To overcome this, you will need to either supply your firmware password or disable it. On systems made before 2010, a hardware change such as removing RAM modules was enough to reset the firmware password, but in newer systems, you will need to contact Apple Support and have this done in person at an Apple Store.
3. Wireless or third-party keyboard
If you use a wireless keyboard, then any keys you press will not be recognized if they are held down before the system detects the keyboard. This is done when the boot chimes sound, so be sure to press and hold the Option key or other startup argument key combinations immediately when you hear the boot chimes, and not before. This requirement does not apply to USB keyboards, so you might also consider forgoing your wireless keyboard for a USB one when attempting these alternative boot options.
In some cases, third-party wireless and USB keyboards may not be recognized by the system at boot, which will likewise prevent any key combinations from being recognized at startup. In these cases, try using another keyboard (specifically the one Apple provided with your system).
4. Conflicting peripheral devices
While less of a problem, you may have an issue with other external devices that your Mac is connected to, which may prevent your hard drive from being recognized. This is especially true if you are using a USB hub or extension cable. To overcome these issues, try disconnecting all devices from your Mac and attach your drive directly to your system. Also ensure you use a provided power source for the drive, if available, as this will ensure it is receiving ample power and not relying solely on the USB connection for power.
5. Manually select in the Startup Disk system preferences
An alternative to using startup options for loading a secondary boot partition is to select your desired drive in the Startup Disk system preferences. This approach can be done even if you have a firmware password enabled on your Mac, and is the way to permanently change the boot drive on your system so you will not have to use special keys at startup.
6. Check the boot drive’s partition map and formatting
A final issue could simply be that your desired boot drive has become damaged. For OS X to load, the drive must have a healthy GUID partition scheme, and be formatted to HFS+ (aka, “Mac OS X Extended). To check this, open Disk Utility and select your drive device in the sidebar. Then press Command-i to get information on the drive, where you should see in formation about its partitioning. You can do the same for the boot volume listed under the drive, where you should see its format listed.
If you are using FileVault full-disk encryption on the drive, then it will appear as a Logical Volume Group and not show you the partitioning scheme. This should mean that the drive is already using GUID partitioning, as it is a requirement for CoreStorage (the technology used for creating the logical volume group), but you can also check by opening the Terminal and running the following command:
diskutil list
The output of this command will list all physical and logical drives available to your system, where you will see those that are labeled as Apple_CoreStorage partitions will also have GUID_partition_scheme listed.

The drives listed here are all partitioned with the GUID partition scheme. You can also see volumes under them (such as Macintosh HD) are listed as Apple_HFS, meaning they are properly formatted.
7. Wipe and reinstall to that partition
Lastly, if you are not relying on any of the drive’s data and only wish to have a secondary boot drive for troubleshooting purposes, then you can use Disk Utility to wipe the partition and then reinstall OS X to it from scratch. Doing so should ensure the drive’s logical environment (software and storage setup) are ready for booting, so if the system still refuses to boot it, then this suggests a hardware incompatibility that is preventing the drive from being available at bootup.
I’ve found that the recognition of things like CMD-S during boot via a wireless keyboard is not very reliable. Older systems are less likely to recognize the startup key. E.G., my 2013 iMac will recognize CMD-S on a “cold boot” (i.e., starting with power off) but never recognized it on a reboot (it’s running 10.8.5, though it seems logical that boot-key recognition is via firmware code). My 2012 iMac is completely flakey at boot-key recognition. I can mostly get it to recognize one by pressing the wireless keyboard’s “on” button just before pressing the iMac’s power button (again, there’s no recognition of CMD-S on a reboot).
There are some external hard drives which will not boot a Mac no matter what backup program is used. The chip set in the drive does not support it.
I have a similar problem.
created a bootable USB stick with Install OS X El Capitan using Terminal; finished without any errors.
Was able to boot from it and do a full clean install. However after using migration assistant and finding many apps not working and basically ending up with the same clutter that led me to the clean install in the first place I decided to do another clean install of El Capitan and no matter what it would not recognize the USB stick at boot up .
A restore from time machine sent the MBP into an endless boot loop and I ended up installing from the app store.
So I got El Capitan working, with the clutter from the pre-install, created another bootable USB stick with Terminal and tried again and nothing. Either wants to boot from the HD or the recovery partition.
Disk maker shows the drive as bootable and finder recognizes it, but no luck booting from it.
Ralf