Yes, Mikko - that is very useful information, except that description of the crypttab is a little crypt-tic (bad pun, sorry :) So if I got that right, it looks like: [device-mapper-name] [physical-location-of-LVM] none luks and I only need to do this for the / partiton, not /home and swap? I should have kept my old crypttab when I went to re-install, but I forgot about it. Oops! Also, I too was having problems with the 8.10 alt disc, so I went back to 8.04.1 and am planning to upgrade - the trick was that I wanted to reinstall / while not deleting my /home partition, which means I have to install from the 'rescue' side of the disk so that it loads the dm-crypt modules and unlocks the partitions to do the new install. Unfortunately it appears that this does not trigger the routines which either install the modules or the /etc/crypttab... ha. Well, I'm going to reboot and try these things to see if everything is tip-top. Thank you guys! Sven: update-initrd is supposed to put ash in there, I believe, but I am quite certain that the it bumps you to a busybox terminal. Thanks again! Cheers, Matt On Thu, Jan 8, 2009 at 3:22 PM, Sven Eschenberg <sven@xxxxxxxxxxxxxxxxxxxxx>wrote: > Hi Mikko, > > thnx, that IS the distribution specific part concerning their initrd builds > I was 'looking' for or rather eferring to. > > So the command is called mkinitramfs and the script needs configuration > information from crypttab. > > Another thing one couldn't know, does Ubunut come with busybox or an ash > etc. in the initrd? It's good to know there's everything in place, I am not > sure though, if an inexperienced user can fix things from a simple rescue > shell. > > Thanx again for your specific additions... > > Regards > > -Sven > > > Mikko Rauhala schrieb: > >> to, 2009-01-08 kello 14:57 +0100, Sven Eschenberg kirjoitti: >> >>> In any case, it might be helpfull to boot a rescue system and inspect the >>> initrd that is currently used or rebuild the initrds (in the hope the needed >>> modules will be packed into the initrd) ... >>> >> >> I found that the Ubuntu alternate installer basically forgets to create >> an /etc/crypttab and the initrd would like that as well to boot >> properly. >> >> You can set up dm_crypt manually from the initrd shell (it drops to it I >> believe after a timeout at least if it can't find the root) and boot >> your system that way to fix it. >> >> [...] >> > > --------------------------------------------------------------------- > 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
