![](https://seccdn.libravatar.org/avatar/aaff612bb0750768db78818737bfbdb6.jpg?s=120&d=mm&r=g)
On Thu, 15 Oct 2020 10:55:10 -0500 Ralph wrote:
On Wed, 14 Oct 2020 20:42:53 +0300 Andrei Borzenkov wrote:
14.10.2020 14:39, Ralph пишет:
Some strangeness in a fresh install of Leap 15.2 on a system with multiple LUKS partitions mounted at boot, all owning the same password.
Normal boot and plymouth(?) displays a neon green text line on a blank background asking for the LUKS password for swap. After entering pw, plymouth(?) then displays three neon green blocks for several seconds. Remaining three LUKS partitions are invisibly mounted without further prompting and system boots into graphical mode.
Boot with plymouth.enable=0 and I get the text display, as expected and usual in previous revs, but then I get prompted for passwords for all 4 partitions, even though they all have the same password. This used to be buffered and pw retried on additional partitions first before system would ask for any needed additional pw. Not now, apparently.
I cannot reproduce it. I create two encrypted partitions with the same passphrase and I'm asked just once. Systemd should actually cache passphrase in kernel keyring for short period of time. How long is interval between password requests?
You may want to boot with systemd.log_level=debug which /may/ provide more information what happens.
Thank you very much for taking the time to try to reproduce the problem. More confirmation that it SHOULD be working, which means something particular to me is messed up. At the moment I have no idea what it might be.
Interval between pw requests is just from time boot asks for pw for encrypted swap to check for hibernated system and time it mounts encrypted /home and additional LUKS partitions, looks like max 2 clock seconds during a 'normal' boot. I don't have a log from booting with plymouth.enable=0, thanks to default openSUSE setting of logs going to non-permanent storage, but I've fixed that and will get a log at next opportunity to boot.
I will try your log suggestion at next reboot.
I have not had time to dig back into this, but I did need to reboot for something else day or two ago so I have a log on a boot using plymouth.enable=0 (but without your suggested systemd.log_level=debug as email was out at that moment) and I got the following in the log... systemd-tty-ask-password-agent[881]: Invalid password file /run/systemd/ask-password/ask.FjjVli systemd-tty-ask-password-agent[881]: Failed to show password: Bad message ...which looks mighty similar to a problem we had with multi-LUKS a few years ago. I will need to dig up the discussion and the bugzilla from back then and see if it's the same. Ralph -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org