Reboot fail after installing El Capitan help!!

To LeeSniper and PJ'sPal...

All your suggestions are fine...

But, if not starting up is - ONLY - KEXT related, a clean instal is like shooting with a canon at a mosquito.

Just get rid of old KEXT stuff, remove them from the TWO libraries, System and User.

If anyone, like me, (since Lion...!) never did a clean install, you will be surprised how many old and now obsolete things are residing in these libraries.

As I wrote this in previous posts:

There are TWO ways to solve the Kext problems. One way is to do it with Terminal, the other way is to use Finder, but then you have to be able to start up by means of another bootable disk.

Method 1, by use of Terminal:

From the recovery partition you can get into Terminal, then try the following commands in Terminal to list the kexts on your internal drive, (if asked for your password give it):

Important is :

cd /Volumes/MacHD Replace MacHD with the exact name of your harddisk.

NOTE: If there is a space in the name of your HD (for instance Mac HD) put in a BACKSLASH before the space like: Mac\ HD

You should see that you are now on your internal disk... If not: You made a typing error, and you will remain on the recovery partition: Try again!

Then, but be VERY careful with these commands and use correct Uppercase and lowercase...! (you can copy and paste)

sudo ls -1 /Library/Extensions/ ; sudo find /System/Library/Extensions -ctime +1d -depth 2 ; sudo find /Library/Extensions -ctime +1d -depth 2

This will give you all the kexts to sort out, if you found them:

Make different locations for the not supported kexts with these commands:

sudo md ~/System/Library/KextNotSupported

sudo md ~/Library/KextNotSupported

Move all suspects to the different location with these commands:

sudo cp ~/System/Library/Extensions/EXACT KEXT NAMES /System/Library/KextNotSupported

sudo cp ~/Library/Extensions/EXACT KEXT NAMES /Library/KextNotSupported

Delete them in original location:

sudo rm ~/System/Library/Extensions/EXACT KEXT NAMES

sudo rm ~/Library/Extensions/EXACT KEXT NAMES

Repeat for every suspected kext.

Note: replace EXACT KEXT NAMES with, for instance, EtimaAsync.kext and, again, use the EXACT Uppercase and lowercase...

Method 2, by using the Finder:

Boot from another disk or thumb drive.

Go with Finder to your internal disk,

go to Library -> Extensions and look for old suspected kexts. If you found them, make a new folder and move them there: Important: Delete them from the Extensions folder.

Repeat this with System -> Library -> Extensions

Hope this helps!

Dear GSfromNL:

I have a MAC PRO with PCIE expansion slots and a variety of cards that I can install/uninstall for expansion.

I did a clean install with Yosemite about a year or so ago.

I did not do a clean install of El Capitan 10.11.1 and had no problems with it until upgrading to 10.11.2.

The system security improvements did not flag something it could not work with.

Something I added, after the clean install of Yosemite, inserted a KEXT I believe is causing the problem.

My guess is an antivirus application but I have not yet really determined the issue because it could be others.

The problem is that we may not know exactly what KEXT is causing the problem.

One would assume Apple did not see this as an issue either until now or these users would not experience the problem.

We have to guess one by one and then try and reboot - a process that may take hours to complete.

Conflict Catcher used to do this for us in the old days.

My point is that the hours spent trying to fix things now and guessing at the problem, would have been better spent doing a clean install from a blank drive and migrating data/applications/users automatically overnight.

From my SSD with El Capitan that still does not boot.

Here are my library extensions:

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/ACS6x.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/ArcMSR.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/ATTOCelerityFC8.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/ATTOExpressSASHBA2.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/ATTOExpressSASRAID2.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/BJUSBLoad.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/CalDigitHDProDrv.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/CIJUSBLoad.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/HighPointIOP.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/HighPointRR.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/hp_io_enabler_compound.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/LittleSnitch.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/PromiseSTEX.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/SoftRAID.kext/

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/SophosNetworkInterceptor.kext /

file:///Volumes/ALG-MacPro2-APD/Library/Extensions/SophosOnAccessInterceptor.kex t/

The CallDigit, hp_io_enabler; and ATTOxxxx for my PCIE card are dated August 2013.

The BJUSBLoad, HighPointxxx, PromiseSTEX; and ACS6x are dated in 2014.

LittleSnitch; Sophos; and SoftRAID are dated in 2015.

If I were to guess, the 2013 and 2014 KEXTs are possibly a problem.

However, I would not rule out SoftRAID or Sophos with 2015 dates.

If I really wanted to know which was the culprit, I would go through 7 or 9 reboots of my system and may still not find out which is the culprit.

All the SYSTEM/LIBRARY extensions (too many to show) are all dated in 2015.

Of course the date may not be accurate.

Assuming we can drop all the Apple ones, there are significantly more KEXTs here.

To determine exactly which one is the issue, may take months.

I could do it, but I really don't have the time any more.

What if there is some other problem and it is not a KEXT?

Maybe Apple's own SSD drive needed some driver for support - the reason why all these MacBooks and my Mac Pro will not boot.

Regardless, I should have followed my own rule of doing clean installs of OS X.

Because this was just a version update, I thought I could get away with the Application Store update process.

I was wrong.

To finally boot up, I ended up doing a clean install (without computer extensions) on a magnetic hard drive to boot into 10.11.2.

Hi GSfromNL:

Thank you the further information.

I previously zapped the PRAM.

I also tried the SMC reset and no luck.

I previously tried the safe boot with El Capitan on my SSD.

It fails and stalls at the same spot with safe boot - getting past the hardware chimes and the software progress bar.

It never gets to the LOGIN screen.

The Mac Pro is booting EL Capitan 10.11.2 now from a different drive with the same hardware, so it is not likely the NVRAM and/or SMC controller in hardware that is causing problems.

I have not analyzed the KEXTs if they are signed and can pass the SIP or not.

It would be interesting if I could turn off SIP on the SSD but I can't get to the terminal command when booting from the SSD.
If there were keystrokes to immediately could go into terminal mode, memories of the old golden days of computers, that would be useful but it does not.

If it booted up to LOGIN with SIP off, that would tell me that SIP is offended by some software.

I have been in contact with Apple customer service and I sent them my system diagnosis files from boot up from my SSD and my bootable hard drive.

They wanted to see if they could improve the next 10.11.3 release.

I hope that I have been able to help them with it.

When I get through the holidays and my end of year due dates, I will spend some time to try and figure out what KEXT may be the problem.

This is just not the time to be debugging software.

Just for the notice, I tried every single way mentioned here and in other places / forums online, even after deleting the kexts, after a few days the OS was freezing, shuts down after putting it up from sleep mode. I had kept it on (no sleep mode) for days so that I get my work done and it still froze or I would find it shut down at some point.

I really advise in this case to make a clean install after backing up. And do not update to the 10.11.2 version, because that is when the problems occurred..

Hi! and sincere thanks to all of you who have helped with this problem. The last post was a month ago today, so I hope you'all are still checking in.

Just briefly, this is my first Mac; I inherited it last fall (2015) from a family member but with a clean Yosemite install. It's a late 2011, 15" , I7, etc. It began having the same problem(s) described in this thread about 4-6 weeks ago, probably when I upgraded initially to El Capitan or the latest version - not sure which.

I'm having one additional twist that I haven't read in any of the other posts: after the startup chime, my login screen is not the smooth pale blue, but rather has pinkish blue horizontal lines. The login box, the shutdown, restart, etc. are all still legible, but it will NOT BOOT from this screen. I've tried 100 times at least, not even in safe or recovery but instead will go to the "smooth" pale blue screen that I assume is what's called the "blue screen of death". After a few seconds here - maybe 15 or 20 seconds - it restarts on it's own back to the "blue lines" login.

Well, magically yesterday the login was smooth (no horizontal pinkish blue lines) and it booted. Guess it was my Valentine Day gift!! While it was up I went thru all the kext files as advised. There are no "Not Signed" and only one "Loadable: No". The "Loadable: No" is AppleOSXUSBNCM.kext (I think -should have written it down). I was not able to either move or delete it because it's a "required system file" or something like that.

There is one, however, named "Unsupported". It showed in the text file on my desktop, but I could never find it in Finder. I found the one immediately preceding it, but "Unsupported" did not show in Finder. It was signed by Apple....something or other.

Sadly, when I did a restart, it's back to the "blue lines" again, so I'm down. I hope I have made a small contribution here with my unique version of the much larger problem.

Where do I go from here?

Thanks!!

Considering the age of your Mac (2011) this could be a hardware issue. If it is a hardware issue, it's usually cheaper to buy a new Mac than repair.

Do you have access to another Mac? If yes, you can use screen sharing to see if the problem Mac looks the same when viewed using screen sharing. This would rule out the monitor but there are other parts like a graphics card that could be going bad. If you could take your Mac into an Apple Store they could run hardware tests.

eg. I have a 2006 iMac. The monitor is shot. It's so bad you can't see anything. However, when I screen share, I can use the old iMac without any issues.

I'm in denial for the present anyway that this is a hardware problem. This computer worked perfectly for a couple of months and only began the freezing, crashing, not booting after I upgraded to El Capitan. This could be coincidence, but in reading thru this thread and others, 90% of the symptoms I'm having are mentioned by others and have been solved with software changes.

Unfortunately, I don't have easy access to another Mac. My workplace has always used windows computers, so I have done the same. I have an external monitor; do you think connecting connecting to it would test the graphics card/monitor? Is the graphics card on the logic board? A logic board for this model is $159, and the instructions for replacing it seem pretty straight forward - provided you have the tools.

Thanks!

When you booted into the recovery drive using Command R, did you ever see the box with OS X Utilities? If not, I suspect it's your install. I suggest you create a USB installer and try installing El Capitan from the USB drive. You'll need a working Mac to download El Capitan installer and prepare the USB drive.

http://blog.macsales.com/33160-how-to-create-a-bootable-el-capitan-usb-install-d rive-with-diskmaker-x

BTW, the MacBook was on sale for $300 off. Just ended. http://9to5toys.com/2016/02/11/12-inch-retina-macbook-sale/

This site posts weekly updates to deals.

Story of my life, a day late and a megabyte short. Thanks for the links; I'll find a Mac and try to create a USB installer. To your question - when this problem first began, I was successful 2 maybe 3 times in booting into the recovery drive but not in the last couple of dozen attempts. Just goes from blue lines to smooth blue.

Thanks again,

Hello GS from NL,

I've followed this thread for a while, but have perhaps a unique problem. Installed El Capitan on mid-2007 iMac. Stuck in reboot. Starts up with some progress before shutting down and rebooting continuously. Never completes the progress bar. No startup mode works for me. Safe Mode doesn't work. Neither does Recovery Mode. I am able to startup in Target mode and connect via Firewire from my MBP. Familiar enough with Terminal to cut and paste, but not sure how to find and delete kexts via Target Mode. Is there a simple command line prefix I can use to run your fix? Don't want to run Terminal on my MBP instead of the iMac.

Thanks in advance for your help.

Vance

Hi Tsofa:

I am having the same issue as many others. My imac keeps restarting after upgrading to el crapitan from snow leopard.

I tried using this terminal kexts command that you mentioned but it isn't working for me.

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/*

My HD is called MacOsx there is no HD in the name. Do I deleted everywhere it says Macintosh HD and replace it with MacOsx. Also I noticed that in other parts of the command it reads Volumes/Macintosh\HD/Library/Application with this I am confused at what not to put. Do I remove both Macintosh\HD or just Macintosh?

macbook air 2011, stuck at boot screen after osx update...

This helped

https://www.justinsilver.com/technology/os-x-el-capitan-10-11-1-hanging-on-boot- fixed

1) boot to recovery mode (hold cmd-R at boot)

2) in terminal compare kexts in "/Library/Extensions/" and "/Volumes/Macintosh HD/Library/Extensions/"

and remove some kexts from "/Volumes/Macintosh HD/Library/Extensions/"

in my case HP and Canon printers

3) reboot and everything works again

Hello GSfromNL,

Thanks for trying to assist everyone here on this thread with their Mac troubles.

When I put this command "system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt", the terminal gives me this output. "/var/root/Desktop/kextList.txt: No such file or directory". I actually recently installed an Antivirus, Avira. Had no issues with my mac, after doing the El Cap update for 2 months now. I need help!!!

PS Mac Book Pro think tis 2012/13 (not sure). 8GB RAM, 750 HDD

Samsung 850 Pro worked when originally formatted with OS 10.11 the failed after 10.11.6. At first could not write one bit and had 1TB left on this 2TB drive. Erase failed as well but read worked. Saved to backup and sent disk to seller. He refused to help and sent the SSD back. Tried to plug it in again just for grins and surprisingly it worked for write and read again and allowed format. Unfortunately it would never again allow OS X boot and froze at the white screen after progress bar completed. SO......

Bought an OCZ 490GB drive and decided to try mounting that with OS X 10.11.6 using Super Duper copy. Nope. Now trying USB boot with a fresh install. Waiting at this moment for it to complete. I called Apple, they said my .09 computer chipset is too old but I upgraded to '10 and 12 core 3.46. Computer boots fine from Seagate 7200 drive every time. THE SSD'S WONT WORK. I don't understand how they managed to screw up SSD's in El C but it has really cost me. I'm so disappointed I may revert everything and just use this machine tilt dies years from now and never buy another tower from apple again. Disgusted Audio musician producer!