Looks like I fixed the issue but I’m not sure how
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:
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…
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
linux, boot, grub2, uefi
linux, initramfs-tools
Linux boot problems got you down? This guide explores common issues like blank screens, missing GRUB menus, kernel panics, and file system errors. Learn how to troubleshoot and conquer them all!
linux, grub, linux-mint
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…
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…
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.
1 Like
