Bug 804365 - cryptsetup luksFormat fails "device-mapper: table: 253:0: crypt: unknown target type"
Summary: cryptsetup luksFormat fails "device-mapper: table: 253:0: crypt: unknown targ...
Keywords:
Status: CLOSED DUPLICATE of bug 804345
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptsetup-luks
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-18 09:28 UTC by Richard W.M. Jones
Modified: 2012-03-18 10:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-18 10:32:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2012-03-18 09:28:51 UTC
Description of problem:

This just started to happen in Rawhide (as in, it didn't
happen two days ago).  I'm not sure if it's a kernel or
LUKS problem.

# parted -s -- /dev/vda mklabel msdos mkpart primary 128s -128s
# cryptsetup -q --key-slot 0 luksFormat /dev/vda1 /tmp/luksykr7fm
[   56.250443] device-mapper: table: 253:0: crypt: unknown target type
[   56.250879] device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl on temporary-cryptsetup-110 failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/vda1.
Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info).
Failed to write to key storage.

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

kernel-3.3.0-0.rc7.git2.1.fc18
cryptsetup-libs-1.4.1-2.fc17
device-mapper-libs-1.02.74-3.fc18.x86_64

How reproducible:

Unknown, at least once.

Steps to Reproduce:

[see above]

Additional info:

Full logs here --
http://koji.fedoraproject.org/koji/taskinfo?taskID=3905286

Comment 1 Milan Broz 2012-03-18 10:32:11 UTC
Apparently dm-crypt kernel module missing somewhere.

*** This bug has been marked as a duplicate of bug 804345 ***


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