No bootable device found - mac-mini (late 2012) and Centos 7
An EFI boot manager utility
Status: Beta
Brought to you by:
srs5694
Menu
▾
▴
I am trying to make my mac-mini dual-boot into Cent-os 7 which not touching my OSX (mavericks atm) install.
I shrank the OSX install successfully, and installed refind-0.10.0-1 using the OSX install script.
When the system boots I see refind and it can boot OSX just fine.
I then tried installing Centos 7 from the DVS, but it failed complaining that grub's core.img would not fit anywhere.
So I burnd a gparted-live DVD, and used that to move the 3 OSX partions (EFI, Customer, Recovery) by 1MB.
This works fine, and I can still boot into OSX using refind..
Then I managed to install Centos7 just fine, but it refuses to boot. Refind shows up and
has OSX, OSX recover, and a Linux icon (and another X-DVD when teh superdrive is attached)
But under the Linux icon there is no kernel version mentioned, and when I press FN-F2 twice I
get am empty booty commandline..
when I try to boot I get
no bootable device found - insert one and press any key
so I boot into the Centos recovery from the DVD
and I see this
What else do I need to do to make this work?
any help is appreciated
Try removing all the filesystem driver files from
/mnt/efi/EFI/BOOT/drivers_x64except for theext4_x64.efifile. You currently have all the filesystem drivers installed simultaneously, and that sometimes creates problems, particularly on Macs.Thanks. I tried that but i still get the same 'No bootable device' message..
I just noticed a detail in your description that makes me think the Linux entry you're trying to boot is for a BIOS-mode boot loader. That will work if and only if you've got a hybrid MBR, as described here. If you don't have a hybrid MBR, you could try creating one and see if that helps.
Alternatively, do you see any entries that refer to your kernel file(s) by name (as in
vmlinuz-3.10.0-229.el7.x86_64)? Assuming you have a driver for the filesystem you used on/boot, you should see such an entry, and it should work; however, you may need to add aroot=/dev/mapper/centos_n2--vmhost-rootkernel option by hitting F2 or Insert twice to launch it, at least until you can runmkrlconfin Linux to build a/boot/refind_linux.conffile. If you don't see such an entry, it might be worth trying to diagnose why it's not showing up. To that end, what filesystem is in use on/boot? Btrfs might require extra options to work correctly. You could try installing an EFI shell to see if you can locate the kernel from it, which would help with such reconfiguration.I use ext4 on /boot, because Centos7 by default is xfs which i suspected wasn't supported.
and no, I have nothing referring to a linux kernel by name. when I pres F2 twice I get just an empty editor without anything else
what would the complete rub commandline look like?
On a hunch, I booted back into gparted and named /dev/sda5 '/boot' and gave it the label 'boot' and now it works
That's strange. Are you seeing the same Linux icon as before, or has that changed to a CentOS or Fedora icon? When you boot to CentOS, is there a directory called
/sys/firmware/efi? Also, could you post the output ofcat /proc/cmdline? I'm just trying to understand what's going on, since renaming that volume should not have made any difference.I see the same Linux icon..
[root@os-ctrl sys]# cd firmware
[root@os-ctrl firmware]# ls
acpi dmi memmap
[root@os-ctrl firmware]#
BOOT_IMAGE=/vmlinuz-3.10.0-229.el7.x86_64 root=/dev/mapper/centos_n2--vmhost-root ro vconsole.font=latarcyrheb-sun16 rd.lvm.lv=centos_n2-vmhost/swap vconsole.keymap=us rd.lvm.lv=centos_n2-vmhost/root rhgb quiet LANG=en_US.UTF-8
You're almost certainly booting in BIOS mode, not in EFI mode. I still don't know why your kernels aren't showing up as options in the rEFInd menu -- but if you're happy booting the way you are booting, I'd say it's best to leave it where it is.