Bugzilla – Bug 1169891
Cannot unlock encrypted partitions; system unbootable
Last modified: 2020-04-20 14:23:21 UTC
Created attachment 836113 [details] Output of 'journal -xb' Hi! Since updating Tumbleweed to 2020-04-14 my systems with encrypted home directory fail to boot. At some point during the boot, I'd have to enter the home partition's password, but that prompt is never shown. I think it's there, it just doesn't get the console. From the journal, (attached) I think it is related to systemd-vconsole-setup failing. I'm currently able to work around the problem with the following commands: 1) <wait for systemd repair mode prompt> 2) manually run vconsole-setup with 'systemctl start systemd-vconsole-setup' 3) enter password for home partition 4) continue regular boot with 'systemctl default' After entering that sequence, the regular boot continues as expected. Not a long-term solution, of course. Alternatively to step 2, I can also do 2') manually mount /home with 'systemctl start home.mount' Updating to Tumbleweed 2020-04-16 did not solve the problems.
I suspect this bug could be baused by a recent update of plymouth from 0.9.5+git20190908+3abfab2 to 0.9.5+git20191224+d7c737d
s/baused/caused
Duplicate of #1169783 *** This bug has been marked as a duplicate of bug 1169783 ***