Bug 21455 - kernel fails unlock multiple LUKS encrypted partitions at boot (Regression)
Summary: kernel fails unlock multiple LUKS encrypted partitions at boot (Regression)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-05 17:09 CEST by Michael Riss
Modified: 2020-08-02 22:28 CEST (History)
2 users (show)

See Also:
Source RPM: kernel-4.9.40-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Michael Riss 2017-08-05 17:09:57 CEST
Description of problem:
On a system with encrypted "/"- and "/home"-partitions the kernel hangs at boot.
The previous kernel 4.9.35-1 did ask once for a password to unlock the LUKS
encrypted partitions and then tried to unlock all encrypted partitions with
this password. This allowed you to e.g. install "/" on a SSD and "/home" on a HDD and have both encrypted with the same password. 
The new kernel seems to use the entered password only for the first partition to unlock and then hangs when trying to unlock the second partition.

Version-Release number of selected component (if applicable):
kernel-4.9.40-1

How reproducible:

Steps to Reproduce:
1. Install a system with separate, encrypted partitions for "/" and "/home".
2. Try to boot.

Workaround:
You can edit the kernel command line in grub and erase the "quiet" and "splash" keywords, so that the kernel boots in text mode. This gives you access to the 
second LUKS "unlock" password request. This way you can enter the password also for the second partition and the system boots up.
Manuel Hiebel 2017-08-05 19:53:39 CEST

Assignee: bugsquad => basesystem

Manuel Hiebel 2017-08-05 19:59:25 CEST

CC: (none) => kernel

Comment 1 Aurelien Oudelet 2020-08-02 22:28:39 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.