As the title said today I updated my TumbleWeed PC on KDE discover. Then after the download was finished I reboot my PC then type my password on Grub, then to my Encrypted swap partition, then lastly my encrypted home partition, and updated my system. After my system finished updating it restarted again and boot. Then cycle begin again type my Grub password, then see my bootloader (by the way currently I’m on kernel version is 6.11.7.1 default) after the countdown finished it showed my latest kernel version it’s on 6.11.8.1 default and after that my problem show up. After the bootloader it will show first I need to type my password for my Swap Partition and then Home Partition (both Encrypted though). My Problem is I can’t get through on my Swap partition because it always put me back on typing my password on my Swap partition again and again until it won’t let me type again and it will said: “Failed to Start Cryptography Setup for cr_swap” and “Dependency failed for Local Encrypted Volumes” at that point I need to restart again. And I know some of you might said: “Maybe ya type ya password wrong, etc.” trust me I didn’t not type my password wrong and I did this process 4 times and those 4 attempts the same problem and prompts show up. So I use snapper to go back at my system previous state and what do you know after typing my grub password and get into prompt where I need to type my password on Swap partition it was alright and after that it was smooth sailing. Now my question is why this happened and what it caused it? Does Tumbleweed change my keyboard layout when got to typing my swap partition if so if I manage to guess my swap partition for some miracle my home partition will be my next headache. My guess is after the kernel load it change my keyboard layout to something else and since I can’t see letters when I type my password there’s no way to know if my guess was right. But one thing for certain the new update on tumbleweed causing me a problem and I guess I’ll stick on my current version until someone explained why this happened and show a way to fix this or an update that will fix this issue.
How should we know? Unpack initrd of the “bad” kernel and check /etc/vconsole.conf.
If you are using plymouth, try booting with plymouth.enable=0 to get pure text based password prompt.
At that point you should be left in dracut emergency shell and dracut should have generated /run/initramfs/rdsosreport.txt. This file may give some clues to what happens.
If you are using plymouth, try booting with plymouth.enable=0 to get pure text based password prompt.
Did this and yup I was right and wrong. Right cuz I was typing my password correctly and Wrong because my guess of the Kernel somehow changing my keyboard layout is wrong. But the problem is I can’t still pass through the Swap Partition.
This command was not supposed to print anything. This command was supposed to unpack initrd into the current directory. Did you try to read the man page?
After unpacking there should be file etc/vconsole.conf in the current directory. But you already said, that you checked the keyboard layout and it was correct. And you still did not explain whether swap is unlocked in initrd or in the real root.
And you still did not explain whether swap is unlocked in initrd or in the real root.
It seem when I try to enter my password on prompt when I reboot my pc my system (or the tumbleweed) doesn’t seem like unlocking the swap partition at all and after 3 attempts it just show Failed to Start Cryptography Setup for cr_swap” and “Dependency failed for Local Encrypted Volumes”
OK, what happens after that? dracut should wait for several minutes and then timeout and drop you into emergency shell. Full system should do the same. Did you wait long enough?
Booting without quiet on the kernel command line may show more information.
Nothing sir. I waited I guess 10 to 15 minutes since I cook some breakfast for me self. And after the two prompt "Failed to Start Cryptography Setup for cr_swap” and “Dependency failed for Local Encrypted Volumes” nothing. Just those two prompt.
Similar problem here after today’s (huge) update. I can’t see any boot message by pressing Esc after started booting.
Get prompted for /home encrypted password three times (password is OK) and I see under password text box a keyboard symbol with Spanish under It, which I can’t access by pressing Tab (shows * in password box) and have no mouse pointer visible/available.
My Guess is system isn’t using Spanish when typing the password.
System gives error decrypting /home so when I get to login screen and type user password can’t login because there is no /home partition available.
As root, created a new user, logged in Plasma/Wayland and launched GNOME Disks to find out what was the encrypted partition and if I could decrypt and mount it. Succeeded, so I rebooted.
On boot I enter the right decryption password the three times the system asks because it doesn’t recognize it (might as well type anything), system continues booting and when I get to graphical login screen I switch to tty1, log in as root and execute the following commands:
cryptsetup luksOpen /dev/sda4 cr_home (asks for encryption password and decrypts it)
mount -a
Now I have /home mounted and I can go to graphical screen and log in as my user.
Yes the /etc/default/grub config don’t have quite. I’ll try again today since Tumbleweed got new snapshot update. Hope this update fix the problem. And it seem some of the users getting this problem as well after they updated their system.
