Q: First Boot-Up Into El Capitan "Got Stuck"
I upgraded my 2010 MacBook Pro from Yosemite (10.10.5) to El Capitan, today, and had one, EXTREMELY, notable issue.
The installation seemed to go fine. My computer, then, rebooted to launch into El Capitan. I saw the familiar grey screen with the Apple logo and the progress bar. The progress bar, quickly, went almost to the end (around 90%) and, then, it just got stuck there. I let it sit for a good half-hour and it wouldn't advance any further. Not sure what to do, I called Apple. First, they had me try restarting. No go. The boot-up still got stuck at the same point. Next, they had me boot to the recovery partition. Upon loading the recovery partition, I did some poking around. I launched Disk Utility and saw that it was the new version. Opened Startup Disk and that informed me that my drive was running 10.11, so I knew the OS was installed (it just wasn't completing the boot). The Apple guy I spoke to suggested that I, next, try reinstalling El Capitan from the recovery partition. Knowing that this would take several hours, I was hoping for a different way. I did some poking around online for solutions to "stuck" start-ups. While in the recovery drive, I ran Disk Utility. No problems. Then, I shut down my computer. I restarted while doing an SMC reset. It, then, booted up fine. I got the iCloud set-up window, the license agreement, and all of the other windows that one is supposed to see upon the initial boot-up for a new OS. Then, my desktop showed up, so I knew I was good to go.
Everything else seems to be going smoothly. I haven't tried everything, but all of my "mission critical" apps seem to be working fine.
Just wondered if anyone else had a similar problem? Any ideas on what the hang-up could have, possibly, been?
MacBook Pro (15-inch Mid 2010), OS X El Capitan (10.11), null
Posted on Oct 3, 2015 4:13 PM
Poking around the forum, I noticed many other folks having problems booting up after installing El Capitan. I'm thinking that THIS THREAD describes the issue, best. It seems that the problem is, most likely, kext (kernal extension) related. One poster in the, aforementioned, thread posted this solution from the OWC knowledge base:
If your Mac is randomly getting stuck during the boot process in Yosemite, it may be from unsigned extensions. This is most common with the Mac mini models.
First you will need to get it to boot before we can proceed.
Getting the Mac to boot:
1) Start the machine while holding down the Option-Apple-P-R keys
2) Wait until you hear the 3rd startup chime, then release the keys.
3) If that doesn't work try an SMC reset here: https://support.apple.com/en-us/HT201295
Now for the fix after you get the machine to boot:
1) Open Terminal in /Applications/Utilities
2) Enter "system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt" without the quotes and hit return(this will take a while to run).
3) There should now be a kextList.txt file on your desktop, open it and press both the "Apple(Command)" and "F" keys to bring up the find.
4) In the find field insert "Obtained from: Not Signed" Copy the destination to the .kext file to a list for use later. (Click next to cycle through all of them.) Example: /System/Library/Extensions/JMicronATA.kext
5) Browse your drive to /System/Library/Extensions and remove any of the unsigned kext files.
6) Reboot and you should be all set.
I mentioned in my first post that I did an SMC reset. I guess I stumbled onto the first part of the equation. I ran the Terminal command and found more than a dozen kexts on my system that were "not signed". Based on the modification dates, the majority of this unsigned kexts predated my computer (suggesting that they were carried over when I upgraded from my previous computer). I did my homework and determined that most of these kexts had no ties to any applications that I had, currently, installed and using. So I concluded that they were safe to delete. I moved them all to a different folder (just in case) and deleted them from the System Extensions folder. I restarted my computer and it booted up without any problems.
Looks like I'm in the clear, now. Hopefully, this is helpful to someone else.
Posted on Oct 5, 2015 6:45 AM