On 20 February 2010 03:55, Jonas= Meurer <jona= s@freesources.org> wrote:

hey sven,

On 17/02/2010 Selim Levy wrote:
> The cause:
> During the CD installation of debian, the debian installer associates = the
> external hard drive to /dev/sdb. =A0However, following the installatio= n, when
> I boot *from* the external hard drive, the system associates it with > /dev/sda. =A0So essentially, I'm installing linux (and dm-crypt an= d everything
> else) to /dev/sdb, though it will then be called /dev/sda when I boot = from
> it.
>
> The question:
> I've already made the necessary changes to GRUB and the /boot part= ition is
> booting properly -- I can get a busybox prompt -- but I'm unable t= o continue
> booting into the root partition. =A0Where are the files on /boot locat= ed that
> must be changed in order for the boot partition to properly deal with = the
> dm-crypt encrypted LVM volume group? =A0I have already found the
> conf/conf.d/cryptroot file within my initrd image and have modified bo= th
> lines in it. =A0(One line is for the root partition, the other for swa= p.)
> I've modified the 'target=3D' and the 'source=3D' = entries (on both llines) to
> show 'sda3' as opposed to the original 'sdb3'. =A0What= else must be changed?

you need to change both /etc/crypttab and /etc/fstab on the rescue system, and maybe even /etc/initramfs-tools/conf.d/resume.
afterwards you'll have to regenerate the initramfs image. the best way<= br> to do so is to:
- unlock and mount the rootfs of your rescue system to /mnt/rescue
- copy /proc/modules, /proc/cmdline and /proc/devices to
=A0/mnt/rescue/proc
- bind-mount /dev to /mnt/rescue/dev: 'mount -o bind /dev /mnt/rescue/d= ev'
- chroot into /mnt/rescue/dev
- modify /proc/cmdline, /etc/crypttab and /etc/fstab
- run 'update-initramfs -u'

Just in ca= se I had screwed things up myself prior to your reply and my new attempts, = I reinstalled Debian lenny onto the external USB drive (which I call "= rescue" or "external").

I booted back into my internal drive and attempted all of your recommen= dations on the external drive:

<output for following omitted beca= use no errors>
# cryptsetup luksOpen /dev/sdc3 rescue
# vgchange -= a y rescue
# mount /dev/rescue/rooto /mnt/RootRescue/
# mount /dev/sdc2 /mnt/RootRe= scue/boot/
# mount -o bind /dev /mnt/RootRescue/dev

However, = when I get to updating my initramfs, I get the following error:

# chroot /mnt/RootRescue/ /usr/sbin/update-initramfs -u
update-initramfs= : Generating /boot/initrd.img-2.6.26-2-amd64
cryptsetup: WARNING: invali= d line in /etc/crypttab -
cryptsetup: WARNING: invalid line in /etc/cryp= ttab -

The contents of the rescue's /etc/crypttab, for which I've trie= d various things is:
# cat crypttab
sdb3_crypt /dev/sdb3 none luks

I wonder whether my problem is related to which drive gets /dev/sd= x designation based upon which one booted.=A0 When booted on my usual/inter= nal drive and with /dev still bind-mounted (above), I have /mnt/RootRescue/= dev/sda and ..../sdc well populated.=A0 Nothing about sdb.=A0 When I try to= boot from the external drive, I get lots of sdb output (particularly if I = boot into "rescue" mode).=A0 Don't know if that helps any...<= br>
Thanks in advance for your assistance.

Cheers,
S

<= br>
=A0