Comment 23 for bug 428435

After some research this is what I've found out; udev is responsible of creating the entries under /dev/disks/by-uuid. Jaunty's udev (which is also in the old initrd) uses udev's vol_id library to detect the FS information. Karmic has new udev which has ditched vol_id and is using blkid instead. That's why the crypto partiton is "correctly" detected with the old initrd.

Now that odd behavior has an explanation and I can safely concentrate on solution.

Steven: How about creating a shell script that would handle the dd magic based on a couple of questions made to the user? Users could use live-cd to download and install the script manually to unencrypted /boot and we could do a safe backup of the superblock so that it can be restored if user has selected a wrong fs type? The scipt could also mount the modified partition as readonly to let the user verify that the files are there or something like that. Anyway it would be nice if there was a solution that would not require the user to do error prone DD magic by hand and is reversible if the user makes a mistake (wrong partition, wrong fs type, etc).