| 2010-01-19 06:45:26 |
Stéphane Graber |
bug |
|
|
added bug |
| 2010-01-19 06:46:30 |
Stéphane Graber |
description |
Binary package hint: plymouth
I'm pretty sure I already reported that through probably in some other bug reports I filed during the few issues I had with Plymouth and mountall. So here's a new one that should make tracking easier:
My laptop is currently running up to date lucid with the following partitioning:
- /dev/sda1 => / (ext4)
- /dev/sda2 => Volume for encryption
- LVM
- VG
- LV home: /home (ext4)
The reason I'm using LVM is because I like to be able to create additional partitions if needed (even though I have only a single one at the moment) and I have / outside of the encrypted volume for boot performance (that's on a SSD and I like fast booting).
When booting, I correctly get Plymouth to start and see the splash just well but it gets stuck there and doesn't get to gdm.
Pressing ESC, I get out of the splash and can see that cryptsetup is trying to unlock /dev/sda2 but never prompts me for the passphrase. As a result, the laptop simply can't boot.
Commenting my /home partition in the fstab makes the boot work perfectly though I then have to manually unlock the partition and mount the LV by hand.
Expected result would be to have cryptsetup ask plymouth to prompt me for the passphrase, so it can correctly unlock the encrypted volume.
My current guess is that the most tested use case for cryptsetup is where you have your root partition on the encrypted volume and so the unlocking has to happens in the initrd, in my case, the unlocking process happens during the boot, after the root partition is mounted. |
Binary package hint: plymouth
I'm pretty sure I already reported that issue though probably in some other bug reports I filed during the few issues I had with Plymouth and mountall.
So here's a new one focusing on that single encryption issue, that should make tracking easier:
My laptop is currently running up to date lucid with the following partitioning:
- /dev/sda1 => / (ext4)
- /dev/sda2 => Volume for encryption
- LVM
- VG
- LV home: /home (ext4)
The reason I'm using LVM is because I like to be able to create additional partitions if needed (even though I have only a single one at the moment) and I have / outside of the encrypted volume for boot performance (that's on a SSD and I like fast booting).
When booting, I correctly get Plymouth to start and see the splash just well but it gets stuck there and doesn't get to gdm.
Pressing ESC, I get out of the splash and can see that cryptsetup is trying to unlock /dev/sda2 but never prompts me for the passphrase. As a result, the laptop simply can't boot.
Commenting my /home partition in the fstab makes the boot work perfectly though I then have to manually unlock the partition and mount the LV by hand.
Expected result would be to have cryptsetup ask plymouth to prompt me for the passphrase, so it can correctly unlock the encrypted volume.
My current guess is that the most tested use case for cryptsetup is where you have your root partition on the encrypted volume and so the unlocking has to happens in the initrd, in my case, the unlocking process happens during the boot, after the root partition is mounted.
|
|
| 2010-01-21 03:06:54 |
Stéphane Graber |
attachment added |
|
/etc/default/cryptdisks http://launchpadlibrarian.net/38174562/cryptdisks |
|
| 2010-01-21 03:07:20 |
Stéphane Graber |
attachment added |
|
Modified /etc/init/cryptdisks-enable.conf http://launchpadlibrarian.net/38174568/cryptdisks-enable.conf |
|
| 2010-01-21 03:08:36 |
Stéphane Graber |
attachment added |
|
Modified /etc/init/cryptdisks-udev.conf http://launchpadlibrarian.net/38174580/cryptdisks-udev.conf |
|
| 2010-01-21 03:09:01 |
Stéphane Graber |
attachment added |
|
/etc/crypttab http://launchpadlibrarian.net/38174584/crypttab |
|
| 2010-01-21 03:10:18 |
Stéphane Graber |
attachment added |
|
/etc/fstab http://launchpadlibrarian.net/38174619/fstab |
|
| 2010-01-21 03:10:41 |
Stéphane Graber |
attachment added |
|
/root/log.enable http://launchpadlibrarian.net/38174622/log.enable |
|
| 2010-01-21 03:10:59 |
Stéphane Graber |
attachment added |
|
/root/log.udev http://launchpadlibrarian.net/38174625/log.udev |
|
| 2010-01-21 11:42:58 |
Steve Langasek |
plymouth (Ubuntu): importance |
Undecided |
High |
|
| 2010-01-26 06:25:17 |
Stéphane Graber |
attachment added |
|
plymouth-not-prompting.329 http://launchpadlibrarian.net/38391704/plymouth-not-prompting.329 |
|
| 2010-01-26 07:18:15 |
Steve Langasek |
plymouth (Ubuntu): status |
New |
Triaged |
|
| 2010-01-26 07:18:25 |
Steve Langasek |
bug task added |
|
cryptsetup (Ubuntu) |
|
| 2010-01-26 07:19:29 |
Steve Langasek |
cryptsetup (Ubuntu): importance |
Undecided |
High |
|
| 2010-01-26 07:19:29 |
Steve Langasek |
cryptsetup (Ubuntu): status |
New |
Triaged |
|
| 2010-01-26 07:19:39 |
Steve Langasek |
plymouth (Ubuntu): importance |
High |
Medium |
|
| 2010-01-26 07:20:01 |
Steve Langasek |
summary |
[lucid] Plymounth not asking for passphrase on non-root partition |
[lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk |
|
| 2010-02-02 02:09:32 |
Steve Langasek |
plymouth (Ubuntu): assignee |
|
Steve Langasek (vorlon) |
|
| 2010-02-02 07:50:24 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/plymouth |
|
| 2010-02-02 08:20:09 |
Launchpad Janitor |
plymouth (Ubuntu): status |
Triaged |
Fix Released |
|
| 2010-02-03 01:55:10 |
Steve Langasek |
plymouth (Ubuntu): status |
Fix Released |
Incomplete |
|
| 2010-02-03 20:41:29 |
Steve Langasek |
plymouth (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2010-04-02 12:40:05 |
Marc Gariépy |
cryptsetup (Ubuntu): status |
Triaged |
Fix Released |
|
