El Capitan won't Boot after update

When does 12.1.1 come out?

This helped me too! Have a mid 2010 MacBook Pro 13". Factory components.

Symptom: I could only use El-capitan just after the El-capitan installation, but when I rebooted it got stuck at the boot screen with a empty status bar. I reboot the computer because it was very slow.

This did work!

1. sudo rm -rf /System/Library/Extensions/EltimaAsync.kext

2. sudo touch /Volumes/<Name of your hardrive>/System/Library/Extensions

This did NOT work!

1. Safe mode (SHIFT button) during boot did not work. Nothing happened. This should only boot with necessary extensions :-(

2. Reinstall El-capitan from system recovery did not work (El-capitan only works directly after installation)

3. Repair disk permissions did not work.

Hope this helps!

When this happens, it *seems*, from cursory research, to mostly be the 2010-2011 systems getting this issue.

So that begs the question, is there something about the ROM or system board that makes these more susceptible, or is it just that so few of them are nuke-n-pave fresh installs of The Cap, so there's just legacy stuff going on in the system's software bowels.

* shrug *

Both my mid-2011 systems seem fine since the 10.11.1 update recently.

My MB Pro 13" is an early 2011. Haven't had any problems since killing EltimaAsync.kext. 10.11.1 has been fine.

After updating to El Capitan 10.11.1 my MacBook Pro (2012) had the "Blinking Folder". It turn out that the boot record was missing on the Crucial SSD. I followed this procedure from The Gippy Pages and it worked!!

http://top-frog.com/2010/02/03/blinking-question-mark-on-os-x-boot-dont-panic-ju st-yet/

After this procedure I made a clone copy of my hard drive as a "just in case" scenario that El Capitan would strike again. I was fearful that it wasn't playing well with my Crucial M4 500gb SSD.... and that may well have been the case. As a precaution I opted to buy a new Samsung 850 EVO 500gb an cloned my Crucial SSD to it. I'm running on my new Samsung 850 EVO SSD as of the writing. By the way, trim is enabled on both my SSD's without any modifications.

you are good as I managed to get to recovery and start to reinstall El Capitan. gracias

Hi , i was able to remove MACFUSE with this instructions:

http://blog.downloadnp.com/2014/08/how-to-uninstall-macfuse-using-terminal.html

It worked with me !!!

Cheers

Identical problem on MacBook Pro Retina Mid 2012 - restarting or shutdown would result in the apple logo and the bar ....

After reinstalling El Capitan two times it was clearly a reproducable event as such a undocumented feature.

This trick solved the problem. thanks a lot!!!

Apple please get out a fix asap.

same problem not solve

I have a MacPro4,1 that was running Yosemite from an internal RAID array (4 disks - I think arranged as RAID10).

I updated to El Capitan at the weekend, and now the system won't boot from El Capitan on the internal disks.

I get the Prohibitory sign every time:

- Normal Boot

- Verbose Boot

- Safe Mode

- Single User Mode

I've reset the SMC. Zapped the PRAM. It will not boot from the internal disk array.

I can't get OS Recovery from the internal disks. Apple doesn't support this on bootable software RAID array.

I managed to make up a bootable USB installer for El Capitan.

I used that to create an El Capitan system on an external USB drive that allowed me to boot a new system setup.

The individual RAID HDD check out OK. I can even mount the logical partition. But I cannot boot from it.

BTW - The new Disk Utility is pretty, but pretty unusable. Retro-grade step by Apple.

I have a Time Machine backup of my Yosemite configuration, but when I tried to restore to the internal software RAID array from El Capitan, it couldn't delete the old setup and write the Time Machine setup.

I'm happy enough in Terminal - and had a look through /System/Library/Extensions - there's some pretty old stuff in there since this machine has had Mavericks & Yosemite. But nothing that would suggest that the system should be unbootable.

I've also got a MaxPower eSATA 6G Pro PCIe Controller (gives me an external eSATA connector for an external HW RAID array I have). The card complies with the AHCI standard and so used standard Apple drivers - nothing special.

Before I try building a Yosemite external USB drive to boot from and try using that to blow my internal RAID setup away, does anyone have any ideas on how I can rescue this? It's pretty important to me ... 8000+ photographs (all backed up !! but still a pain in to have to rebuild everything)

After an El Capitain upgrade, I had the same problem as mentioned on the start of this thread.

I had done two reinstalls, one internet reinstall, reinstalled files from time machine and eventually got my computer running (as I am fairly new to Macs even this much I had to do with some help from Apple Support, about 8hrs worth including waits for the computer to catch up).

Then on a reboot, the same problem occurred. Usual restart attempts. AppleChat even suggested 'it might be a hardware problem'. Finally found the post below using my phone and emailed it to myself, checking the name of my Macintosh disk in Disk Utility (as the original name had been overwritten with the last clean reinstall). It worked.

Thank you very much, to the forum, and to those concerned.

iMac (27-inch, Late 2013) 10.11.1

RusFox Oct 6, 2015 2:48 PM
Re: El Capitan won't Boot after update in response to Joe Winke Helpful Helpful

Its work!:

Posted by TSOPA from Reboot fail after installing El Capitan help!!

Hey I ran across this fix and it worked for me on two machines.

Email this code to yourself, but change the machine name to YOUR EXACT(!) HardDisk-name.

• cd "/Volumes/Macintosh HD/Library/Extensions/" ; mkdir Unsupported ; mv Net* Unsupported ; mv Sym* Unsupported ; mv hp* Unsupported ; mv ndc* Unsupported ; cd "/Volumes/Macintosh HD/System/Library/Extensions/" ; mkdir Unsupported ; mv Belc* Unsupported ; mv Eltima* Unsupported ; mv hp* Unsupported ; mv Hua* Unsupported ; mv Netg* Unsupported ; mv Remo* Unsupported ; mv RIM* Unsupported ; mv USBEx* Unsupported ; rm -Rf /Volumes/Macintosh HD/Library/Filesystems/*fuse* ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Sym* ; rm -Rf /Volumes/Macintosh\ HD/var/folders/*

Boot in Restore mode.

Click OS help and Safari will open

Open your email and copy the code

Quit Safari and open Terminal from the top menu

Paste the code and hit return.

Give it a minute or two. When it is done you will then be able to quit Terminal.

Restart. Be patient, restart does not begin immediately, and in 20-30 seconds

Will Apple make an announcement when it is safe to upgrade to El Capitan?

I'm sure in their eyes, it is safe now. I've had this same problem on 2 mid-2011 iMacs, but I'm sure those having this issue are outliers upgrading from some earlier machines and versions. *shrug*

"Safe" is a relative term here; I didn't lose any data, just couldn't boot until I found this and similar threads of discussion, and found a quick and easy fix.

I'm not excusing it... but they can't test for every situation with every piece of hardware and every bit of software.

I'm sure they'll address it... PS.. the recent .1 update (10.11.1...?) went on without a hitch on both machines.

Also could not reboot, mine got login screen, but just hung at spinning white dots and spinning colored circular cursor. Both just kept spinning .... Used Command-R to get to recovery options and went back to 10.10. My machine is 2009 iMac, and same no boot up issue with Yosemite, recovered again with TM. I will skip 10.11for 10.12. Apple soft quality control appears to have diminished over the past few years. Inexcusable to release an update that causes total machine malfunction. I am hopeful and confident apple's big brains will solve this programming debacle in short order.

I strongly disagree!