doc(ZFS): update UEFI loader instructions for 13+ #408
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1335,11 +1335,13 @@ For systems using EFI to boot, execute the following command: | |
|
|
||
| [source,shell] | ||
| .... | ||
| # 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.efi |
||
| # umount /boot/efi | ||
| .... | ||
|
|
||
| Apply the bootcode to all bootable disks in the pool. | ||
| See man:gpart[8] and man:loader.efi[8] for more information. | ||
| ==== | ||
|
|
||
| [[zfs-zpool-history]] | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this?