Thanks guys - the problem with the cryptsetup error seems to have been related to using the recovery prompt. I ran: "cryptsetup luksOpen" from the busybox shell, exited it, and then booted the system just fine. After getting into the system, I added the appropriate entries in /etc/crypttab, and then used: $ sudo update-initramfs -k all -c -v to do the trick. In my full environment it calls cryptsetup witout errors, so it must have had something to do with running that from a rescue prompt. But, the important thing is that everything seems tip-top now! I'm writing a HOWTO on installing Ubuntu over an existing dm-crypt system because I ran into so many headaches while trying to do it. I'll send the link when it is done. Thanks a bunch to all of you, this would have taken me infinitely longer to figure all of this out on my own. Cheers! Matt On Thu, Jan 8, 2009 at 5:35 PM, DarKRaveR <dark@xxxxxxxxxxxxx> wrote: > Hi Matt, > > Well, yes and no, BBox is a mulitcall binary with a huge heapload of tools, > including a shell, with ash flavor or bash (faiak), anyway, that'S not > really important. > cryptsetup does not USE and file in /etc, I'd rather think the file is used > for an appropriate init script and obviously mkinitramfs. > Either mkinitramfs is buggy, or is has some sort of module scheme, with a > module which ist supplied by some package along cryptsetup and which fails. > Unfortunately I got no Ubuntu at hand, to dig into this right now - But it > wouldn't be the first bug in mkinitramfs and the surrounding 'framework'. > If you have the necessary experience, you could dig into the script and see > at what point crypttab is treated and in what way exactly. > > Regards > > -Sven > > Matt Rosales schrieb: > >> OK, well attempt #1 = fail. >> >> >> From busybox (which apparently is ash... I get your comment now Mathieu) I >> tried first to create a /etc/crypttab file with the correct info in it, >> but >> of course this doesn't stay after a reboot, now does it... ha. >> >> So I got the rescue up and running; all of the appropriate modules are in >> there: aes, dm-crypt and dm-mod, put the data in the crypttab file, and >> tried to use mkinitramfs -o <initrd-filename> but got a cryptsetup error: >> WARNING: invalid line in /etc/crypttab >> >> This is odd to me since there is only one line in it: >> MtOlympus /dev/sda4 none luks >> >> This may be a bug in cryptsetup, as I've been reading in various other >> posts, so I'm going to see if I can update the package through the rescue >> disk... >> >> Thanks for your help guys! >> >> Matt >> >> > > --------------------------------------------------------------------- > dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ > To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx > For additional commands, e-mail: dm-crypt-help@xxxxxxxx > > -- (206) 714 4059 matt@xxxxxxxxxxxxxxx PO Box 644 Bellevue, WA, USA 98009-0644
