Public bug reported:
Binary package hint: udev
Description: Ubuntu 9.04
Release: 9.04
udev:
Installed: 141-1
Symptoms:
My laptop fails to boot since I upgraded from Intrepid to Jaunty. Before
Jaunty, the system asked for cryptsetup luks passphrases twice, a first time
for the root partition (sda3 on my system) and a second time for the swap
partion (sda4). Since Jaunty it asks for the root cryptsetup passphrase,
unlocks the slot, waits a long time then drops to a shell, saying that the
device /dev/disks/by-uuid/.... (id of sda4 partition) was not found. I have to
manually create the link in /dev/disks/by-uuid every time for the system to
boot.
What's actually wrong:
running udevadm info --export-db do not report any uuid for sda4, while sda3 is
correct. See attached file.
More wrongness:
# vol_id /dev/sda4
unknown or non-unique volume type (--probe-all lists possibly conflicting types)
# vol_id --probe-all /dev/sda4
swap
crypto_LUKS
## I could not find a way to make vol_id spit out the uuid of the luks header
of the partition.
For information, blkid has a different kind of wrongness. Out of the box
it will report a wrong uuid (that is, the uuid that was used in intrepid
and before), probably because it parses the luks data as swap area. But
then it is possible to edit /etc/blkid.tab and say that sda4 is of type
crypt_LUKS, then blkid will find the right UUID and remember it.
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
udev fails to identify crypt_LUKS swap partition by uuid
https://bugs.launchpad.net/bugs/362315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
