After I finish work this evening (about 10 hours from now) I'll build and test that it's broken a broken one, for your perusal.. Is that OK?
Thanks,
Christian
On Tue, 2005-05-24 at 07:54 +0100, Patrick Caulfield wrote:
Christian Weeks wrote: > Package: lvm-common > Version: 1.5.18 > Severity: critical > Justification: breaks the whole system > > > I ran an upgrade this morning and picked up this package, among others, > including a new kernel image. This generated a new initrd which rendered > my "Root on LVM" system unbootable into the new kernel. Fortunately, I > had a recovery kernel on hand that still worked. > > After some frantic recovery work, I have determined that rolling back > lvm-common to 1.5.17 enables the generation of an unbroken initrd that > can be booted. > > The error reported during the boot process is "No program "vgchange" > exists for your LVM version". Root is unmountable and the kernel panics > shortly afterward. > > Frankly, this is a bit of a surprise- I didn't think this particular > package would be the problem cause. > > Sorry to create an RC bug, but this almost hosed my system completely > and my guess is it will break anyone who uses lvm on root after a kernel > upgrade. > So your initrd doesn't contain vgchange! hmmm. How ws the initrd generated and can you send me it please ?
-- Christian Weeks <[EMAIL PROTECTED]> |