| 2009-08-28 07:16:27 |
Nicola Larosa |
bug |
|
|
added bug |
| 2009-08-28 07:19:02 |
Nicola Larosa |
tags |
|
karmic |
|
| 2009-08-28 07:21:39 |
Nicola Larosa |
description |
This is on Karmic.
Startup freezes after successfully opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. presumably after the cryptdisks-early init script is run. The volumes are defined via lvm2.
There is no message on the screen, no log apparently written anywhere.
The kernel is still responsive, USB connects and disconnects are reported on screen. The Magic SysRq key combos work, allowing a clean shutdown.
Another Karmic install in another partition works, and correctly mounts all volumes, all in good shape. Such a second install has not been upgraded since Tuesday 25, three days ago. |
This is on Karmic.
Startup freezes after successfully opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. presumably after the cryptdisks-early init script is run. The volumes are defined via lvm2.
The passphrase is asked and successfully recognized, but the volumes within are not mounted. No relevant message is shown on screen, no log apparently written anywhere.
The kernel is still responsive, USB connects and disconnects are shown on screen, the Magic SysRq key combos work, allowing a clean shutdown.
Another Karmic install in another partition works, and correctly mounts all volumes, all in good shape. Such a second install has not been upgraded since Tuesday 25, three days ago. |
|
| 2009-08-28 10:00:37 |
Nicola Larosa |
affects |
ubuntu |
cryptsetup (Ubuntu) |
|
| 2009-08-28 10:01:04 |
Nicola Larosa |
summary |
Startup freezes after opening encrypted device |
cryptsetup stops after opening encrypted device |
|
| 2009-08-28 10:04:28 |
Nicola Larosa |
description |
This is on Karmic.
Startup freezes after successfully opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. presumably after the cryptdisks-early init script is run. The volumes are defined via lvm2.
The passphrase is asked and successfully recognized, but the volumes within are not mounted. No relevant message is shown on screen, no log apparently written anywhere.
The kernel is still responsive, USB connects and disconnects are shown on screen, the Magic SysRq key combos work, allowing a clean shutdown.
Another Karmic install in another partition works, and correctly mounts all volumes, all in good shape. Such a second install has not been upgraded since Tuesday 25, three days ago. |
This is on Karmic.
cryptsetup stops after opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. The volumes are defined via lvm2.
The passphrase is asked and successfully recognized, and then the command freezes, preventing mounting the volumes on boot. No message is shown on screen.
The command works in another Karmic install in another partition, exiting correctly. Such a second install has not been upgraded since Tuesday 25, three days ago.
|
|
| 2009-08-28 10:04:46 |
Nicola Larosa |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-08-28 14:20:26 |
Nicola Larosa |
description |
This is on Karmic.
cryptsetup stops after opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. The volumes are defined via lvm2.
The passphrase is asked and successfully recognized, and then the command freezes, preventing mounting the volumes on boot. No message is shown on screen.
The command works in another Karmic install in another partition, exiting correctly. Such a second install has not been upgraded since Tuesday 25, three days ago.
|
This is on Karmic.
cryptsetup stops after opening the encrypted partition /dev/sda3 , where the /var, /home and swap volumes are located. The volumes are defined via lvm2.
The passphrase is asked and successfully recognized, and then the command freezes, preventing mounting the volumes on boot. No message is shown on screen.
The command works in another Karmic install in another partition, exiting correctly. Such a second install has not been upgraded since Tuesday 25, three days ago. However, the last change to the cryptsetup package is from May, so something else has probably changed.
|
|
| 2009-09-05 04:29:13 |
Richard Hansen |
cryptsetup (Ubuntu): status |
New |
Incomplete |
|
| 2010-11-23 04:21:05 |
Launchpad Janitor |
cryptsetup (Ubuntu): status |
Incomplete |
Expired |
|
