Bug 2037434

Summary:	"No key available with this passphrase." after package update
Product:	[Fedora] Fedora	Reporter:	Marcin Juszkiewicz <mjuszkie>
Component:	cryptsetup	Assignee:	Milan Broz <gmazyland>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	35	CC:	agk, gmazyland, okozina
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-05 16:30:24 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 Marcin Juszkiewicz 2022-01-05 16:11:01 UTC

Description of problem:

I use Fedora 35 and did small system update today (2.1GB of packages). After reboot to 5.15.12 kernel system was unable to mount my Luks encrypted /home filesystem.

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

2.4.2-1.fc35

How reproducible:

always

Steps to Reproduce:
1. boot system
2. cryptsetup open /dev/nvme1n1p1 fedora-home


Actual results:

[root@puchatek /]# cryptsetup open /dev/nvme1n1p1 fedora-home
Enter passphrase for /dev/nvme1n1p1: 
No key available with this passphrase.
Enter passphrase for /dev/nvme1n1p1: 

Expected results:

[root@puchatek /]# cryptsetup open /dev/nvme1n1p1 fedora-home
Enter passphrase for /dev/nvme1n1p1: 
[root@puchatek /]# 

And opened partition.

Additional info:

Comment 1 Marcin Juszkiewicz 2022-01-05 16:30:24 UTC

Turned out that MSI firmware was to blame - reverted to old one and it works again.

Argh.

Comment 2 Milan Broz 2022-01-05 16:32:15 UTC

Hm, that's interesting (usually it is wrong keyboard setting :)

Comment 3 Marcin Juszkiewicz 2022-01-05 16:57:36 UTC

I checked also:

echo "passphrase" | cryptsetup open /dev/nvme1n1p1 fedora-home

And it was wrong too.

This system will not get firmware update anymore from me. Vendor is not capable of writing working one.