From nobody Thu Mar 23 19:23:44 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PjFdP2gfQz41hgr for ; Thu, 23 Mar 2023 19:24:09 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.ipv6.vt.edu [IPv6:2001:468:c80:a103:2:5000:5555:5555]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PjFdN2SG0z3sbV for ; Thu, 23 Mar 2023 19:24:08 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2001:470:e15b:23::23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id B92872880E; Thu, 23 Mar 2023 15:23:55 -0400 (EDT) Content-Type: text/plain; charset=us-ascii List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Subject: Re: Current best practices: UEFI boot on zfsboot nvme raid? From: Paul Mather In-Reply-To: Date: Thu, 23 Mar 2023 15:23:44 -0400 Cc: FreeBSD Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Derek (freebsd lists)" <482254ac@razorfever.net> X-Mailer: Apple Mail (2.3731.400.51.1.1) X-Rspamd-Queue-Id: 4PjFdN2SG0z3sbV X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1312, ipnet:2001:468:c80::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mar 22, 2023, at 4:56 PM, Derek (freebsd lists) = <482254ac@razorfever.net> wrote: > Hiya, >=20 > Wondering what current best practices (13.1-RELEASE) are to make sure = a zfsroot UEFI-boot system with a failed boot disk still boots, given = the need to have a partition with an msdos filesystem to boot? >=20 > My first take is that I'll need to manually update each disks' efi = code whenever /boot/loader.efi is updated, including after directly = after a fresh installation? >=20 > Something that is irking me though, is that a device name is also = hard-coded into /etc/fstab, so if the drive fails, a mounted filesystem = also breaks. I don't see how this can be a good thing, and will also = interfere with a clean reboot, even if the boot code exists elsewhere. >=20 > My guess is, like swap, it might be possible to gmirror across my RAID = this filesystem and remove all of these considerations. Is this the = best practice? I don't know if it's best practices, but that is what I do. I have a = /dev/mirror/efi geom_mirror msdosfs mounted via /etc/fstab on /boot/efi. = That makes it easy to update both copies at once and keep them in sync. However, the HUGE downside is that efibootmgr doesn't appear to work = with GEOM labels, and so I get "efibootmgr: Cannot translate unix loader = path" errors when trying to create new boot entries via "efibootmgr -c". = :-( I believe this Bugzilla is pertinent, and it still appears to be open: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229191 So, I guess best practices for everything working is to stick with the = low-level device names like ada0p1 and so on. Cheers, Paul.=