Date: Sat, 13 Aug 2022 05:48:41 +0900 (JST) From: Yasuhiro Kimura <yasu@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Updating EFI boot loader results in boot hangup Message-ID: <20220813.054841.1081731685466016992.yasu@FreeBSD.org> In-Reply-To: <CAFDf7UJ2OU4rwhaYD9N%2B9Nx%2BsygG5Y-j9RfZpTNDiVKVNnFhFA@mail.gmail.com> References: <CAFDf7ULYcHfmw4VNroe%2BOECAFo2L4BP3aEtBJwXNcBArYGMq_g@mail.gmail.com> <20220813.024435.741655799390389695.yasu@FreeBSD.org> <CAFDf7UJ2OU4rwhaYD9N%2B9Nx%2BsygG5Y-j9RfZpTNDiVKVNnFhFA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Nuno Teixeira <eduardo@freebsd.org> Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 21:03:02 +0100 > I'm searching without success to load a bkp loader in case of boot failure. > > Upgrade process willl be like: > --- > mount -t msdosfs /dev/nvd0p1 /mnt > cp /mnt/efi/boot/bootx64.efi /mnt/efi/boot/bootx64.old > cp /boot/loader.efi /mnt/efi/boot/bootx64.efi > --- > > I can't find the right docs to load bootx64.old. > Could you tell me what you did to solve your boot? > > Thanks I use VirturalBox to run 14-CURRENT system. UEFI BIOS of VirtualBox provides a way to select loader file and boot from it. So I take following steps when updating loader file. 1. cd /boot/efi/efi/freebsd 2. mv loader.efi loader.backup.efi 3. cp -a /boot/loader.efi . And when boot from new loader file fails, I enter UEFI BIOS, select loader.backup.efi and boot from it. As you can see, above way depends on the feature of VirturalBox. So it depends on your hardware whether or not you can adopt it. As Larry pointed out, surest way is to boot from install media such as memstick or cdrom. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220813.054841.1081731685466016992.yasu>