Encrypted LVM fails to install (Lubuntu-alternate-14.04)

[turtlepurple]

I installed Lubuntu 14.04.1 (32bit) with alternate Installer and used the encrypted LVM setup option. The system wont boot - after a minute waiting i see busybox initramfs.

in the initramfs i CAN open sda5 with cryptsetup luksOpen /dev/sda5 sda5_crypt

lvm -vgscan then DOES see my encrypted Logical Volumes (root and swap)

The system also does boot to tty1 when i use (recovery mode). actually i tried changing all the bootparametes (that differ in normal and recovery mode) live in grub and it only fails when I have the splash option active.

So i guess the initramfs is not missing any modules it just tries to boot before asking me for a password.

And I dont know what to do after opening my encrypted LV to retry a normal boot from that point on. exiting initramfs gives errors. mounting /dev/mapper/sda5_crypt to /root (or /) doesnt seem to be right, too.

(actually tried lubuntu 14.04.1-alternate 64, 14.04-alternate 32 and 14.04.1-desktop 64 alrdy - (some of them had problems during "installation of software" but i think this is irrelevant) - was the same upon booting)

The install works for Ubuntu 14.04.1 - it will graphically ask me to enter the password. Is this lightdm? whats missing here in lubuntu?

Also asked a question at ask-ubuntu: http://askubuntu.com/questions/584663/how-to-arrange-initramfs-lubuntu-14-04-1-encrypted-lvm-boots-in-recovery-mode

[turtlepurple (turtle-purple)]

Here's a dump of the failing initrd

[turtlepurple (turtle-purple)]

The Software install -problem wasnt irrelevant - see (https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1417918, https://bugs.launchpad.net/ubuntu/+source/pkgsel/+bug/1065349)

The system is bootable in recovery mode and can be fixed with a simple "sudo apt-get install lubuntu-dekstop" (after adding the repositories to /etc/apt/sources..list - it only contains the CD after the failing install)

Other way is to use "Install" ( Or "Expert install" - thats in unetbootin-menu) This will lead to another bug when installing MBR if you're using a pendrive (https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1426219)

And as the Desktop-CD (14.04.2) is still failing on encrypted LVM - Installation (https://bugs.launchpad.net/ubuntu/+bug/1241833) the alternate CD is still the best way to go.

Encrypted LVM does work with the "Install"-method + MBR-workaround (https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1424789)

[turtlepurple (turtle-purple)]

EDIT: (Wrecked up the last post)

The Software install -problem wasnt irrelevant - see (https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1417918, https://bugs.launchpad.net/ubuntu/+source/pkgsel/+bug/1065349)

1. Workaround; The system is bootable in recovery mode and can be fixed with a simple "sudo apt-get install lubuntu-dekstop" (after adding the repositories to /etc/apt/sources..list - it only contains the CD after the failing install)

2. Clean Install: use "Install" ( Or "Expert install" - thats in unetbootin-menu) This will lead to another bug when installing MBR if you're using a pendrive (https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1426219) but just select "No" when installing MBR and you can choose the target device.

That way I installed a working guided encrypted LVM from lubuntu 14.04.1 alternate i386

[Mathieu Trudel-Lapierre (cyphermox)]

What message do you get in the initramfs?

Installation problems are rarely irrelevant when they precede a failure to boot; certainly some package has not yet been configured and that's why running 'sudo apt-get install luibuntu-desktop' fixes things.

If you see the same error messages in install as in the other bugs you linked, then it's indeed a problem that can be caused by the failing installation, especially if you're seeing these messages about libgl* failing to be installed (Conflicts).

I'll reassign this to pkgsel for now, but without the details from the installation (the exact messages that appeared, which may still be in /var/log/installer), it's going to be hard to resolve this after the fact.

[Launchpad Janitor (janitor)]

[Expired for pkgsel (Ubuntu) because there has been no activity for 60 days.]