Christian Weeks wrote:
> Yup. That worked a treat.
>
> Thanks!
>
Great, I'll upload that one then.
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Yup. That worked a treat.
Thanks!
Christian
On Wed, 2005-05-25 at 09:04 +0100, Patrick Caulfield wrote:
Thanks. Can you try the updated package on http://people.debian.org/~patrick/ please?
--
Christian Weeks <[EMAIL PROTECTED]>
Thanks. Can you try the updated package on http://people.debian.org/~patrick/
please?
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Patrick,
I've verified my recreation of the problem.
You can find working and non-working initrd images in
http://weeksfamily.ca/lvmproblem/
There's also a package report showing the status of relevant packages.
The only difference between the working and the non-working is the
upgrade (well, d
Christian Weeks wrote:
> Hmm, I've regenerated a working one now... When I was examining it, it
> did have vgchange contained within it, and also another vgchange under
> /lib/lvm-200/ (or something similar)... I figured that one of the
> scripts was somehow choking when it tried to execute the vgc
Hmm, I've regenerated a working one now... When I was examining it, it did have vgchange contained within it, and also another vgchange under /lib/lvm-200/ (or something similar)... I figured that one of the scripts was somehow choking when it tried to execute the vgchange executable in the ini
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
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.
8 matches
Mail list logo