Cannot boot OpenSUSE Tumbleweed

[sussybro]

I have dual-boot system, Windoze 10 and OpenSUSE Tumbleweed. I use default install with btfs and grub. Today after adding 4 parameters to kernel in YAST right after partition uuid (nvidia nvidia_modeset=1 nvidia_uvm=1 nvidia_drm=1) and after upgrading a system with sudo zypper dup + upgrading flatpaks in KDE Discover I rebooted, and surprisingly it started to boot Windoze. So I tried to select my linux disk from boot menu, and got an error “Reboot and select proper Boot device or insert boot media in selected Boot device and press a key”.
I cannot boot to my linux in any way and I’m exhausted by trying literally everything I could imagine and not getting any results.
What I’ve already tried:

• Reinstalling grub with shim-install (Reinstalling GRUB Bootloader from the Rescue System | Support | SUSE) and manually with commands

grub2-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=opensuse --recheck
grub2-mkconfig -o /boot/grub2/grub.cfg

• using bootrepair and getting error

Please enable a repository containing the [grub2] packages in the software sources of Ubuntu 16.04.1 LTS (sdb8). Then try again

Therefore trying to do that manually as suggested here : Boot repair enable a repository containing grub2 packages - Ask Ubuntu with no success

• using timeshift from bootrepair with no success with error sth like “no subvolume @” i don’t remember exactly
• using snapper crom chrooted env with --no-dbus flag with actual problems:
  1 Failure (org.freedesktop.DBus.Error.ServiceUnknown) · Issue #537 · openSUSE/snapper · GitHub
  2 Cannot rollback using read only snapshot IO ERROR (.snapshots is not a btrfs subvolume). - #6 by arvidjaar
• trying to boot from grub shell that i run by using tumbleweed install medium and selecting boot from hard disk (first option) but I could not find vmlinuz anywhere (I’m not too techie in linux i don’t even know what vmlinuz is + I don’t understand the idea behind btrfs subvolumes)

None of above methodes worked out, I could not get grub to display which is veeeery very weird since reinstalling should make it display. Also, my SSD passed Smart check so it is not broken.

Please at least give me some concept whats wrong, my mind is already blown by this, like…with such problems on Arch it was just the matter of chrooting, removing grub, installing and voila. Thank you in advance

I accidentaly deleted previous topic so I recreate it (btw why there is no confirmation before deletion) with new findings:

• tried using supergrub to boot and after selecting /efi/boot/bootx64.efi or /EFI/boot/bootx64.efi it is stuck at black screen. Selecting /efi/opensuse/grub.efi launches GRUB shell version 2.12. I am still unable to boot the system

[sussybro]

I tried again reinstalling grub with this commands: Grub2 reinstallation from rescue system
No luck. Therefore I checked with Gparted and KDE partition manager on live system, that I have 3 partitions on my ssd:

1. fat32 512MiB with flags boot, esp
2. btrfs no flags
3. swap

So I guess flags are set correctly which is different than what an author of that post encountered. I also did check and repair fat32 partition in gparted there was no error.
Did short self-test smart in gnome disks it completed successfully.

[sussybro]

Great, no one can help? Reinstall is only left option?
I’d prefer not to, configuring everything again, backing up the whole disk, recovering it etc. come on…

[malcolmlewis]

@sussybro and you were using GRUB and not systemd-boot? In the system BIOS is there an option to select a boot menu, in that menu is there openSUSE present?

If you boot from an openSUSE Rescue session (install media(?)) what does the output from efibootmgr -v show?

If nothing, then it should be possible to create a new efi entry for openSUSE with efibootmgr to store into NVRAM, assuming an openSUSE directory is present in /boot/efi.

[sussybro]

In the boot menu there is no opensuse option available, just the disk opensuse is installed on.
efibootmgr -v output shows boot order and some binary data, I don’t know what this data mean though and if its correct:

[sussybro]

I’m still fighting, tried reformatting boot partition and again reinstalling grub, but I see one weird thing. When I remove boot entries for opensuse and reinstall grub it correctly shows the path to grubx64.efi or shim.efi, BUT after restarting and trying to boot it and again going into rescue shell I can see it changes to that weird 2 boot entries “Hard Drive” and “Unknown Device” which is shown on the image I sent in previous reply. No magician could give a hint? I suspect sth might be wrong with initramfs too (while I don’t know what initramfs is actually), but I tried this link:

dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg

and yeah…no result. Also tried doing zypper dup but no success.

[sussybro]

I managed to boot my system finally! I did exactly that:

1. rescue boot
2. cp /boot/efi/EFI/opensuse/grubx64.efi /boot/efi/EFI/boot/bootx64.efi
3. doing grub2-install --removable --target=x86_64-efi --efi-directory=/boot/efi
4. rebooting and selecting localboot in ventoy (F4)
5. selecting find and boot BOOTX64.efi
6. It boots grub rescue shell, where i’ve got error ../../grub-core/kern/disk.c:236:disk ` ,gpt2' not found
7. I used ls to find my btrfs root partition
8. then used commands

set root=(hd1,gpt2)/boot/grub2
insmod normal
normal

Now I need to figure out, why uefi cannot find grubx64.efi or bootx64.efi automatically and I have to use ventoy to find it manually.

[sussybro]

Looks like I fixed the issue but I’m not sure how
Here is a quick summary of what changes exactly I’ve made for future viewers with similar problem:

• Reformatting a boot partition and reinstalling grub and updating /etc/fstab with new EFI partition UUID (blkid)

mkfs.vfat -F32 /dev/sda1
grub2-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=opensuse --recheck
grub2-mkconfig -o /boot/grub2/grub.cfg

• later I have changed /etc/default/grub kernel parameters (GRUB_CMDLINE_LINUX_DEFAULT) to just nomodeset and reran grub2-mkconfig and

grub2-install --removable --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=opensuse

• Also I regenerated initramfs with dracut

dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg

• Finally I managed to boot my system by using method I explained in my previous reply
• after boot I went into YAST → bootloader tab → selected bootloader Not Managed then changed that instantly back to GRUB2 for EFI and checked/unchecked Update NVRAM Entry
• After that I rebooted and was able to see opensuse entry in my boot menu and successfully boot.

I think the key role in fixing the issue played proper chrooting into btrfs system.

Additionally here are some links that helped me fix the issue, so they might help you reading that:

Reinstalling GRUB Bootloader from the Rescue System |...

Grub2 reinstallation from rescue system

Try: First mount your root partition (includes use of cryptsetup) at “/mnt” Then: mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --rbind /sys /mnt/sys chroot /mnt mount -a ### mount everything else needed shim-install exit ### exit from chroot reboot This is for a UEFI install. For non-uefi grub install, you have to use “grub2-install “location” where “location” is the device on which to install grub – typically the MBR (”/dev/sda" or similar) or the device for “/boot”. Not…

Repair a broken UEFI/GRUB2/openSUSE boot scenario

I would like to share the line of action i use to investigate and (hopefully) repair broken UEFI boot scenarios (It may even serve to manually install GRUB2 for UEFI boot). Please be aware: I use openSUSE 42.3 on UEFI-based machines with GRUB2 as bootloader. “secureboot” is always disabled. The UEFI is set to boot in UEFI-mode (no “Compatibility Support Mode (CSM)” aka “Legacy mode” or “MBR mode”). All disks have a GPT partition scheme and ext4 as file system. RAID or LVM are not used. There …

https://wiki.archlinux.org/title/GRUB#Default/fallback_boot_path
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#efibootmgr
https://bbs.archlinux.org/viewtopic.php?id=283707
https://bbs.archlinux.org/viewtopic.php?id=252598

How to recreate EFI boot partition?

regenerate initramfs after moving boot partition

[SOLVED] Common Linux Boot Errors and How to Fix Them

How to boot from GRUB Shell

Boot repair enable a repository containing grub2 packages

booting ends in grub command line with btrfs filesystem...

How to mount a btrfs file system with the mount command?

I have a btrfs file system in a Sabrent USB connected NVMe case. The only way I’ve been able to successfully mount it is with a two command sequence. Is there some way to mount it with just one mount command? Here is the alternate fstab I tried to use with one command. UUID=4c96a0c2-f72f-4827-b023-83ba000b2fd2 / btrfs defaults 0 0 UUID=4c96a0c2-f72f-4827-b023-83ba000b2fd2 /.snapshots btrfs subvol=/@/.snapshots 0 0 UUID=4c…

Cannot rollback using read only snapshot IO ERROR (.snapshots is not a btrfs subvolume).

Hello! I for some reason cannot rollback using a bootable read only snapshot. After I boot in the snapshot and type sudo snapper rollback I get Creating read-only snapshot of default subvolume.IO Error (.snapshots is not a btrfs subvolume). I have a SSD at sda1 with dualboot (using btrfs for / partition) and FAT for the /boot/efi partition and a HDD with my /home partition using ext4. $ sudo fdisk -l Disk /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 sectors Disk model: Samsung SSD 8…

DuckDuckGo AI Chat at DuckDuckGo

And at the end I’d like to honor myself for solving this puzzle and not losing all the patience. Usually if you encounter such issue just go reinstall the OS, quickest and most certain way to make it work, but be careful to do backup of your data on external media before. Also wanted to appreciate every author of mentioned above links, without these I would just end up wasting a lot of time finally reinstalling OS anyway.