Encrypted Root with F11

[davide]

Brian Mearns <bmearns <at> ieee.org> writes:
> Well, I opened my initrd init-script, but very little of it means
> anything to me. Davide indicated a certain section in his script as
> relevant, so I've included that section of mine. It's a bit different,
> but I'm not sure if that's relevant:
> 
> ###############################################
>    echo Creating block device nodes.
>    mkblkdevs
>    echo Creating character device nodes.
>    mkchardevs
>    echo "Loading aes module"
>    modprobe -q aes
>    echo "Loading cbc module"
>    modprobe -q cbc
>    echo "Loading sha256 module"
>    modprobe -q sha256
>    echo "Loading sata_nv module"
>    modprobe -q sata_nv
>    echo "Loading pata_acpi module"
>    modprobe -q pata_acpi
>    echo "Loading ata_generic module"
>    modprobe -q ata_generic
>    echo "Loading dm-crypt module"
>    modprobe -q dm-crypt
>    echo Making device-mapper control node
>    mkdmnod
>    modprobe scsi_wait_scan
>    rmmod scsi_wait_scan
>    mkblkdevs
>    echo Scanning logical volumes
> ###############################################

I'm not sure that order matters in creating initrd image but my init and yours
differ just in modules order.


just to be sure, can you paste here the same output (once you mount the 
encrypted partition)?

(219)-~% sudo cryptsetup status /dev/mapper/luks-alfanumeric-code-uuid | grep 
cipher
[sudo] password for davide: 
/dev/mapper//dev/mapper/luks-alfanumeric-code-uuid is active:
  cipher:  aes-cbc-essiv:sha256
(220)-~% 

as you can see, I'm using aes in cbc mode with sha256.
You? Maybe you choosed a different setup and there is a mistake in the module
choice.