Bug 2037434 - "No key available with this passphrase." after package update
Summary: "No key available with this passphrase." after package update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptsetup
Version: 35
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Milan Broz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-05 16:11 UTC by Marcin Juszkiewicz
Modified: 2022-01-05 16:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-05 16:30:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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