On 6 August 2013 19:35, Ben Hutchings <b...@decadent.org.uk> wrote: > On Tue, 2013-08-06 at 10:17 -0700, Matt Taggart wrote: >> Ben Hutchings writes: >> > On Mon, 2013-08-05 at 16:31 -0700, Matt Taggart wrote: >> > > I think I am seeing the same bug reported in #716978... >> > >=20 >> > > I just did an install of wheezy using a d-i daily (updated today >> > > 2013-08-05). The root is md raid->crypt->lvm. Upon boot the initramfs >> > > started up the md raid devices properly, but failed to setup the crypto >> > > and dropped to an initramfs shell. When I poke around I see that >> > >=20 >> > > /lib/modules/3.2.0-4-amd64/kernel/crypto/ >> > >=20 >> > > is lacking most of the crypto modules (including the xts/serpant/etc >> > > that my system needed). So I am unable to bring things up by hand >> > > either. >> > >=20 >> > > During the install, for the question about how much to include in the >> > > initramfs, I picked the "just what's needed by this system" answer, >> > > although I think that should have been OK. >> > >> > I doubt we'll ever be able to get it completely right. That option >> > should be warned against in general. It is useful for machines with >> > limited memory or space for the initramfs (e.g. ARM systems where the >> > bootloader looks for it in a specific flash partition). Otherwise it >> > just saves a fraction of a second of boot time, or fails to boot. >> >> I used d-i rescue mode to mount the disks and switch from "dep" to "most" >> mode for update-initramfs and that pulled the crypto modules in. But now >> the problem is that the LVM tools aren't in the initramfs so it gets stuck >> at that point. > > That's strange. The LVM tools are added by > /usr/share/initramfs-tools/hooks/lvm2 which is part of the lvm2 package. > So this implies lvm2 wasn't installed either, though that seems > unlikely. >
Do we have full debug level logs for the broken install available? cause I did some refactoring on partman-lvm and partman-crypto together with new upstream releases of lvm2, crypto, kernel.... there are plenty of things that could have gone wrong. Also just recently in ubuntu this upload was made: https://launchpad.net/ubuntu/+source/lvm2/2.02.98-1ubuntu4 To fix a very nasty: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1206235 Not sure if debian is also affected, and whether it's related at all. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
