From owner-freebsd-amd64@freebsd.org Wed Feb 17 02:56:00 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C798AAB3B6 for ; Wed, 17 Feb 2016 02:56:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74D641AA9 for ; Wed, 17 Feb 2016 02:56:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1H2u03L055044 for ; Wed, 17 Feb 2016 02:56:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207269] boot1.efi loading wrong system Date: Wed, 17 Feb 2016 02:56:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eu9gu4@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 17 Feb 2016 04:23:57 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2016 02:56:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207269 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@FreeBSD.org Reporter: eu9gu4@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Actually this is about FreeBSD 10.3-beta2, but it was not option to chose f= rom 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 cas= e: 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 S= SD, 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=