On Tue, Oct 10, 2023 at 1:50 PM Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 09.10.23 um 16:38 schrieb Andrei Borzenkov:
Windows bootloader is not in the list of boot options. Which is rather unusual (especially after Windows update that apparently updated the bootloader).
Boot001F* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Educated guess - it has always been this way, you just did not notice it. The NVMe boot entry most likely loads \EFI\Boot\bootx64.efi which was overwritten by Windows update. Prove output of
ls -lR /boot/efi
(after mounting it in live linux).
Your openSUSE bootloader was removed
./EFI/opensuse: total 0
So you need to reinstall it.
Tried it pretty much like described here: https://en.opensuse.org/SDB:BTRFS#How_to_manually_re-install_grub_on_opensus...
1. It does not mention /boot/efi which should be mounted on /mnt/my-root/boot/efi 2. It does not mention /sys/firmware/efi/efivars which should be bind-mounted on /mnt/my-root/sys/firmware/efi/efivars (or /sys should be mounted with --rbind option instead of --bind) Both are needed to successfully install bootloader on EFI. 3. grub2-install is *NOT* an alternative to the "update-bootloader --reinit", it is wrong
But not only ran update-bootloader but also ran yast2 bootloader where settings looked about right and confirmed it.
Now there is EFI/opensuse/grub/grubx64.efi (only that)
I have no idea where it comes from. But if you did not have the mounts in 1 and 2, it could not succeed anyway. But show grep -Ev '^$|^#' /etc/sysconfig/bootloader
But I still cannot boot from there.
I am confused. Previously in this thread you said the problem was fixed?
What else to do in addition to "reinstall the bootloader"?
Thanks, Wolfgang