Comment 11 for bug 144390

Hi,

Ian Jackson [2007-10-02 16:49 -0000]:
> Martin Pitt writes ("[Bug 144390] Re: use entire disk with lvm/encrypted partitioning fails to boot"):
> > The root problem is that /usr/share/initramfs-tools/hooks/cryptroot does
> > not know anything about UUIDs. It needs to be taught to recognize UUIDs
> > in fstab and crypttab and write a sane /conf/conf.d/cryptroot into the
> > initramfs.
>
> This is not possible, because the UUID of the filesystem is in the
> encrypted portion of the disk. So it is no good quoting the fs UUID
> in the config file as the on-disk copy is not accessible until the
> decryption for the relevant partition or LV has already been set up.

No, that's alright. The script I am talking about runs at
update-initramfs -u time. What it does is to read fstab and crypttab
and figure out the 'outer' (encrypted) devices that contains the root
file system (which is on the cleartext device in an LVM). It
essentially translates fstab and crypttab into a proper
conf/conf.d/cryptroot file in the initramfs, so that the initramfs
hook knows which device it needs to luksOpen to get the root fs.