scudette <[EMAIL PROTECTED]> writes:
> If I remove the UUIDs and replace them back with a device name it
> works.
Yes, the installer was fixed to not do the UUID conversion for
/dev/mapper/*_crypt devices anymore. You have used a broken version of
the installer, please undo that mangling by hand.
Gutsy fails to find the root device in /usr/share/initramfs-
tools/hooks/cryptroot because it blindly looks at the fstab entry for
root and takes the first entry like so:
while read device mount type options dump pass; do
if [ "$mount" = "/" ]; then
echo "$d
Feisty and gutsy now correctly support booting from encrypted LVM
properly with cryptsetup package.
** Changed in: cryptsetup (Ubuntu)
Status: Fix Committed => Fix Released
--
Support for encrypted root filesystem (cryptsetup)
https://bugs.launchpad.net/bugs/21878
You received this bug no
This works a little better, It will check every 1/2 a second for the
device, then as soon as it shows up it continues. Should speed things up
from the above fix a bit.
Other then this fix cryptsetup-1.0.4+svn26-1ubuntu1 Works for me using
lvm on top of a single Luks partition.
/usr/share/initram
I have the same problems with a normal disk (/dev/hda1) as cryptroot.
Introducing a "sleep 5" let me boot my system.
# Make sure the cryptsource device is available
if [ ! -e $cryptsource ]; then
activate_vg $cryptsource
fi
+ if [ ! -e $cryptsource ];
Thats pretty much what i came up with to get it working.
except that theres no need to create symlinks to vgchange, it should
instead call `lvm vgchange`, the lvm script does it incorrectly to by
making symlinks.
And yeah it has to run _before_ lvm, it takes care of all the lvm stuff
it self, ha
... and once again I messed up - the patch I submitted last contains some
unnecessary testing code (to allow activating VG by name, it's never done
anyway).
Attached is the patch without this part.
More coffee needed, I think...
** Attachment added: "Patch for lvm support in ramdisk cryptroot
** Attachment added: "Patch to wait for device nodes in ramdisk cryptroot
script"
http://librarian.launchpad.net/5401161/initramfs-cryptroot-script.patch
--
Support for encrypted root filesystem (cryptsetup)
https://launchpad.net/bugs/21878
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Attachment added: "Patch to load correct block cipher algorithm for
encrypted root in cryptroot-hook"
http://librarian.launchpad.net/5401165/initramfs-cryptroot-hook.patch
--
Support for encrypted root filesystem (cryptsetup)
https://launchpad.net/bugs/21878
--
ubuntu-bugs mailing list
Hmm, I don't think you really need to modify the scripts for
LUKS - LVM PV - ROOT-ON-LVM configuration, if you use correct
parameters everywhere.
My root command line is simply:
root=/dev/mapper/sys-root resume=/dev/mapper/sys-swap ro quiet
And crypttab contains following line:
sys
I have a patched /usr/share/initramfs-tools/scripts/local-top/cryptroot to work
with a encrypted physical volume and root on lvm. The key is it runs _before_
lvm, thats the only major change, that and it doesn't call "/sbin/vgchange" but
calls "lvm vgchange" (nothing should be calling "/sbin/vg
I've done some more testing now with the local-top and hook scripts from
1.0.4-8ubuntu1 (everything else was default edgy packages). There are
two things that are still broken for me.
To be clear, I have /dev/hda3 as a LUKS partition which gets mounted on
/dev/mapper/cdisk. This then uses lvm to
I'd like to test 2:1.0.4-8ubuntu1 but I can only find the source. As
I'm testing on a small old box with just the cli system installed I
can't sensibly install the toolchain. Is there a binary package for
edgy anywhere or can I usefully test by just taking the scripts from
this source package.
B
could you please check if package version 1.0.4-8ubuntu1 does work for
you? there have been many many changes merged from debian, including
crypted root filesystem.
I'm setting this bug to 'Fix committed'. Please check if this bug has
been fixed for you and set it to either confirmed or fix releas
14 matches
Mail list logo
