[Pkg-cryptsetup-devel] Bug#428329: Bug#428329: Bug in debian-Installer/initramfs when I use "GUID Partition Table (GPT)" with a crypted root filesystem

[Jonas Meurer]

On 25/11/2007 Max Vozeler wrote:
> quoting from #428329:
> > ...
> > 
> > Setting up cryptographic volume sda3_crypt (based on /dev/sda3)
> > Enter LUKS passphrase: _  <-- I give the passphrase here
> > key slot 0 unlocked.
> > Command successfull.
> > Done.

At least cryptsetup seems to successfully setup the dm-crypt root device.

> > /init: /init: 1: cannot open /dev/root: No such device or address
> > Begin: Running /scripts/lcoal-premount ...
> > Done.

I guess that this is a typo by the original bug submitter. lcoal-premount
should be rather local-premount here.

> > Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] [-o <modname>]
> > [ --dump-modversions ] <modname> [parameters...]
> > modporobe -r [-n] [-i] [-v] <modulename> ...
> > modprobe -l -t <dirname> [ -a <modulename> ...]
> > mount: Cannot read /etc/fstab: No such file or directory

This all happens because the rootfs is not mounted at all. So the
question here is, what exactly tries (and fails) to mount /dev/root?

I guess that some configuration script at installation simply ignored
the fact that the rootfs is encrypted, and instead of the dm-crypt root
device (like /dev/mapper/root) added /dev/root to /etc/fstab.

David, you have better knowledge of the whole installation process, what
do you think about that?

greetings,
 jonas