Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

teezy

macrumors regular
Original poster
Jul 18, 2012
118
26
Tri-State Area, USA
Copy and pasting this from my post/comment on a Gizmodo article (which apparently hasn't gotten "approved" yet) so excuse any chronological "inaccuracies". The only thing different is the amendment of the next sentence and the next sentence only, along with re-wording the following sentence so it makes sense.........

I'll preface this by saying that I was invited to participate in the El Capitan beta program but never did download any of the beta releases lol. Because I was invited to participate, I was granted access to the GM, which I installed last night.

Ran my next Time Machine backup, and installed 10.11 with no issues... until about a half hour later when the machine booted up and that’s where I ran into a bunch of brick walls (in a software/app compatibility regard). Lol, I was up for another hour or so updating as much as I can. This was expected, though, because it was only about 4-5 hours after I got the email when I actually got the chance to download the installer and run it, and not many apps were updated for 10.11 compatibility ahead of time (most notably, Xtrafinder *sad face*).

One big issue I’ve run into - which I don’t think is much of a 10.11 issue as it is the way I set the darn thing up - is with the new SIP setup. I’ve been using cDock for the past year with Yosemite, and apparently with El Capitan there’s this “protection” (rootless) thing, I reckon for the end-user’s benefit, that will require the user to disable it, install some sort of... proxy or... helper file/tool into the kernel and then re-enable the “protection” so apps like cDock can work. I know exactly what I need to do JUST to disable/re-enable SIP (“csrutil disable” in Terminal), but for some reason, I can’t access recovery on my boot drive.

A heads up:

My machine is a mid-2012 MacBook Pro 13” (the 2.9GHz setup)

My boot drive is an SSD. Has the OS partition and a Recovery HD partition... and that other first partition that’s like 325kb or whatever, I forgot.

I’ve done the optical drive “mod”, where I have another hard drive installed into the machine (its the original Toshiba 750GB HDD) that I use as a scratch disk for video editing and whatnot. I also use it as a fail-safe, in case for some magical reason I can’t boot onto my main drive, meaning it does have a working copy of OSX 10.9.5 on it. Purposely not updating it because I need a “way back” into that UI, lol (not really). There’s a recovery partition on that drive too, which shows up in the boot menu as well as diskutil -list, of course.

Anyway, the recovery partition on my SSD shows up when I run the diskutil -list command as disk0s2 (IIRC), but when I run the command in recovery from the HDD, or my Time Machine disk, at the foot of the diskutil -list results says “Macintosh SSD...” (that’s what I named it) “... [insert UUID here] is locked and encrypted” or something along those lines (perhaps because I have FileVault enabled on the SSD), which makes me wonder if the reason that I can’t get to the recovery partition on my SSD is because the drive is encrypted at the boot menu(???)... then I read something about reverting corestorage or something... blah. Idunno. But I DO know that I can’t get into my “active” recovery, at all. I don’t recall having this “issue” before I updated to 10.11.

Any tips? I was gonna disable FileVault but I had to get some sleep, so I left it alone, lol.
 
Try restarting with Command+R. That should boot into your recovery partition.

Yosemite and El Capitan installers often create core storage where it wasn't there before. This prevents the recovery partition from showing up in the startup manager.

If the installation creates a core storage logical volume then provided it is revertible you can revert it to get partitions back to normal by running these 2 commands in terminal.

diskutil cs list

and then

diskutil coreStorage revert lvUUID

where lvUUID is the last lvUUID reported by the previous Terminal command.

Then restart for everything to get back to normal after you have run these commands in Terminal.

If you successfully revert your core storage then you should now see the recovery partition in your startup manager with starting up with the option key held down.
 
Last edited:
Any tips? I was gonna disable FileVault but I had to get some sleep, so I left it alone, lol.

I'm confused at this point exactly what you are trying to do? Do you want to reinstall (restore) Yosemite from the Time Machine backup?
 
Try restarting with Command+R. That should boot into your recovery partition.

Yosemite and El Capitan installers often create core storage where it wasn't there before. This prevents the recovery partition from showing up in the startup manager.

If the installation creates a core storage logical volume then provided it is revertible you can revert it to get partitions back to normal by running these 2 commands in terminal.

diskutil cs list

and then

diskutil coreStorage revert lvUUID

where lvUUID is the last lvUUID reported by the previous Terminal command.

Then restart for everything to get back to normal after you have run these commands in Terminal.

If you successfully revert your core storage then you should now see the recovery partition in your startup manager with starting up with the option key held down.

When I try the cmd+r method, I'm booted into Internet Recovery instead of the local recovery that "should" be readily available. Strange, right? I'll try that revert thing though.
 
Last edited:
I'm confused at this point exactly what you are trying to do? Do you want to reinstall (restore) Yosemite from the Time Machine backup?

Nope. I want to use cDock.
Thanks to 10.11, there's that new System Integrity Protection that needs to be temporarily disable so a certain command can be entered in Terminal (only in recovery mode) and then re-enabled so that apps like cDock and possibly Finder bar mods and so on... can work. Sorry about the confusion.

The issue at hand is that I can't boot into local recovery... I can only either get to internet recovery, recovery on my time machine drive, or recovery on my other hard drive (that's running 10.9).. not recovery on my el capitan drive, which is my main drive
 
Nope. I want to use cDock.
Thanks to 10.11, there's that new System Integrity Protection that needs to be temporarily disable so a certain command can be entered in Terminal (only in recovery mode) and then re-enabled so that apps like cDock and possibly Finder bar mods and so on... can work. Sorry about the confusion.

The issue at hand is that I can't boot into local recovery... I can only either get to internet recovery, recovery on my time machine drive, or recovery on my other hard drive (that's running 10.9).. not recovery on my el capitan drive, which is my main drive
Have you installed the OS X El Capitan Recovery Update Version 2.0 Available for Beta Users?
 
Only if it shows up in your updates tab in the mac app store. I doubt it will though after installing the GM.
 
Try restarting with Command+R. That should boot into your recovery partition.

Yosemite and El Capitan installers often create core storage where it wasn't there before. This prevents the recovery partition from showing up in the startup manager.

If the installation creates a core storage logical volume then provided it is revertible you can revert it to get partitions back to normal by running these 2 commands in terminal.

diskutil cs list

and then

diskutil coreStorage revert lvUUID

where lvUUID is the last lvUUID reported by the previous Terminal command.

Then restart for everything to get back to normal after you have run these commands in Terminal.

If you successfully revert your core storage then you should now see the recovery partition in your startup manager with starting up with the option key held down.

Trying this now! Still booting into Internet Recovery with Cmd+R even after installing the 10.11 Final. Sigh, lol

Edit: I was freaking out, because the conversion was "paused" in Terminal (kept checking every like 20 seconds or so), then I went to the FileVault menu and saw that I have to connect my Macbook to the charger in order for it to work... which makes complete sense. I'm in class though, didn't bother bringing my charger. I'll have to let it run when I get home. Hopefully it works! I need cDock and Xtrafinder working, lol.

Edit 2: thanks, ty! followed your instructions and that surely did the trick. got my local recovery back lol. cDock and XtraFinder are both working great too, even after turning SIP back on. now I can turn FileVault back on! haha
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.