Bug 1255965

Summary:	encrypted LVM with root: "failed to start cryptography setup for luks" with kernel 4.1.5-200.fc22.x86_64
Product:	[Fedora] Fedora	Reporter:	AceSlash <slash>
Component:	cryptsetup	Assignee:	Milan Broz <gmazyland>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	agk, gmazyland, okozina, slash
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-25 12:20:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description AceSlash 2015-08-22 13:03:20 UTC

Description of problem:

After entering the passphrase for my LUKS encrypted partition with the kernel 4.1.5-200.fc22.x86_64 the following message appears after the password has been validated:

Failed to start cryptography setup for luks....

Selecting the kernel 4.1.4-200.fc22.x86_64 on the Grub menu doesn't trigger the issue.

How reproducible:

Install Fedora with 2 partitions, one for boot and the other with an encrypted LVM volume containing the root partition. Validate that you can decrypt and boot normally. Update Fedora with the kernel "4.1.5-200.fc22.x86_64", you'll get the error message.


Actual results:

Cannot decrypt the LUKS volume.


Expected results:

Decrypt the LUKS volume.

Comment 1 Milan Broz 2015-08-24 07:25:10 UTC

Could you please post lsinitrd for both initramfs?

It seems like some kernel module is missing there but I am not able reproduce it.
(That message means that some crypto backend cannot be initialized so LUKS fail is just consequence of it.)

Clean install from netboot iso install with that kernel and luks is properly unlocked here.

Comment 2 Milan Broz 2015-08-24 11:38:49 UTC

I just tried clean minimal encrypted install from DVD and then update only kernel with mentioned version - everything works. So something is nonstandard in your system.
LUKS parameters or storage config? lsblk and cryptsetup luksDump can help to check it.

Comment 3 AceSlash 2015-08-25 12:20:57 UTC

I tried to reproduce it today but was not able to, the system opened the encrypted volume as expected with the kernel 4.1.5-200.fc22.x86_64.

I'm not sure of what changed since last time. I think the ticket can be closed, I'll reopen it if I am able to reproduce.

In case we need it, bellow are the first lines of the luksdump:
LUKS header information for /dev/sda2

Version:        1
Cipher name:    aes
Cipher mode:    xts-plain64
Hash spec:      sha1
Payload offset: 4096

Comment 4 Milan Broz 2015-08-25 12:31:42 UTC

ok, thanks.

LUKS parameters are default (as used in Anaconda installer) so it should not be a problem.