Hi...
I'm comming with news that might explain things...
First I've diffed the initrds on the two machines I talked about in my
initial report...
The one that breaks is "1" and the one that works is "2"...
I attach the diff file...
Another interesting detail is dpkg -l lvm\*...
On
reassign 291386 initrd-tools
thanks
On Thu, Jan 20, 2005 at 02:17:34PM +0100, Eric Deplagne wrote:
> Package: kernel-image-2.4.27-2-686
> Version: 2.4.27-7
> Severity: critical
> Justification: breaks the whole system
>
> When the install of kernel-image tries to create initrd,
> those lines go t
Processing commands for [EMAIL PROTECTED]:
> reassign 291386 initrd-tools
Bug#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2
setup
Bug reassigned from package `kernel-image-2.4.27-2-686' to `initrd-tools'.
> thanks
Stopping processing here.
Please c
reassign 291386 initrd-tools
thanks
On Thu, Jan 20, 2005 at 02:17:34PM +0100, Eric Deplagne wrote:
> Package: kernel-image-2.4.27-2-686
> Version: 2.4.27-7
> Severity: critical
> Justification: breaks the whole system
>
> When the install of kernel-image tries to create initrd,
> those lines go t
Package: kernel-image-2.4.27-2-686
Version: 2.4.27-7
Severity: critical
Justification: breaks the whole system
When the install of kernel-image tries to create initrd,
those lines go to /var/log/messages:
Jan 20 09:39:39 fregate kernel: device-mapper: unknown block ioctl 0x801c6d02
Jan 20 09:39:4
5 matches
Mail list logo