> > BTW, this breaks policy (no upgrade-path from sarge to etch, assuming > > this version of lvm2 ever gets to etch - this bug should prevent > Why? Upgrading the kernel before is a valid path.
See discussions related to bug #317332. It seems there are more schools of
thought here. Some would like to have the ability to go back and forth
between no less than two kernel versions. I do not particularly care, I
just noted this by the way.
> > Kernel-image-2.6.15-1-686-smp has now been installed and system works
> > fine, except that when I do another upgrade, it now pulls the new lvm2
> > into place and after that it's not bootable. LVM2 no longer finds its
> > volume groups. Please bear in mind that the system has its root on
> > LVM2, to its really not usable at all.
> LVM don't call itself before init works, so you have a initrd which does
> the work for you.
Except that it does not. Like I said, it (LVM2) never finds the volume
groups, kernel panics and system will not boot. This all happens during
the boot following installation of newest LVM2. The initrd is loaded fine,
but whatever pieces of LVM ended up on the initrd are unable to find the
real root device and we all know what happens next.
Rebooting older kernel (2.6.12 in this case) still works, and also the
combination of old LVM and 2.6.15 works.
--
-----------------------------------------------
| Juha Jäykkä, [EMAIL PROTECTED] |
| home: http://www.utu.fi/~juolja/ |
-----------------------------------------------
pgp2pP0cvEDTc.pgp
Description: PGP signature
