Date: Sun, 18 Jul 2021 23:50:13 +0000 From: Thomas Laus <lausts@acm.org> To: freebsd-current@freebsd.org Subject: Re: EFI boot partition overwritten: mount -t msdosfs (or mount_msdosfs(8)) Message-ID: <0100017abc06ffdd-9d095532-19fd-4fd9-a034-2d3708a90fb7-000000@email.amazonses.com> In-Reply-To: <8400d4f1-0c39-c5f6-ed37-12d6fb78f7c8@gmail.com> References: <0100017aaf3bd028-56a36bdb-37e1-4d14-9d10-4ff2367110d4-000000@email.amazonses.com> <CANCZdfqKcXrkc=aK=ck1yjgGjNPnKZjQwOV5TopEdLTjxGi%2BdQ@mail.gmail.com> <8400d4f1-0c39-c5f6-ed37-12d6fb78f7c8@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/18/21 2:21 PM, Graham Perrin wrote: > On 16/07/2021 18:35, Warner Losh wrote: >> # newfs_msdos -F 32 /dev/ada0p4 >> # mount -t msdos /dev/ada0p4 /boot/efi > > > Typo: msdosfs, not msdos. > > Alternatively, mount_msdosfs(8). > > Alternatively (I agree, even better), incorporate things such as this in > the Handbook :-) > > Then have the (ahem) book of answers to frequently asked questions link > to the Handbook. > I agree with having this information in the Handbook. Writing the contents of the EFI partition has changed filenames through the recent release cycles. FreeBSD 12.0 + uses "dd(1) the /boot/boot1.efifat file". FreeBSD 13.0 has a gptboot.efi in the /boot directory I was tempted to use 'gpart bootcode -p /boot/gptboot.efi' like writing the boot record on a ZFS system but was concerned about digging a bigger hole. Warner Losh has still another way of writing the EFI partition contents. Once the Handbook defines a 'standard' method, the /usr/src/UPDATING file can just reference it. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0100017abc06ffdd-9d095532-19fd-4fd9-a034-2d3708a90fb7-000000>