Hi, every once in a while I have boot issues with my dual boot laptop where Windows 11 and Tumbleweed are installed. Just today I booted Windows (which does not happen very often but sometimes I need to) and had to install a bunch of updates. Now I cannot boot to TW anymore. So something must have destroyed the boot. When I open the BIOS during boot I still have the entry opensuse-secureboot available but selecting it just brings me back to the same selection so apparently something is broken there. What is the correct way to recover that and can I avoid this somehow? Thanks, Wolfgang
On 2023-10-08 20:31, Wolfgang Rosenauer wrote:
Hi,
every once in a while I have boot issues with my dual boot laptop where Windows 11 and Tumbleweed are installed.
Just today I booted Windows (which does not happen very often but sometimes I need to) and had to install a bunch of updates. Now I cannot boot to TW anymore. So something must have destroyed the boot. When I open the BIOS during boot I still have the entry opensuse-secureboot available but selecting it just brings me back to the same selection so apparently something is broken there.
What is the correct way to recover that and can I avoid this somehow?
The first doubt is whether it is a classical BIOS or a modern UEFI. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 08.10.2023 21:54, Carlos E. R. wrote:
On 2023-10-08 20:31, Wolfgang Rosenauer wrote:
Hi,
every once in a while I have boot issues with my dual boot laptop where Windows 11 and Tumbleweed are installed.
Just today I booted Windows (which does not happen very often but sometimes I need to) and had to install a bunch of updates. Now I cannot boot to TW anymore. So something must have destroyed the boot. When I open the BIOS during boot I still have the entry opensuse-secureboot available but selecting it just brings me back to the same selection so apparently something is broken there.
What is the correct way to recover that and can I avoid this somehow?
The first doubt is whether it is a classical BIOS or a modern UEFI.
Windows 11 does not (officially) support legacy BIOS at all.
Boot from installation usb or dvd, from the menu, choose "boot installed system" ()you may be asked for root partition), use yast to restore the boot loader. Regards, Francesco
Am 09.10.23 um 09:13 schrieb Francesco Teodori:
Boot from installation usb or dvd, from the menu, choose "boot installed system" ()you may be asked for root partition), use yast to restore the boot loader.
does not work. Booting from a TW stick and selecting "Boot Linux system" (as there is not "boot installed system" I need to select the root partition and the kernel image before the screen gets black and nothing happens at all. I'm now in the rescue system but I'm unsure what I need to mount, chroot, mount within the chroot and so on to actually restore the bootloader. Wolfgang
Wolfgang Rosenauer composed on 2023-10-09 09:54 (UTC+0200):
does not work. Booting from a TW stick and selecting "Boot Linux system" (as there is not "boot installed system" I need to select the root partition and the kernel image before the screen gets black and nothing happens at all.
I'm now in the rescue system but I'm unsure what I need to mount, chroot, mount within the chroot and so on to actually restore the bootloader.
https://en.opensuse.org/SDB:BTRFS seems may cover what you need to know, mainly way down the page. https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch... may also be helpful. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-10-09 09:54, Wolfgang Rosenauer wrote:
Am 09.10.23 um 09:13 schrieb Francesco Teodori:
Boot from installation usb or dvd, from the menu, choose "boot installed system" ()you may be asked for root partition), use yast to restore the boot loader.
does not work. Booting from a TW stick and selecting "Boot Linux system" (as there is not "boot installed system" I need to select the root partition and the kernel image before the screen gets black and nothing happens at all.
I'm now in the rescue system but I'm unsure what I need to mount, chroot, mount within the chroot and so on to actually restore the bootloader.
Andrei asked you to post some information exactly at that point before attempting any restoration. Mount the hard disk Tw partition somewhere, mount its boot, then tree /somewhere/EFI efibootmgr -v -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 08.10.2023 21:31, Wolfgang Rosenauer wrote:
Hi,
every once in a while I have boot issues with my dual boot laptop where Windows 11 and Tumbleweed are installed.
Just today I booted Windows (which does not happen very often but sometimes I need to) and had to install a bunch of updates. Now I cannot boot to TW anymore. So something must have destroyed the boot. When I open the BIOS during boot I still have the entry opensuse-secureboot available but selecting it just brings me back to the same selection so apparently something is broken there.
Are there any errors or other messages when you try to start opensuse-secureboot? Does your BIOS support "boot from file"? If yes, can you try selecting \EFI\opensuse\shim.efi manually? Is \EFI\opensuse still present? What is the content? Boot any live linux, post full output of "efibootmgr -v".
What is the correct way to recover
Without understanding why it fails recovering is difficult.
that and can I avoid this somehow?
Thanks, Wolfgang
Hi, sorry for my double post. Somehow when I write to users@ my mailfilter broke things so thought that my message didn't come through. (and this one might be not threaded correctly)
Are there any errors or other messages when you try to start opensuse-secureboot? Does your BIOS support "boot from file"? If yes, can you try selecting \EFI\opensuse\shim.efi manually?
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options: opensuse-secureboot NVMe0 .... (which boots Windows) There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far. Wolfgang
Am 08.10.23 um 23:45 schrieb Wolfgang Rosenauer:
Hi,
sorry for my double post. Somehow when I write to users@ my mailfilter broke things so thought that my message didn't come through.
(and this one might be not threaded correctly)
Are there any errors or other messages when you try to start opensuse-secureboot? Does your BIOS support "boot from file"? If yes, can you try selecting \EFI\opensuse\shim.efi manually?
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options:
opensuse-secureboot NVMe0 .... (which boots Windows)
There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
it is present and it is empty.
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far.
On Mon, Oct 9, 2023 at 2:20 PM Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 08.10.23 um 23:45 schrieb Wolfgang Rosenauer:
Hi,
sorry for my double post. Somehow when I write to users@ my mailfilter broke things so thought that my message didn't come through.
(and this one might be not threaded correctly)
Are there any errors or other messages when you try to start opensuse-secureboot? Does your BIOS support "boot from file"? If yes, can you try selecting \EFI\opensuse\shim.efi manually?
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options:
opensuse-secureboot NVMe0 .... (which boots Windows)
There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
it is present and it is empty.
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far.
Somewhat interesting BootOrder: 0000,001D,001E,001F,0020,0021,0022,0023,0024,0025 Boot0000* opensuse-secureboot HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\opensuse\shim.efi) Boot0001* Windows Boot Manager HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi) 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).
Am 09.10.23 um 13:40 schrieb Andrei Borzenkov:
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options:
opensuse-secureboot NVMe0 .... (which boots Windows)
There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
it is present and it is empty.
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far.
Somewhat interesting
BootOrder: 0000,001D,001E,001F,0020,0021,0022,0023,0024,0025 Boot0000* opensuse-secureboot HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\opensuse\shim.efi) Boot0001* Windows Boot Manager HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)
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).
https://paste.opensuse.org/pastes/6d188dbf24b4 Ok, I'm not sure I understand all of the above as my boot knowledge is from the pre-EFI era mainly. Currently when I boot the system it immediately starts to boot Windows (no grub menu). When I stop the boot process and open the boot device selection via F12 I get offered two possibilities (which always was the case): opensuse-secureboot NVMe... The latter always booted Windows directly. The first always brought up the grub boot menu. Until yesterday. (Windows is also part of the grub menu but I could never boot from there as Bitlocker was/is unhappy about that order.) When and what was loaded when, sorry, I have no idea. It more or less worked until yesterday and since this happened now the second time within a few months I try to find a better solution. Next I'll try is to reinstall grub/bootloader as suggested in another part of the thread. Wolfgang
Op maandag 9 oktober 2023 13:53:24 CEST schreef Wolfgang Rosenauer: Hi Wolfgang, I would use the media, or a new version of it, you started to install TW on this system. In the menu where you can install TW you can choose to update a current version. Just use that option. -- fr.gr. member openSUSE Freek de Kruijf
On Mon, Oct 9, 2023 at 5:21 PM Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 09.10.23 um 13:40 schrieb Andrei Borzenkov:
I cannot find an option to boot from file. It's a rather new Lenovo Thinkpad with a graphical boot menu containing two options:
opensuse-secureboot NVMe0 .... (which boots Windows)
There is no error visible. After selecting opensuse-secureboot there is a black screen for a second just to go back to the boot menu.
Is \EFI\opensuse still present? What is the content?
it is present and it is empty.
Boot any live linux, post full output of "efibootmgr -v".
Will do so tomorrow and come back. First need to create a USB storage with a TW image and it's getting late here. Thanks for the feedback so far.
Somewhat interesting
BootOrder: 0000,001D,001E,001F,0020,0021,0022,0023,0024,0025 Boot0000* opensuse-secureboot HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\opensuse\shim.efi) Boot0001* Windows Boot Manager HD(1,GPT,f2809dd7-02ba-4b21-a014-a411e8bf0b91,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)
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.
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... 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) But I still cannot boot from there. What else to do in addition to "reinstall the bootloader"? Thanks, Wolfgang
On 2023-10-09 16:53, Wolfgang Rosenauer wrote:
Am 09.10.23 um 16:38 schrieb Andrei Borzenkov:
...
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...
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)
But I still cannot boot from there.
What else to do in addition to "reinstall the bootloader"?
What I do is: I start the same as in that web page, except that as I don't use btrfs it is far easier. When I get to the section in "Change root and install grub", do that chroot, then: Edit in /etc/default/grub the line GRUB_DISTRIBUTOR=... and write something appropriate that is not "opensuse". For instance: GRUB_DISTRIBUTOR=Tumbleweed I have GRUB_DISTRIBUTOR=opensuse_main (I had trouble with "-" and uppercases) Run grub2-mkconfig -o /boot/grub2/grub.cfg Notice that not all chars are valid, it depends on the BIOS. No knowing which are invalid. Tell tale are boot problems, or that the name doesn't appear after booting in command "efibootmgr" after booting. This name will appear as tittle in the Grub menu. The purpose of this is that openSUSE uses always the same name for all installations and the overwrite one another. This name will also be the name of the directory in /boot/efi/EFI/whatever. So if something overwrites "opensuse", your boot will no longer be there, but in some other directory. If you have multiboot with openSUSE, this is crucial. Second step start yast in _text_ mode (call "yast" in xterm, konsole, etc). Go to "System"/"Boot Loader" Check that all things look correct, then on tab "Bootloader Options" change the timeout one second up or down. The side effect of this tiny change is that all files are written to destination on accept. Cross your fingers, light a candle, burn some scented pasta while you dance three times, accept and reboot. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
Am 09.10.23 um 18:12 schrieb Carlos E. R.:
What I do is:
I start the same as in that web page, except that as I don't use btrfs it is far easier. When I get to the section in "Change root and install grub", do that chroot, then:
Just booted the rescue system and noticed a hint before the login prompt to use the tool mount-rootfs-and-do-chroot That one with the root fs as parameter prepares almost everything and chroots directly. Another mount -a later I was ready to work in the installed system.
Second step
start yast in _text_ mode (call "yast" in xterm, konsole, etc). Go to "System"/"Boot Loader"
Check that all things look correct, then on tab "Bootloader Options" change the timeout one second up or down. The side effect of this tiny change is that all files are written to destination on accept.
did this - changed a tiny thing - and saved. And finally: My bootloader is back! Thanks to everyone for the pointers. So I would expect that this happens for everyone else running Windows 11 that it wipes the opensuse boot stuff when doing some sort of update once in a while? I'm wondering why I haven't found multiple references to such a problem? Wolfgang
On 2023-10-09 19:14, Wolfgang Rosenauer wrote:
Am 09.10.23 um 18:12 schrieb Carlos E. R.:
What I do is:
I start the same as in that web page, except that as I don't use btrfs it is far easier. When I get to the section in "Change root and install grub", do that chroot, then:
Just booted the rescue system and noticed a hint before the login prompt to use the tool mount-rootfs-and-do-chroot
That one with the root fs as parameter prepares almost everything and chroots directly. Another mount -a later I was ready to work in the installed system.
Second step
start yast in _text_ mode (call "yast" in xterm, konsole, etc). Go to "System"/"Boot Loader"
Check that all things look correct, then on tab "Bootloader Options" change the timeout one second up or down. The side effect of this tiny change is that all files are written to destination on accept.
did this - changed a tiny thing - and saved.
And finally: My bootloader is back! Thanks to everyone for the pointers.
So I would expect that this happens for everyone else running Windows 11 that it wipes the opensuse boot stuff when doing some sort of update once in a while?
I'm wondering why I haven't found multiple references to such a problem?
Because no, it doesn't happen to many people. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
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
Am 10.10.23 um 13:10 schrieb Andrei Borzenkov:
But I still cannot boot from there.
I am confused. Previously in this thread you said the problem was fixed?
I assume the mails arrived for you in the wrong order because yes, I said it's fixed and in the same mail I explained what I did. And I wrote it after the one you replied to now. Wolfgang
On 10.10.2023 14:39, Wolfgang Rosenauer wrote:
Am 10.10.23 um 13:10 schrieb Andrei Borzenkov:
But I still cannot boot from there.
I am confused. Previously in this thread you said the problem was fixed?
I assume the mails arrived for you in the wrong order because yes, I
I guess it did because currently I received a lot of the old mail.
said it's fixed and in the same mail I explained what I did.
And I wrote it after the one you replied to now.
Wolfgang
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Francesco Teodori -
Freek de Kruijf -
Wolfgang Rosenauer