*** This bug is a duplicate of bug 428435 ***
https://bugs.launchpad.net/bugs/428435
** This bug is no longer a duplicate of bug 362315
blkid fails to identify old LUKS partition volumes
** This bug has been marked a duplicate of bug 428435
luks encrypted partition not detected or mounte
*** This bug is a duplicate of bug 362315 ***
https://bugs.launchpad.net/bugs/362315
** This bug has been marked a duplicate of bug 362315
blkid fails to identify old LUKS partition volumes
--
initrd no longer activating encrypted filesystems
https://bugs.launchpad.net/bugs/318892
You rec
I've just checked on my recently-built Karmic laptop to see if this is
still a problem. I think it is not. The /etc/crypttab generated
automatically as part of the Karmic installation contains an _ in the
device name, so I suspect this was probably fixed by a new release of
whatever package reads t
I experienced the same issue, after a fresh reinstall of Jaunty
yesterday. I also had my encrypted lvm partition created by an earlier
ubuntu release and it was named sda5_crypt. The script which is
responsible for parsing crypttab seems to be in /usr/share/initramfs-
tools/hooks/cryptsetup . Bug 3
ha-HA! The problem seems to be that underscore is no longer a valid
character for the device name. I changed "sda2_crypt" to "root" and
everything works beautifully!
Now for the bad part. What the heck happened here?! WHY did "sda2_crypt"
stop being a valid target name? That name was picked for my
bug 319982 and bug 287879 have been fixed now and I'm still not prompted
for my encryption passphrase at boot. After reading over comments by
other people in those bugs, I've noticed that my initrd does not contain
a file "conf/conf.d/cryptroot". This file seems to be what tells the
initrd which de
You're experiencing a new and fantastic bug introduces in the recent
update to udev 138-1. Check out bug 332270.
--
initrd no longer activating encrypted filesystems
https://bugs.launchpad.net/bugs/318892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I have what appears to be a related issue. I was originally getting the
busybox prompt, but running cryptsetup luksOpen... wouldn't fix the
problem. I ran the recovery CD, chrooted, and did an apt-get upgrade.
After recent updates installed (about 10 minutes before I posted this) I
rebooted. Now
Even after updating for the package fix referred to in bug #287879 my
issue is still not fixed. I could really use some help debugging this!
Here's my current state:
Every time I boot my system, I'm dropped to an initrd busybox prompt
with a notice that my root device can't be found. The root dev
My issue could be related to (or the same as) bug #287879. Since that is
now resolved I'll update tonight to indicate if this has resolved my
issue. I got that package update last night but haven't rebooted the
laptop yet.
--
initrd no longer activating encrypted filesystems
https://bugs.launchpa
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
initrd no longer activating encrypted filesystems
https://bugs.launchpad.net/bugs/318892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I should mention that the laptop in question is running Jaunty, so the
packages involved are changing frequently. My initrd has been
regenerated a number of times since the problem started, and the kernel
has been updated at least twice.
My guess is that the order of the stuff run in the initrd ha
12 matches
Mail list logo
