Hi, I had the same problem when upgrading to a newer (custom) kernel version on debian. I'm using a physical encrypted harddisk partition where LVM2 with my partitions (including root) reside in. After debugging the initrd.img I created with mkinitrd I found out that it creates an initrd.img with devfs. Since my newer kernel (2.6.16) does not support devfs, cryptsetup could not find /dev/mapper/control and failed with the same message "Command failed: Incompatible libdevmapper 1.02.03 (2006-02-08)(compat) and kernel driver". Also ensure that /proc is mounted. (If that solution doesn't work for you, you might consider including strace in your initrd. It will help you debugging cryptsetup and hopefully allow you to determine the error.) I then used mkinitramfs to create the initial ramdisk which worked just fine for me, though I had to write some hooks and additional scripts until it worked. (mkinitramfs doesn't have cryptsetup support for now). I'm considering to update my wiki entry at http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedLVM2Root to include the mkinitramfs solution.. I guess that the error VFS: Can't find ext3 filesystem on dev dm-0." is normal if your root device is not ext3 (I get the same "error"). IMHO the kernel tries different filesystems to mount the root filesystem. If you have reiserfs on your root device (like me) it will first try to mount root with ext3, if that fails it tries to mount it with reiserfs or other filesystems. Though my problems were slightly different to yours, I hope that I could help ;) greets, Stefan On Thu, 27 Apr 2006 14:11:53 +0200 "Mailings'AT'netzwerk.cc" <mailings@xxxxxxxxxxx> wrote: > Hi, > > I've got a few problems with my 2 crypt harddrives. > > First, what I am doing after boot and what happens: > > modprobe aes > modprobe dm-crypt > modprobe dm-mod > > mount /dev/sdc /mnt/key/ > > gpg --decrypt /mnt/key/harddisk.gpg|cryptsetup -s 128 create crypt1 > /dev/hde1 > > mount /dev/mapper/crypt1 -t ext3 /crypt1 > > Then I've got: > > "VFS: Can't find ext3 filesystem on dev dm-0." > > And that's true. fdisk show's nothing inside. > > So I am reverting: > > umount /crypt1 > cryptsetup remove /dev/mapper/crypt1 > dmsetup remove_all > rmmod -f dm_crypt > rmmod -f dm_mod > > and get a: > > "Command failed: Incompatible libdevmapper 1.02.03 (2006-02-08)(compat) > and kernel driver" > > I am using Debian with various kernel versions. > > One thing left: > > cryptsetup status control > /dev/mapper/control is inactive. > > Anyone have got a hint ? > > Thanks > > Sven --------------------------------------------------------------------- - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
