On Thu, Apr 07, 2005 at 12:05:31PM +0200, Eric Deplagne wrote: > On Tue, 05 Apr 2005 11:28:22 -0700, Steve Langasek wrote:
> > I've tried to pin down this bug, but I find that the current version of > > initrd-tools builds correct (matching) initrds whether or not the lvm10 > > package is installed. Is it possible that the broken initrd was built with > > an old version of initrd-tools, or was somehow built on a system that did > > not have lvm2 installed? Can you still recreate this broken initrd problem > > if you install lvm10 on the system? What version of initrd-tools do you > > currently have installed? > It does occur all the same for me with initrd-tools 0.1.77... Hmm. > Do you have the root filesystem on lvm2 ? Yes, of course; there's no reason to expect any lvm support in the initrd otherwise. > I attach the output of "diff -rub /mnt/initrd1 /mnt/initrd2", > with on /mnt/initrd1 a mount of the initrd without lvm10, > and on /mnt/initrd2 a mount of the initrd with lvm10 > I also verified that the initrd with lvm10 still does not boot my box > properly... Ok, got it -- this is only a problem with 2.4 kernels, where lvm-mod.o is available, and did not happen when testing against a 2.6 kernel. Now to figure out how to fix the check, so that it can distinguish between a volume that requires lvm2 and one that works with lvm1. Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
