Date: Wed, 22 Mar 2023 16:56:55 -0400 From: "Derek (freebsd lists)" <482254ac@razorfever.net> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Current best practices: UEFI boot on zfsboot nvme raid? Message-ID: <fa6f8a67-e358-8e09-aeee-90018ec7a5ee@chezmarcotte.ca>
next in thread | raw e-mail | index | archive | help
Hiya, 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? 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? 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. 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 originally tried to revert to BIOS boot where I wouldn't have these concerns, but was unsuccessful at getting my nvme devices to boot. Thoughts appreciated! Derek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fa6f8a67-e358-8e09-aeee-90018ec7a5ee>