Date: Thu, 23 Mar 2023 15:33:21 -0400 From: "Derek (freebsd lists)" <482254ac@razorfever.net> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Current best practices: UEFI boot on zfsboot nvme raid? Message-ID: <c9cce226-5581-bfa5-f6d4-ae940791f206@chezmarcotte.ca> In-Reply-To: <D17EBA11-C66B-4271-A83A-FBD0936BB8B6@gromit.dlib.vt.edu> References: <fa6f8a67-e358-8e09-aeee-90018ec7a5ee@chezmarcotte.ca> <D17EBA11-C66B-4271-A83A-FBD0936BB8B6@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-03-23 15:23, Paul Mather wrote: > On Mar 22, 2023, at 4:56 PM, Derek (freebsd lists) <482254ac@razorfever.net> wrote: > >> 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=229191 > > So, I guess best practices for everything working is to stick with the low-level device names like ada0p1 and so on. > This is great information, and good leads to follow. Thanks for your reply. For those finding the thread later, I feel like "stick with low-level device names" refers to the work around when using efibootmgr referenced in the bug. People do win on freebsd-questions! Derek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c9cce226-5581-bfa5-f6d4-ae940791f206>