crypttab not updated when building an md->LUKS->LVM root device using Hardy alternate installcd on amd64

[Luke Scharf]

I built a system with the following filesystem, using the manual partitioning tool in Ubuntu 8.04 alternate server install CD for amd64:
/dev/sda1 -\
/dev/sdb1 -+-> /dev/md0 -> ext3 (for /boot)
/dev/sda2 -\
/dev/sdb2 -+> /dev/md1 -> LUKS encryption (md1_crypt) -> LVM physical Volume -> LVM -> root (ext3), /tmp (ext3), /var (ext3, and also swap

(Aside: It took a couple of attempts to arrive at this layering -- I had originally figured I would put the the encryption on top of LVM, so as to make booting and troubleshooting easy. However, the layering that I describe above seemed natural in the installer, and the system only prompts me for the passphrase once on boot.)

PROBLEM: The problem is that the installer neglected to put any entries in /etc/crupttab.When I attempted to boot the system for the first time, it entered the initrd shell.

WORKAROUND: In the initrd shell, I had to run "cryptsetup luksOpen md1_crypt /dev/md1", "vgscan", and "continue" to be able to boot. Once the system booted, I manually filled in /etc/crypttab (based on what I had to enter in the initrd shell), ran "dpkg-reconfigure initramfs-tools", and rebooted. After these changes, the system boots normally, and I got on with life.

SOLUTION: The alternate installer on Hardy Server should write /etc/crypttab when doing a manual install.