Hi, I just upped my Pi4 running Tumbleweed. As there was also a new kernel, it ran dracut & grub2-install. But that one failed: Output of grub2-branding-openSUSE-84.87.20200106-2.1.noarch.rpm %posttrans script: update-bootloader: 2021-03-24 17:03:25 <3> update-bootloader-7679 run_command.294: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: <<<<<<<<<<<<<<<< target = arm64-efi + /usr/sbin/grub2-install --target=arm64-efi --no-nvram --removable Installing for arm64-efi platform. Use signed file in /usr/share/grub2/arm64-efi/grub.efi for installation. Installation finished. No error reported. + /usr/sbin/grub2-install --target=arm64-efi Installing for arm64-efi platform. Use signed file in /usr/share/grub2/arm64-efi/grub.efi for installation. Could not prepare Boot variable: Read-only file system /usr/sbin/grub2-install: error: efibootmgr failed to register the boot entry: Input/output error. If I manually run efibootmgr I get Pi4:~ # efibootmgr No BootOrder is set; firmware will attempt recovery Should I expect the FW to fix things, or is there something I better do/try now before rebooting the system?
Hello, On Wed, Mar 24, 2021 at 05:16:45PM +0000, Peter Suetterlin wrote:
Hi,
I just upped my Pi4 running Tumbleweed. As there was also a new kernel, it ran dracut & grub2-install. But that one failed:
Output of grub2-branding-openSUSE-84.87.20200106-2.1.noarch.rpm %posttrans script: update-bootloader: 2021-03-24 17:03:25 <3> update-bootloader-7679 run_command.294: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: <<<<<<<<<<<<<<<< target = arm64-efi + /usr/sbin/grub2-install --target=arm64-efi --no-nvram --removable Installing for arm64-efi platform. Use signed file in /usr/share/grub2/arm64-efi/grub.efi for installation. Installation finished. No error reported. + /usr/sbin/grub2-install --target=arm64-efi Installing for arm64-efi platform. Use signed file in /usr/share/grub2/arm64-efi/grub.efi for installation. Could not prepare Boot variable: Read-only file system /usr/sbin/grub2-install: error: efibootmgr failed to register the boot entry: Input/output error.
If I manually run efibootmgr I get
Pi4:~ # efibootmgr No BootOrder is set; firmware will attempt recovery
Should I expect the FW to fix things, or is there something I better do/try now before rebooting the system?
Sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1178247 Since the --no-nvram --removable install was executed your system should still be bootable. Thanks Michal
Peter Suetterlin wrote:
Should I expect the FW to fix things, or is there something I better do/try now before rebooting the system?
So I checked the posttrans scriptlett, and what it does is a /sbin/update-bootloader --refresh I re-ran that command, and checked the output in /var/log/pbl.log. No error message this time :) efibootmgr however still says no BootOrder set, and FW would recover it. :o I crossed fingers, and rebooted. No issues, system is up w/o errors. :D
participants (2)
-
Michal Suchánek -
Peter Suetterlin