Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jun 2026 12:02:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 295997] Improve docs, manpages and mountpoints around multiple /dev/gpt/efibootN and /dev/gpt/gptbootN
Message-ID:  <bug-295997-227@https.bugs.freebsd.org/bugzilla/>

index | next in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295997

            Bug ID: 295997
           Summary: Improve docs, manpages and mountpoints around multiple
                    /dev/gpt/efibootN and /dev/gpt/gptbootN
           Product: Base System
           Version: 14.4-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: michaelo@FreeBSD.org

This is coming from Bug 294338 and my experiencing installing a brand new HPE
ProLiant server with ZFS mirror on two disks:

Installation: When the installer creates GPT partition tables onto mirrored or
ZRAID'd disks, it also creates the ESPs and assigns them labels: efibootN where
N is the counter for the amount of ESPs (disks). An entry in the fstab is
created for the efiboot0 label (first one) only. The otherones aren't even
mounted. This isn't mentioned not visible why the rest is not mounted as
/boot/efiN. Updating boot code or installing EFI applications on all ESPs
requires mount/umount through all disks. For consistency reasons one would
expect fstab would contain /boot/efi0, /boot/efi1, and so forth for every
single disk beating part of zroot. Maybe this also applies to UFS, but I have
never used UFS outside of HW RAID where only one bootable UFS drive exists.

Documentation and manpages: There several ones like upgrading notes, likely
handbook and loader/uefi-related manpages which only mention /boot/efi and
nothing else, no mention of other possible ESPs in the system.
Upgrade/modification instructions apply to efiboot0/gptboot0 thus /boot/efi(0)
only. Here I would expect that docs and manpages would consistently mention
that boot code needs to be updated/installed on ALL affected ESPs or
freebsd-boot partitions which can be used for booting the system.

-- 
You are receiving this mail because:
You are the assignee for the bug.

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-295997-227>