Date: Fri, 19 Feb 2021 21:41:21 +0100 From: David Marec <david.marec@lapinbilly.eu> To: Kurt Jaeger <pi@freebsd.org>, Warner Losh <imp@bsdimp.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD 13/stable and zpool upgrade Message-ID: <7c9810fe-6960-0ec7-cab3-2f0c344471f4@lapinbilly.eu> In-Reply-To: <YDACWGA4mLKXiuAb@home.opsec.eu> References: <ac735a6b-b82e-36e4-eb66-d2c0d422cc75@lapinbilly.eu> <CANCZdfrm0dpQ6tyggj-VStTz1zTz8wvqZ35ePn5Dc-o66nC4JQ@mail.gmail.com> <YDACWGA4mLKXiuAb@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 19/02/2021 19:24, Kurt Jaeger wrote: > I suspect that your 'zpool upgrade' enabled things that weren't enabled > before. This caused the old boot blocks to no longer work. Correct. That' s definitely the source of the booting issue. > We should be better about upgrading boot blocks, but EFI is kinda new and > kinda different EFI is able to boot any FreeBSD box for a while. The main issue is that the legacy way to upgrade these /bootcode and partcode/ not only does not work, but do bad things. # gpart bootcode -p /boot/gptzfsboot -i 1 ada0s1 will install an old and inappropriate /partcode/. IMO, 'gptzfsboot' should be sweep off along with 'boot1.efifat' ( by calling 'make delete-old') or be built with the right 'BOOTx64.EFI', which actually is`/boot/loader.efi` . -- David Marec http://wiki.fug-fr.org/doku.php?id=start https://diaspora.lapinbilly.eu/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c9810fe-6960-0ec7-cab3-2f0c344471f4>