I updated my Tumbleweed instance today on my production rig (334 updates) my system has full disk-encrytion set up when installing OS. Filesystem is BTRFS.
The update recommended me to reboot, so I did. when rebooting I get to my grub screen where I have to type in my passphrase to get to the boot login-screen/splash-screen, it opens slot 0 and puts me into grub rescue
I know my passphrase is right.
anyone have any idea how to fix this? or do I have to format and reinstall everything?
I’m not sure I which update it was but I’m guessing it was the latest (20240105) because it just poped up on my notification about 40 min agou. when I saw it I did as I always do when I’m not doing anything work related, I ran zdup
I was not aware of that. but here is the screen info.
I still have it it boots up to Fedora and openSUSE installer. I agree that slot 0 open indicates that pwd is correct, because that’s what it says every time I have logged into the computer.
I have never really done anything with grub, I don’t know what info you would need or how to get it but if you know, I’d be happy to post it.
Boot the installer to the rescue system. Login there as root.
Open your root file system with:
cryptsetup luksopen /dev/sdX cr_root
(change that /dev/sdX to the correct name for the partition).
Then mount your root file system at “/mnt”.
Then use the commands:
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --rbind /sys /mnt/sys
Note any errors that you see.
Next:
chroot /mnt
mount -a
This should leave you in your system at a command prompt.
You can then try:
update-bootloader --reinit
I’m guessing that there will be error messages along the way. Report them here. If there are no error messages, you could try rebooting and see if the problem has been fixed.
^^^ this command does not work.
I’ve tried these:
- cryptsetup luksopen /dev/nvme0n1/cr_root
- cryptsetup luksopen /dev/nvme0n1p1(2,3,4)/cr_root
- cryptsetup luksopen /dev/mapper/cr_root (what it is in fstab)
- cryptsetup luksopen /dev/nvme0n1 cr_root
no luck it give me an error saying; cryptsetup; unknown action
this is what my lsblk -pf output gives me.
When booting in with rescue-system and logging in using “root” as username and which brings me into tty1, then to become root.
any thoughts?
Oops, my mistake. It should be “luksOpen”.
Try:
cryptsetup luksOpen /dev/nvme0n1p2 cr_root
except that instead of that “p2” you might need “p3” or “p4”
Perhaps you need all of them. But you cannot call them all “cr_root”. So maybe use “cr_auto1”, “cr_auto2” and “cr_auto3”. And you may need to experiment to see which is the root file system.
To experiment, you try mounting with something like
mount /dev/mapper/cr_auto1 /mnt
and then look at “/mnt” to see if it looks like a root file system (has directories “usr”, “etc”, “opt”.
If not, umount that one and try the next.
When you find the correct one, try:
cat /mnt/etc/os-release
cat /mnt/etc/fstab
and post the output here. That will give us a better idea how to proceed.
None of the mount --(r)bind commands or chroot /mnt gave me any errors.
but mount -a gave me error messages on all subvolumes (see the picture below)
and that is probably because I have not mounted the /home (partition/subvolume)
Thank you so much for your help! at first that did not fix it either. I got the same slot 0 open -rescue
and nothing more, so I decided to try your steps again to see if I missed anything.
and something caught my eye when I re-ran lsblk -pf
now all of a sudden my openSUSE nvme drive was no longer nvme"0"n1p(X)
but, nvme"1"n1p(X) ,
but I still finished doing your steps. and again it did not boot. so I decided to go into the bios of my MSI x570 Unify MB and look at the boot order.
I have had to use openSUSE secureboot to be able to log in (dont konw why) but all of a sudden now openSUSE sabrent4p was set as #1.
I changed it back to #1 being openSUSE secureboot and now it works like before, like nothing has happened.
I truly do not know why my boot-order changed when I upgraded to the latest image today! but I’m truly thank full for your help and what I have learned, because I’m really like openSUSE TW and the non arrogant community around it.
For future reference remember it. I have an ASUS board that does much the same. Mine is set to default to my Windows drive, to hide my Linux install from unwanted guests. I use F8 during post to choose boot device manually to get to Linux. I use Windows bootloader for Windows and grub for Linux, each on it’s own drive. Occasionally my board will ignore my boot order and boot to grub. I typically check BIOS before anything else when there are issues.
