[Bug 207269] boot1.efi loading wrong system
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Feb 17 02:56:00 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207269
Bug ID: 207269
Summary: boot1.efi loading wrong system
Product: Base System
Version: 11.0-CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: eu9gu4 at gmail.com
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
Actually this is about FreeBSD 10.3-beta2, but it was not option to chose from
when reporting the bug.
I think /boot/boot1.efi boots the first FreeBSD bootable partition that it
finds, instead of looking further and trying to boot the system on its own
partition.
This is wrong in case there are two FreeBSD systems installed, as in my case:
My machine has a HDD connected to 1st SATA port, a SSD connected to 2nd SATA
port and a few other hard disks used for data and not interacting yet with
FreeBSD.
The HDD is ada4 (sda in Linux) and the SDD is ada5 (sdb in Linux).
The HDD has a first partition set as EFI, from where GRUB boots all my
operating systems: FreeBSD, Linux and Windows.
Everything was fine with the first FreeBSD installed on HDD.
After installing the second FreeBSD on SSD, I can only boot the first one
installed on HDD, regardless of the option I select in GRUB, which has two
separate entries for FreeBSD:
..
chainloader (hd0,gpt9)/boot/boot1.efi (for HDD)
and
..
chainloader (hd3,gpt5)/boot/boot1.efi (for SSD)
During setup I skipped the creation of another EFI partition as proposed by
installer, because I already had one and I knew that /EFI/BOOT/BOOTX64.EFI is a
simple copy of boot1.efi.
My choice of this specific configuration is coming from a recently failed SSD,
I just wanted to have an immediate option available if my SSD fails again.
Can boot1.efi by modified in a way that allows booting multiple systems if they
exist on different partitions?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list