Reboot fail after installing El Capitan help!!
I Just jjust installed El Capitan on the latest Mac book pro rentina. I have tried to restart and it does not reboot. Any suggestions on the fix?
MacBook Air (13-inch Mid 2011)
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I Just jjust installed El Capitan on the latest Mac book pro rentina. I have tried to restart and it does not reboot. Any suggestions on the fix?
MacBook Air (13-inch Mid 2011)
I have the same problem and have restored twice with the same problem. I did run across this solution, but am to tired to try it right now. I do not plan to shutdown again until I can get it fixed on my other mac computer. Having the same problem on both. Keep you posted.
https://forums.developer.apple.com/thread/21331
Either way, this is best fixed from Recovery Mode, but you shouldn't have to reinstall again to boot normally because moving the kexts in Recovery Mode should allow the boot process to continue as normal. Let me know how it goes.
cd "/Volumes/Macintosh HD/Library/Extensions/" ; mkdir Unsupported ; mv hp* Unsupported ; mv B* Unsupported ; cd "/Volumes/Macintosh HD/System/Library/Extensions/" ; mkdir Unsupported ; mv Elt* Unsupported ; mv ssud* Unsupported ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Rox* ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Check* ; rm -Rf /Volumes/Macintosh\ HD/Library/Filesystems/*fuse* ; rm -Rf /Volumes/Macintosh\ HD/var/folders/*
hello,
i encounter same issue but before searching in Apple community forum I tried to solve it with an Apple care advisor ... Too bad for me.
Following advisors instruction, my fusion drive is now in a weird state and osx installer is not able anymore to write any data on disk and suggest me to contact.... Apple care...
I'm really fed up with Apple and their less and less quality product.
Thanks a lot Lucaspeed!
I had the same issue and your suggestion was perfect for me. The Kext was the Eltima's one.
This time I was lucky but I was wondering if there's a way to read in some log file the output of the single user mode (CMD+S) login screen.
In my case it is so fast to disappear that I was only able to read "Eltima" (and it was enough for me). If it was something different I'm not sure would have been able to figure it out...
Thanks,
Gianpi
I just did the kext fix to my brother's late 2012 MBPRD. The command S did not help but his simptom was slightly different. It would hang in the login screen, sometimes as far as allowing password entry. Some signed karperski kexts were the culprit. In his case, safe boot worked and I was able to work from there. Working from restore mode gave no accurate results.
Hi Markzol... On October 5th I posted: (please be not offended, but read before posting:-)
Hi everyone!
Think I've got the final solution, found a nifty trick at OWC's website.
The previous poster is almost right, but it is a tailored solution that will not work for everyone, because everyone has different Kext's by different developers and vendors.
It seems to be all about Kexts and they are in TWO locations, /Library/Extensions AND /System/Library/Extensions.
If you cannot boot, as was the case with me, start a recovery, either via internet or a thumb drive.
It will not destroy everything so no clean install necessary.
After startup do the following (I did everything with Finder):
From OWC and edited by me:
1) Open Terminal in /Applications/Utilities
2) Enter "system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt" without the quotes and hit return (this will take a short while to run).
3) There should now be a kextList.txt file on your desktop, open it and press both the "Command" and "F" keys to bring up the find.
4) In the find field insert "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 create a folder by the name Unsupported, move any of the unsigned kext files to the folder Unsupported. Delete the Kexts from their original location.
6) Browse in /Library/Extensions and create again a folder named Unsupported. Look if there are more unsupported Kext's and move them to the folder Unsupported. Delete the Kexts from their original location.
7) Beware that there may be Kext's that are "not signed" that you want to keep because you may need them for programs known and trusted by you, so do not move them to the unsupported folder(s). If you did, no worries, you can always put them back later if there are troubles.
8) Reboot and you should be all set.
This did the trick for me, hopefully for everyone...?
Yes you right you have explained before but you didn't make any resume to all the steps in single sheet, so I believe this will prevent users to read all steps and wasting time ... so this should be marked as "THIS HELPED ME"
Best
Mark
Anyway folks...
I hope that this stupid startup-thing is solved by now.
Most people affected seems to have the Etima (e.g. Syncmate, now out of date) syncing-software for Windows and RIM(Blackberry) devices that is causing this startup trouble.
I believe that I, and many other users with me, did never do a clean install, because it seemed totally unnecessary, why, for what reason...?
My Mac was and is still working great after updates from Lion to ElCap, and I never saw the reason for clean installs, to much work, and, I'm very lazy:-)
But old things can cause troubles. So, expect weird things to happen when updating to a new OS, old kexts, old software, old whatever things can and will cause headaches...
Thanks for this board and many thanks to the guru's (OWC and again a guy called Max108 on the developers forum) that put us in the right direction.
To a member, Fred from Doornspijk: I read your postings, but they seem to be deleted or modified. Hope you are OK by now, otherwise let us know? WeI'll be glad to help if we can!
Cheers, Gerard...!
Thank you. It worked on my iMac, also. I deleted the Eltima extension after booting from an external system disk. I used the Finder instead of the Terminal. The reboot worked fine ever since. Two thumbs up!
Thanks Gerard from NL for the 'invitation'. If I read the postings and see all the expertise I feel very stupid. The - obviously - most simple Apple things I don't know. I have learned that can you start the MacBook in safe mode by pressing the shift key and holding it till the computer is working. So I can wait till Apple comes with an update for El Capitan of try - when I am back at home - to set a back up from a month ago on my computer. But I can also give it a try.
So I have the computer the safe mode. I have found Terminal, but when I click on terminal to open it, it does not open.
In your answer to Markzol you write: "start a recovery, either via internet or a thumb drive". How do I start a recovery via internet?
Hi GSfromNL.
I have a problem.
If I run the command system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt using an external operating system installed in an external hard drive, generates me the list of extensions of THE external hard drive, not the internal Volume. How can I get the correct list?
Thank you very much!
As far as I know: The system_profiler command is the system you are working on, so it gives you a list from your system started with the external startup disk.
I'm not a Terminal expert but trying the following commands in Terminal should work to list the kexts on your internal drive.
Start Terminal and type: cd /Volumes/HDname (--->Replace HDname with the name of your harddisk. If there is a space in the name put in a backslash and space like HDname\ XX)
Then type or copy/paste:
sudo ls -1 /Library/Extensions/ ; sudo find /System/Library/Extensions -ctime +1d -depth 2 ; sudo find /Library/Extensions -ctime +1d -depth 2
This I believe, will give you all the kexts for you to sort out…
The easier way is to boot from the internal HD, more reliable…
Dear GSfromNL. After starting with command + R I get the "OS X-helprograms" with four choices: 1. set back from Time Machine 2. Install OS X again 3. Look for help information online 4. Disk help program.
A couple of days ago I chose for option 2. El Capitan is downloaded again, installed again and then my computer is switched off automatically. Is option 2 what you mean with 'Recovery'?
Thanks Fred
You have the answer. the file in your list... "System/Library/Extensions/EltimaAsync.kext/Contents" is one that existed in my list as well. After deleting it, everything worked fine. The file was created originally from a sync program I had acquired years ago for a PDA devise i was using. For me it serves no purpose any longer and it's deletion allows El Capitan to boot flawlessly.
Good luck and thank all for their efforts. Without the postings I never would have discovered the flaw.
Thanks GSfromNL. As others said your suggestion of removing unsigned kext files worked for me. There was one difference for me however that I thought I would share. It did not appear to work for me at first. I moved all the "Not Signed" kext files to the unsupported directory as suggested, rebooted from terminal, and then tried to reboot from menu and it still froze. So I moved the kext files back and did a reboot from terminal. When I did that reboot I got a pop-up message for each of the kext files I moved back (5 for me) saying they were not installed properly and would have to be reinstalled. After that it rebooted. And now I can reboot from my Apple->Restart menu again. The one thing I noticed still is that it seems to take longer on the black screen before you hear the distinctive reboot sound. But it is rebooting. 5 times in a row before posting this. I did another profile and the 5 unsigned kext files are showing up again now but it is still rebooting. I google the kext files that are not signed and based on my finding I went ahead and just deleted all 5 of them.
Thanks again!
I don't know why but this has fixed my problem.
It restarted me at the intro section of El Capitan... I had to re-enter my Icloud username/password etc... and resign the agreements.
But seems to be working.
GSfromNL wrote:
Hi everyone!
Think I've got the final solution, found a nifty trick at OWC's website.
The previous poster is almost right, but it is a tailored solution that will not work for everyone, because everyone has different Kext's by different developers and vendors.
It seems to be all about Kexts and they are in TWO locations, /Library/Extensions AND /System/Library/Extensions.
Thank you GSfromNL!
Before trying this the 10.11.1 update on my MBP 2014 15" just hung and would never complete even after reboots. I followed the process you described above but only got rid of the items that were 2009 or older. I attempted the re-install and it went flawless. I used the same process on my iMac mid 2007 24" and it installed the 10.11.1 update with no problem.
Thanks again!
Reboot fail after installing El Capitan help!!