Il giorno Tue, 12 Dec 2006 09:37:08 +0100 (CET) David Härdeman <[EMAIL PROTECTED]> ha scritto:
> On Mon, December 11, 2006 18:14, Enrico Gatto said: > > On Mon, 11 Dec 2006 10:59:24 +0100 (CET) > > David Härdeman <[EMAIL PROTECTED]> wrote: > > > >> could you please provide me with > >> .. > >> /etc/fstab, > > > > /dev/mapper/croot / ext3 defaults 0 1 > > > >> a list of your boot parameters > > > > /boot/boot/grub/menu.lst contains > > > > Just to be sure, you meant /boot/grub/menu.lst, right? No, it's /boot/boot/grub/menu.lst as in grub documentation when there's a separate boot partition mounted at /boot. Grub is working correctly. > > kernel /vmlinuz-2.6.18.2 root=/dev/evms/root quiet ro > > Could you please try to boot after changing the root parameter to > root=/dev/mapper/croot and let me know what happens? This works without evms, but evms script /usr/share/initramfs-tools/scripts/local-top/evms requires that ROOT is something as /dev/evms/* otherwise it exits without doing nothing. So cryptroot exits with cryptsetup: Source device /dev/evms/root not found The only thing that evms script does is to execute /sbin/evms_activate (that creates evms devices). So I think there are 2 possible solutions: - declare evms incompatible with cryptroot - patch cryptroot script so that it do the work of evms script. I think the second is better :-) I can figure out only 2 approaches: 1- change temporarily ROOT so evms script can be excecuted correctly (this solution is implemented in attachment cryptroot.patch1) 2- patch cryptroot script so that it executes /sbin/evms_activate if cryptsource is an evms volume, as it's done with lvm volumes (this solution is implemented in attachment cryptroot.patch2) Both resolve the problem and works correctly on my linux box with ROOT correctly set to /dev/mapper/croot. If you think one of the patches can be applied without problems then I think that you can close this bug report. > Did you set up the system yourself or did you do it using the crypto > support in debian-installer? I setted up it myself. debian-installer isn't able to make evms volumes AFAIK. > It seems your root parameter is wrong (it > should be the final root dev, i.e. the crypto dev, not the one that is > used to setup the crypto device). Yes, this was the problem on the box without evms. The fact is that on previous versions of cryptsetup the script was able to identify and set correctly ROOT to $crypttatget, so I didn't care it very much. But as previously said with evms the problem is a bit more complex.
cryptroot.patch1
Description: Binary data
cryptroot.patch2
Description: Binary data
signature.asc
Description: PGP signature
