[Pkg-cryptsetup-devel] Bug#344867: Acknowledgement (cryptsetup: aes-cbc-essiv:sha256 fails. module/s not loaded at boot (initrd)?)

[James Clark]

cryptsetup -c aes-cbc-essiv:sha256 create root /dev/hda3
mount /dev/mapper/root /mnt
chroot /mnt

 From within the chrooted environment setup is as follows (i.e. after 
preceding steps)

---

dvda:/# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a "#", and everything on the line after them are ignored.
ide-cd
ide-detect
ide-disk
psmouse
ip_conntrack_ftp
dm-crypt
aes-i586
sha256


dvda:/# cat /etc/crypttab
# <target device> <source device> <key file> <options>
root /dev/hda3 none cipher=aes-cbc-essiv:sha256


dvda:/# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system>  <mount point>   <type>  <options>
<dump>  <pass>
proc             /proc    proc    defaults                   0       0
/dev/hda2        /boot    ext3    defaults,errors=remount-ro 0       1
/dev/mapper/root /        ext3    defaults,errors=remount-ro 0       1


and what is being fed (running it by hand at boot):
kernel (hd0,1)/vmlinuz-2.6.12-1-k7 root=/dev/mapper/root
initrd (hd0,1)/initrd.img-2.6.12-1-k7
  (where initrd.img-2.6.12-1-k7 is the image previously created from
   within the chroot with /boot mounted at /dev/hda2)


A screen capture of the boot failure:
   http://www.bofh.co.nz/files/p1010002_s.jpg


Cheers,
James