On 01/26/2011 05:28 PM, Colin Watson wrote: > I tried to reproduce this with a daily build using the "Guided - use > entire disk and set up encrypted LVM" option, but I couldn't - it > installs cryptsetup into /target successfully and the resulting system > boots fine.
we've fixed that for lvm some time ago in live-installer; good to know that lvm+cryptsetup works. what didn't work was cryptsetup, or mdadm (and that is what this bug is about). > Can you point me at a way to reproduce this? > Alternatively, a syslog from an installation run with the > DEBCONF_DEBUG=developer boot parameter would be helpful. i'll hope i can get to it somewhen later today, but no promise. -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
