Comment 3 for bug 287879

I can confirm this bug on Ubuntu 8.10. Nikolaus is correct. Not only may UUIDs be used to reference LVM volumes in /etc/fstab, this is the default configuration in 8.10. I followed the instructions here (https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto) in order to create a LUKS+LVM encrypted system with AES-XTS, which as of this time is currently unsupported by the alternative installer.

After manually creating a LUKS volume, setting up the LVM, and creating the partitions using the 8.10 Live CD, I installed as normal. The installer setup the system as if it was an unencrypted LVM volume. The LVM volumes in /etc/fstab were referenced by their UUID. However, I found that with this setup the system is unbootable, and no warning is displayed when the initrd is created. There simply is no config/config.d/cryptroot and thus the system is unbootable.

Modifying /etc/fstab to reference the device name resolves the issue. However, UUIDs may be used in /etc/crypttab.

My understanding from reading some other bug reports is that the UUID is inaccessible because it's only available when the volume has been decrypted. However, aren't the partitions mounted by the time fstab is read to mount them? I would assume /etc/crypttab is read first to decrypt the LUKS volume, and then the UUID of the LVM volumes should be accessible to the system. Perhaps I'm wrong about this.

Anyway, this is a serious issue as it causes the system to become unbootable with no warning.