You are not logged in.
Besides a virtualbox installation, this is my first Arch install. I am installing alongside a crunchbang and a windows partition.
I chose to install with BIOS and GPT. I set up a BIOS Boot Partition and ran grub-install with no errors, but am unable to access grub when booting on the hard drive. I choose HDD from the boot options menu, but it just brings me back to the menu with no errors, loading messages, etc. I assume grub is just not being detected, but I'm not sure why.
The strangest part is that I can boot into grub with no problem when I choose "Boot existing OS" from my Arch install DVD. Grub loads fine, and I can boot into any of the partitions on my hard drive.
My problem seems similar to the one discussed here: http://forums.scotsnewsletter.com/index … opic=61598
But the solution above was to install with UEFI. Is there a way to fix the BIOS/Grub/GPT setup without scrapping BIOS for UEFI?
Last edited by zookeeprr (2014-12-10 18:20:09)
Offline
Did you set up /boot/grub/grub.cfg?
# grub-mkconfig -o /boot/grub/grub.cfg
Offline
I did. I was following the Arch begginer's guide. I installed os-prober and ran
# grub-mkconfig -o /boot/grub/grub.cfg
It found my partitions and can recognize them through the "Boot To existing OS" on the install disc, but not when booting on the hard drive, it bypasses grub entirely and reverts back to the boot menu.
Offline
So you also ran grub-install. What did it output? Did you install it to the entire disk?
Offline
I believe I did. Everything is on /dev/sda, and I ran
grub-install /dev/sda
It completed with no errors.
Offline
Have you checked your firmware (BIOS) options to make sure that the "CSM" (Compatibility Support Module) or "Legacy" mode is enabled?
This is needed to boot in non-EFI mode from a UEFI motherboard.
Offline
I think the crucial difference is that I switched from MBR to GPT. Is there something I could have missed in doing that?
I set up a 2 MiB Bios Boot Partition, but it is not at the beginning of the disc. Would that be a problem?
Last edited by zookeeprr (2014-12-10 19:22:39)
Offline
Have you checked your firmware (BIOS) options to make sure that the "CSM" (Compatibility Support Module) or "Legacy" mode is enabled?
This is needed to boot in non-EFI mode from a UEFI motherboard.
I haven't. I'll do that now.
Offline
Looks good there. I have both UEFI and Legacy enabled, and Legacy is set as the priority. I should add I've been dual booting with crucnhbang and windows with grub already. I was using a MBR setup though, not a GPT.
Offline
I set up a 2 MiB Bios Boot Partition, but it is not at the beginning of the disc. Would that be a problem?
According to the ArchWiki, as long as it's within the first 2TiB of the disk, it should be fine.
https://wiki.archlinux.org/index.php/GR … structions
However, the ArchWiki does also note that there are sometimes incompatibilities which prevent non-EFI booting on a GPT disk.
While GPT support on BIOS systems is theoretically possible it sometimes isn't practical and other times there are complete incompatibilities.
https://wiki.archlinux.org/index.php/GPT#BIOS_systems
There are workarounds listed in that link with some more here:
http://mjg59.dreamwidth.org/8035.html
http://rodsbooks.com/gdisk/bios.html
So you may be best advised to "bite the bullet" and go for a full EFI installation -- you will need an EFI system partition (512MiB, FAT(32) formatted, mounted at /boot) for this.
Offline
That must be it. Hopefully the bullet doesn't taste too terrible!
Should I worry about data loss on my other partitions when switching to an EFI installation? Any pitfalls to avoid? I only have experience with the standard BIOS/grub setup.
Offline
Should I worry about data loss on my other partitions when switching to an EFI installation? Any pitfalls to avoid? I only have experience with the standard BIOS/grub setup.
I can't see why data loss would be an issue.
The only caveat is that you must be booted up in EFI-mode for the bootloader/manager to write the entry to your motherboard's NVRAM.
You can check this by running `efivar -l` -- this will return a long list of EFI variables if you are.
I recommend gummiboot -- it's a bootmanager and allows the kernel to boot itself up (and it's the easiest one to use).
https://wiki.archlinux.org/index.php/Be … therboards
Offline
Great stuff. Thanks for the help. Wish me luck!
Offline