Bug#293508: initrd-tools refuses to make an initrd when lvm support is compiled, in the kernel
maximilian attems wrote:
On Fri, 04 Feb 2005, Benedict Verheyen wrote:
I'm trying to switch from a 2.4.24 kernel to a 2.6.10 kernel and
in the process go from lvm1 to lvm2. My root is also on lvm.
When i compile a kernel with lvm2 in it, so no dm-mod to be found,
mkinitrd refuses to build an initrd saying "Kernel does not support LVM".
If i set lvm2 as module, then it makes an initrd.
root@arthur# mkinitrd -o initrd.img-2.6.10.03feb2005-skas3-v7 -r
/dev/main/lv_root 2.6.10.03feb2005-skas3-v7
/usr/sbin/mkinitrd: /dev/mapper/main-lv_root: Kernel does not support LVM
root@arthur# grep "DM" /boot/config-2.6.10.03feb2005-skas3-v7
...
CONFIG_BLK_DEV_DM=y
...
well initrd makes only sense for modularized kernels,
why are you at all building an initrd?
i'm very enclined to close that bug.
As stated in my explanation above, my root is also on LVM and then you
need an initrd in order to be able to get to /.
Somebody on the debian-user list said the mkinitrd script probably has an
error when checking for lvm2. It would be nice if this could be fixed.
there was some work on it lately,
could you specify to which bug you encountered,
opening a separate bug report would be great too.
thanks for your feedback.
I discussed it with a person name Pigeon. He seemed rather knowledgeable
about lvm and he helped me a lot. The thread went on debian-user and is
titled "switch from 2.4.24 lvm1 to 2.6.10 lvm 2 problems".
It can be found here:
http://lists.debian.org/debian-user/2005/02/msg00327.html
He (pigeon) succeeded in upgrading his woody from a lvm1/kernel 2.4.x
setup to a lvm2/kernel 2.6.x setup. His page contains a lot of good info:
http://pigeon.dyndns.org/stuff/lvm-root/lvm-root.html
About the error: basically when you compile the lvm support into the
kernel and don't use modules, the mkinitrd script said something like this:
/usr/sbin/mkinitrd: /dev/mapper/main-lv_root: Kernel does not support LVM
When i left lvm support as a module, it didn't give an error.
For the record, i still haven't managed to get a 2.6 kernel booting
after several days on end of trying and i'm going to move all my
partitions off lvm and then try to get a 2.6 kernel booting. There might
be other problems on my disk although everything has been running nicely
for over 2 years.
--
Benedict Verheyen Debian User
http://www.heimdallit.be Public Key 0x712CBB8D
Reply to: