Date: Thu, 07 Oct 2021 16:42:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258987 Bug ID: 258987 Summary: 13.0-RELEASE installer broken redundancy with UEFI and ZFS Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: firstname.lastname@example.org When installing FreeBSD 13.0-RELEASE with UEFI and multi-disk (mirror or raidz) ZFS , the expected redundancy is broken twice. 1/ An EFI partition is created on all disks of the pool BUT only the EFI partition of the first disk of the pool is formated and setup, the EFI partition of the other disks are not formated (and of course not setup). As a result, if the first disk of the pool fails, the server will not be able to reboot because of missing content of the EFI partition on the remaining disks. 2/ The installer add an entry in the fstab to mount permanently the efi partition of the first disk to /boot/efi . If that physical disk fails, you have one mounted filesystem from a failed disk. This may jeopardize the stability of the system. One should never mount permanently a filesystem from a non-raid device on a server build for redundancy. All of this is new to 13.0-RELEASE and seems added by the following commit https://cgit.freebsd.org/src/commit/?id=0b7472b3d8d2f1e90fade5236b44fd98d8e396c2 Previous releases (12.1, 12.2) setup correctly the EFI partition of ALL disks and don't add /boot/efi to any physical disk in the fstab. I understand, the new (13.0) method for populating the EFI partition require it to be mounted at install time. The installer should loop thru each EFI partition to format it , mount it temporary, set it up, and unmount it. This could also be done by freebsd-update when needed. By doing this, we could get EFI/zfs installation redundancy reliable again. -- You are receiving this mail because: You are the assignee for the bug.