So I recently installed the Yosemite beta on my Macbook Pro. I dual boot OS X and Ubuntu with a partitioned hard drive using rEFIt. But after installing Yosemite, rEFIt disappeared and with it, my access to my Ubuntu partition. Now, I don't have any critical files on the linux side of things, so I'm okay with just living in Yosemite if I need to, but I'd like to get the old functionality back.
I've tried various solutions and this is as far as I got so far:
I installed rEFInd following the instructions for a manual installation in OS X, as found here: The rEFInd Boot Manager: Installing rEFInd
This included going the route of making a directory under /Volumes/esp and mounting that directory.
I then moved all the rEFInd files into /Volumes/esp and blessed them as the new boot.
After restarting, I booted into rEFInd, but it only recognized my Ubuntu EFI partition and not my OS X partition.
I chose the option to recover Mac OS X that rEFInd gave me, since I wanted to first make sure I could boot back into OS X.
This took me to the restore/recover OS X utility.
I chose to just restart.
Restarted back into Yosemite.
Everything's fine, but now I've lost the ability to boot into rEFInd again without repeating the installation. The directory that I mounted in /Volumes is gone.
So I'm wondering if this is a normal behavior with regards to wiping /Volumes after a reboot or if it's a Yosemite quirk/bug. I've never really had any reason to go exploring /Volumes before so I'm not sure what its normal behavior is. I suppose what I really want to know is if there's a way that I can get a more stable installation of rEFInd that doesn't require me to mount it and then bless it each time I want to boot into my linux partition. If that's not viable, would just creating a shell script that does the mounting and blessing for me be a better option? And any ideas as to why rEFInd identified my Ubuntu partition but not my main OS X partition? Thanks.
Some other notes:
rEFIt was totally disabled, which led me to switch to rEFInd. I tried reinstalling rEFIt and it failed. rEFInd also failed to work unless I mounted /Volumes/esp and then blessed it. Just using rEFInd's install.sh did nothing. Holding the option key on startup also doesn't produce any difference.
I've tried various solutions and this is as far as I got so far:
I installed rEFInd following the instructions for a manual installation in OS X, as found here: The rEFInd Boot Manager: Installing rEFInd
This included going the route of making a directory under /Volumes/esp and mounting that directory.
I then moved all the rEFInd files into /Volumes/esp and blessed them as the new boot.
After restarting, I booted into rEFInd, but it only recognized my Ubuntu EFI partition and not my OS X partition.
I chose the option to recover Mac OS X that rEFInd gave me, since I wanted to first make sure I could boot back into OS X.
This took me to the restore/recover OS X utility.
I chose to just restart.
Restarted back into Yosemite.
Everything's fine, but now I've lost the ability to boot into rEFInd again without repeating the installation. The directory that I mounted in /Volumes is gone.
So I'm wondering if this is a normal behavior with regards to wiping /Volumes after a reboot or if it's a Yosemite quirk/bug. I've never really had any reason to go exploring /Volumes before so I'm not sure what its normal behavior is. I suppose what I really want to know is if there's a way that I can get a more stable installation of rEFInd that doesn't require me to mount it and then bless it each time I want to boot into my linux partition. If that's not viable, would just creating a shell script that does the mounting and blessing for me be a better option? And any ideas as to why rEFInd identified my Ubuntu partition but not my main OS X partition? Thanks.
Some other notes:
rEFIt was totally disabled, which led me to switch to rEFInd. I tried reinstalling rEFIt and it failed. rEFInd also failed to work unless I mounted /Volumes/esp and then blessed it. Just using rEFInd's install.sh did nothing. Holding the option key on startup also doesn't produce any difference.