This process will wipe OS X and any other data you have on the machine. Please make sure to backup your system before proceeding.
You may wish to create a recovery disk so that you may restore OSX at a later date, if required.
Create a Live USB with Ubuntu
Refer to this page for detailed instructions. UNetbootin is recommended since it is cross plaform and provides a Graphical User Interface (GUI).
NOTE - Do NOT use the +mac version since it does not support EFI boot.
Boot from the Live USB
The trick to booting from USB on Macs is to hold down the option key as soon as you power on the device. Select EFI Boot from this menu.
Ubuntu should now boot up from the USB. Install Ubuntu using the Erase and use Entire Disk option.
Firstly, when you reboot/power on your Mac, you will see the grey screen of the Mac bootloader for about 30s, and then a gently flashing folder with a '?' inside. If you insert the installer USB now, it should boot. If not, try holding the power button to force the power off, and then follow the USB booting instructions to bring it up.
Boot Manually from Your Hard Drive
At this point the system is unbootable because the Mac bootloader expects the EFI partition to be formatted as HFS+, the typical Mac filesystem, while the Ubuntu installer actually formats it as VFAT.
In this step we'll instruct GRUB on the Live USB too boot off of your newly installed Ubuntu on the hard drive. – This will requires some serious typing, but after having booted this way we'll be ready to set up automatic boot in the next step.
If you’re using the desktop installer, hold the shift key to bring up the GRUB bootloader menu.
When you see the GRUB boot menu, don't select any of the entries. Instead, press C to bring up the GRUB console.
At the grub console, type ls
grub> ls
(memdisk) (hd0) (hd0,msdos) (hd1) (hd2) (hd2,gpt3) (hd2,gpt2)
(hd2,gpt1)
You may not get exactly the same results as this, but you’ll have some similar options.
Now, find the partition which contains your user's home directory.
grub> ls (hd2,gpt2)/home
rohith/
Keep trying until you find it.
The result from the last step has two parts: (hdX,gptY). You need to keep the hdX part, but go through all the gptY options looking for a /boot/grub directory.
grub> ls (hd2,gpt2)/boot/grub
unicode.pf2 [...] grub.cfg
Now you want to set this as your root for further commands.
grub> set root=(hd2,gpt2)
The only way to boot properly is to use the UUID of the drive.
grub> ls -l (hd2,gpt2)
Note down the UUID. You'll have to type it manually in the next step.
grub> linux /boot/vmlinuz〈Tab here!〉.efi.signed root=UUID=〈the UUID from above〉
The GRUB console can do tab completion, so if you just type out the vmlinuz part and hit tab, then hit . and tab again, you won't have to type the whole file name. make sure that the efi.signed part is present.
Now, set the initial RAM disk
grub> initrd /boot/initrd〈Tab here!〉
You should be able to boot off your hard drive the command
grub> boot
Setting up Automatic Boot
You have now booted into your newly installed Ubuntu. Next step is to make boot automatic and pain free, by reformatting the /boot/efi partition to the HFS+ file system that Mac expects, and allowing you to boot straight off of it.
1. Installing Extra Packages
Now, open a terminal and type
sudo add-apt-repository ppa:detly/mactel-utils
sudo apt-get update
sudo apt-get install mactel-boot hfsprogs gdisk grub-efi-amd64
2. Reformatting the EFI Partition
Run mount to get a list of mounted filesystems, and look for anything mounted at /boot/efi. Unmount it.
sudo umount /dev/sda1
We now use gdisk to delete the VFAT partition and create an HFS+ one
sudo gdisk /dev/sda
(Note that there is NO number at the end of that disk name!)
Press p
Confirm that the first partition has type EF00. Now we delete that EF00 partition.
Press d
Create a new HFS+ one in its place.
Press n
Press enter for the first and last sector options.
Enter AF00 for the filesystem code.
Use the p command to double-check your changes, and then w to write.
Now we have an unformatted HFS+ partition. Format it with:
sudo mkfs.hfsplus /dev/sda1 -v ubuntu
3. Updating the Filesystem Table
Edit /etc/fstab
sudoedit /etc/fstab
Delete the lines that refer to /boot/efi using Ctrl+K.
Now, type the following commands -
sudo bash -c 'echo $(blkid -o export -s UUID /dev/sda1) /boot/efi auto defaults 0 0 >> /etc/fstab'
mount /boot/efi
4. Installing GRUB on the HFS Partition
sudo bash -c 'echo "This file is required for booting" > /boot/efi/mach_kernel'
Install GRUB and 'bless' the filesystem.
sudo grub-install --target x86_64-efi --boot-directory=/boot --efi-directory=/boot/efi
sudo hfs-bless "/boot/efi/System/Library/CoreServices/boot.efi"
EDIT Some Troubleshooting: When following these instructions on Ubuntu 14.04 Trusty Tahr, I got the following error message from grub-install
Installing for x86_64-efi platform.grub-install
error: Can't create file: No such file or directory.
After running it again with strace I determined that it wasn't looking for a file called /boot/efi/mach_kernel, but a file called /boot/efi/EFI/ubuntu/mach_kernel and after creating that file, and re-running grub-install everything seems to work. END EDIT
5. Removing the Boot Delay
To set the default EFI boot entry, run
sudo efibootmgr
Get rid of the extra entries -
sudo efibootmgr -b xxxx -B
where xxxx is the boot number obtained from sudo efibootmgr
Now, set the default entry -
sudo efibootmgr -o xxxx
The system should now be bootable!
CREDITS
Jason Heeris - For his original post, the PPA used.
Rohith Madhavan - For the post on Ask Ubuntu, minor modifications.
Best Answer
First, the GParted message about the primary GPT data being corrupt but the backup being OK means that there's a SERIOUS problem with your partition table. FIX IT IMMEDIATELY!!!! If you don't know how to do this, consult my page on the subject and/or post another question. (You'll need to provide details, like the output of
gdisk'spandvcommands, if you expect any real help.) Continuing to use a computer with a damaged partition table more-or-less guarantees that you'll have serious trouble sooner or later -- and in this context, "serious trouble" could mean a complete loss of all the data on your computer! Note, however, that attempts to repair damaged partition tables can sometimes lead to even worse problems, so don't go mucking about randomly. Back up the whole disk and, if you don't know what you're doing, ask for help!Second, now that you've installed rEFInd, you should be able to boot either OS X or Ubuntu from rEFInd. Since Ubuntu isn't launching, there's obviously a problem, but you've provided insufficient details for a proper diagnosis. Please run the Boot Info Script. This will generate a file called
RESULTS.txt. Post that file to a pastebin site and post the URL to your document here. This will give us more details about your configuration, which may help with the diagnosis. Also, please describe what icon and description is associated with the Ubuntu/Linux option in rEFInd, and describe what happens when you try to launch it. If there are multiple Ubuntu or Linux options in rEFInd, try them all, and describe what happens for each one when it fails.I recommend you add a comment to this answer and edit your original question to provide the new information.
EDIT:
It sounds like your Ubuntu boot problems are related to video drivers. There are numerous questions and answers on this site about "black screen" problems when booting Ubuntu, particularly in EFI mode. I recommend you search for them. You can probably overcome the issue by adding an appropriate keyword or two to the kernel's options, but what option will work depends on your hardware. In rEFInd, you can add options by hitting F2 or Insert twice, rather than Enter, when launching the
boot/vmlinuz-*entry. If you find kernel options that work, you can then add them to the/boot/refind_linux.conffile to make them permanent. (If that file doesn't exist, themkrlconfscript that comes with rEFInd will create it, but you must run that script viasudo.)