Bug 588328

Summary: cryptsetup-luks-1.1.1-0.1.fc14.x86_64: can no longer mount encrypted USB drive
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: cryptsetup-luksAssignee: Milan Broz <mbroz>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: agk, dwysocha, lvm-team, mbroz, opensource, pjones, prockai, pvrabec, whulbert
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-03 15:42:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error popup showing "exit code 234...." none

Description Tom London 2010-05-03 13:39:43 UTC
Created attachment 410995 [details]
Error popup showing "exit code 234...."

Description of problem:
I have an encrypted LUKS ext4 fs on a USB hard drive that I've been using for backup for quite a while.

Updating to cryptsetup-luks-1.1.1-0.1.fc14.x86_64 breaks mounting this: Firstly, it prompts for my passphrase even though it should be stored in my keyring, and after entering the correct passphrase, I get the attached error popup that says "cryptsetup exited with exit code 234: cannot find compatible device-mapper kernel modules".

I see no messages in /var/log/messages, but I do see this in ~/.xsession-errors:

(gdu-notification-daemon:1992): libgdu-WARNING **: Don't know how to handle device /dev/dm-2

(gdu-notification-daemon:1992): libgdu-WARNING **: Don't know how to handle device /dev/dm-2

(gdu-notification-daemon:1992): libgdu-WARNING **: Couldn't call GetAll() to get properties for /org/freedesktop/UDisks/devices/dm_2d2: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist


(gdu-notification-daemon:1992): libgdu-WARNING **: Don't know how to handle device /dev/dm-2


If I revert to cryptsetup-luks-1.1.0-1.fc13.x86_64, the system will mount my encrypted fs again....

Version-Release number of selected component (if applicable):
cryptsetup-luks-1.1.1-0.1.fc14.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Described above.   Update to cryptsetup-luks-1.1.1-0.1.fc14.x86_64
2. Connect USB LUKS encrypted drive/fs
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Milan Broz 2010-05-03 13:48:00 UTC
Are you sure that downgrading only cryptsetup solves the problem?

Comment 2 Tom London 2010-05-03 13:56:17 UTC
I think so (well, downgraded cryptsetup-luks-libs too):

[root@tlondon ~]# rpm -qa crypt\* udisk\* lvm2\*
udisks-debuginfo-1.0.1-2.fc14.x86_64
cryptsetup-luks-1.1.0-1.fc13.x86_64
cryptsetup-luks-libs-1.1.0-1.fc13.x86_64
lvm2-2.02.64-1.fc14.x86_64
udisks-1.0.1-3.fc14.x86_64
lvm2-libs-2.02.64-1.fc14.x86_64
[root@tlondon ~]#

Comment 3 Tom London 2010-05-03 13:57:12 UTC
Here are device-mapper rpms:

[root@tlondon ~]# rpm -qa device\*
device-mapper-multipath-libs-0.4.9-14.fc13.x86_64
device-mapper-multipath-0.4.9-14.fc13.x86_64
device-mapper-libs-1.02.47-1.fc14.x86_64
device-mapper-1.02.47-1.fc14.x86_64
device-mapper-event-1.02.47-1.fc14.x86_64
device-mapper-event-libs-1.02.47-1.fc14.x86_64
[root@tlondon ~]#

Comment 4 Milan Broz 2010-05-03 14:26:47 UTC
Ok, seems that added module detection broke crypt module autoload, I'll try to fix it somehow.

Comment 5 Milan Broz 2010-05-03 15:42:48 UTC
Fixed upstream, new build for Fedora rawhide is here
http://koji.fedoraproject.org/koji/buildinfo?buildID=170988
Hopefully it gets into repo soon.

Please reopen if there is still problem. 

Thanks for reporting this.