On my local system i ran i root encyrpted system with kernel 3.0-0.slh.5 (64bit) successful.
I installed 3.0-0.slh.7 on my server (32bit) (including dropbear to decrypt lvm remote), but when asking for password following messages are displayed
could not determine kernel version used
cannot initialize device mapper. is dm_mod kernel module loaded?
typing password local is not succesful ("bad password").
trying to type it remote dropbear asks for a root password where it uses keyfiles.
Booting a old kernel is still working.
edit: remote uncrypting is also on old kernel defect. probaly another problem. please ignore it.
edit2: this happend after a d-u. The last d-u was with kernel 2.6.39-0.slh.3-aptosid-686
Last edited by gerd on 04.08.2011, 12:57; edited 1 time in total
I can guess at the problem, did you just install the kernel on the system with the problem and not do a full d-u and is this the first 3.0 kernel it has seen? In that case the problem is that you (at least) don't have the fixed dmsetup package.
I did a d-u and it first the first 3.0 kernel. Last d-u was about 2 months ago. I have the standard dmsetup package installed.
I tried also to put dm_mod into
/etc/initramfs-tools/module (and update-initramfs) but without success. I cant decrypt the partition at boot (so i can't boot) with kernel 3.0 while it works with kernel 2.6.39