I don't have this issue on a standard RHEL6. But this is when I tested my code on a slightly "customized" RHEL6. I guess something has been removed but not totally sure.
-bash-4.1# cryptsetup --version
cryptsetup 1.2.0
-bash-4.1#
-bash-4.1#
-bash-4.1# uname -r
2.6.32-131.6.1.el6.x86_64
On Fri, Jan 18, 2013 at 11:37 AM, Milan Broz <gmazyland@xxxxxxxxx> wrote:
On 01/18/2013 08:33 PM, Arno Wagner wrote:I would say it is self-compiled kernel :)
> On Fri, Jan 18, 2013 at 11:16:42AM -0800, David Li wrote:
>> Here is a newbie question.
>>
>> I encountered an error at luksFormat on a loop device:
>>
>> device-mapper: reload ioctl failed: Invalid argument
>> Failed to setup dm-crypt key mapping for device /dev/loop0.
>> Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for
>> more info).
>>
>> So I guesss my RHEL6 doesn't have the proper crypto module installed. This
>> is a dump of /proc/crypto:
> [....]
>> But I am not quite sure which package is missing here. Is it something
>> more general like "yum install aes"?
>
> Is this a self-compiled cryptsetup?
RHEL6 default kernel will autoload crypto modules as requested.
(And upstream cryptsetup works there too, it is one of the testing platform)
What's the kernel and cryptsetup version?
Milan
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
