doc(ZFS): update UEFI loader instructions for 13+ #408
Conversation
FreeBSD 13.0+ no longer have boot1.efifat, so replace those instructions with the relevant commands and add reference to loader.efi man page.
| @@ -1335,11 +1335,13 @@ For systems using EFI to boot, execute the following command: | |||
|
|
|||
| [source,shell] | |||
| .... | |||
| # gpart bootcode -p /boot/boot1.efifat -i 1 ada1 | |||
| # mount_msdosfs /dev/ada1p1 /boot/efi | |||
There was a problem hiding this comment.
By default this will automatically be mounted (bsdinstall puts it in fstab) and so will fail with mount_msdosfs: /dev/ada1p1: Device busy. If you need to mount it manually for whatever reason, mount -t msdosfs is better than mount_msdosfs (which is a bit of an implementation detail).
There was a problem hiding this comment.
Correction, it "may fail." You're assuming the disks were created with bsdinstall. There are more than a few FreeBSD disks roaming about that were installed with sysinstall or were manually partitioned to match disks installed long ago.
There was a problem hiding this comment.
I realise. I deliberately said by default at the start of the sentence to fully acknowledge there are other ways to get a working FreeBSD system. That is, by default it will fail. That doesn't mean it will always fail.
There was a problem hiding this comment.
How about this?
mount -t msdosfs -u /dev/ada1p1 /boot/efi| @@ -1335,11 +1335,13 @@ For systems using EFI to boot, execute the following command: | |||
|
|
|||
| [source,shell] | |||
| .... | |||
| # gpart bootcode -p /boot/boot1.efifat -i 1 ada1 | |||
| # mount_msdosfs /dev/ada1p1 /boot/efi | |||
| # cp /boot/loader.efi /boot/efi/efi/boot/bootx64.efi | |||
There was a problem hiding this comment.
Fair point. Most of the other FreeBSD docs I've seen only copy loader.efi to bootx64.efi, as that's correct likely ~99% of the time. The wiki page and man page note there is no 32-bit UEFI support.
The two options 'x64' and 'aa64' would cover probably 99.9% of cases.
# cp /boot/loader.efi /boot/efi/efi/boot/bootx64.efi
or
# cp /boot/loader.efi /boot/efi/efi/boot/bootaa64.efiTo cover all cases, perhaps borrow from the convention used in the loader.efi man page?
# cp /boot/loader.efi /boot/efi/efi/boot/bootXXX.efi (see uefi(8) for values to replace ‘XXX’ with)I don't have enough knowledge to explain why we don't just direct users to only copy it to the designated FreeBSD spot:
# cp /boot/loader.efi /boot/efi/efi/freebsd/loader.efiThere was a problem hiding this comment.
This needs to follow the same approach as loader.efi(8). Both locations are important, but which is more important depends on your system. Only updating the removable media path would be wrong for most desktop and server systems. Only updating the FreeBSD-specific path would be wrong for most SBC systems.
|
Any news with this patch? |
|
The current instructions are still completely broken for supported versions of FreeBSD. This patch makes them much less broken, but only for the vast majority of FreeBSD users. My interest in improving the docs has been exhausted by perfect standing in the way of better. |
No. The instructions you have provided do not work for the vast majority of FreeBSD users, because they only update the removable media path, which is not what a normal desktop/server installed via bsdinstall will be using. |
FreeBSD 13.0+ no longer have boot1.efifat, so replace those instructions with the relevant commands and add reference to loader.efi man page.