Bug 726740 - Kernel 3.1.0-0.rc0.git9.1.fc17 won't unlock encrypted drive
Summary: Kernel 3.1.0-0.rc0.git9.1.fc17 won't unlock encrypted drive
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 16:38 UTC by Tom
Modified: 2011-07-30 03:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-30 03:03:26 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tom 2011-07-29 16:38:57 UTC 
Description of problem:
Kernel 3.1.0-0.rc0.git9.1.fc17 won't unlock encrypted hard drive, but previous kernel 3.0.0-1.fc16 does.

Version-Release number of selected component (if applicable):
Kernel 3.1.0-0.rc0.git9.1.fc17 

How reproducible:
Everytime

Steps to Reproduce:
1.Updated kernel and can no longer boot with new kernel.
2.
3.
  
Actual results:
This is the error I get:
device mapper: reload ioctl failed: Invalid argument
Failed to setup dm_crypt key mapping for device /dev/sda2
check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Failed to read from key storage

Expected results:
Still unlock old encryption

Additional info:
Comment 1 Josh Boyer 2011-07-29 18:32:36 UTC 
This is probably because we messed up some of the pre-RC release handling.  Could you try this build when it completes?

http://koji.fedoraproject.org/koji/buildinfo?buildID=256250
Comment 2 Tom 2011-07-30 02:16:52 UTC 
That got it, thanks.
Comment 3 Josh Boyer 2011-07-30 03:03:26 UTC 
Thanks for testing!
Note You need to log in before you can comment on or make changes to this bug.