I've done some more testing now with the local-top and hook scripts from 1.0.4-8ubuntu1 (everything else was default edgy packages). There are two things that are still broken for me.
To be clear, I have /dev/hda3 as a LUKS partition which gets mounted on /dev/mapper/cdisk. This then uses lvm to give me /dev/mapper/ubuntu- root and /dev/mapper/ubuntu-home which are mounted at the obvious points. I have also only installed a minimal system so I haven't tested usplash issues I've seen elsewhere (I can do that when the basics are working). 1. The local-top/lvm script will wait a LONG time due to the loop waiting for the root device to appear (ubuntu-root) which can't happen before cryptroot is run. This is easy to bodge and I will add to bug #69217 (although there is no visible action there). 2. The fstype test in local-top/cryptroot returns the wrong answer (ext3 not lvm). If I bodge the test to accept ext3 then boot continues successfully, so this is the only critical problem for me. I looked at the results from /usr/lib/klibc/bin/fstype <$1 and file -Lkbs $1 at all points of the chain getting the following results: /dev/hda3 fstype: FSTYPE=luks FSSIZE=0 file -Lkbs: data /dev/mapper/cdisk fstype: FSTYPE=ext3 FSSIZE=4515147776 file -Lkbs: LVM2 (Linux Logical Volume Manager) , UUID: Ia7Ek2XowWxeCQlu5s5ZfdrbmKv0mTw\012- Linux rev 1.0 ext3 filesystem data (large files) /dev/mapper/ubuntu-root fstype: FSTYPE=ext3 FSSIZE=838860800 file -Lkbs: Linux rev 1.0 ext3 filesystem data (large files) So unfortunately neither looks good enough. -- Support for encrypted root filesystem (cryptsetup) https://launchpad.net/bugs/21878 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
