reassign 521343 lilo
forcemerge 520645 521343
thanks Bastian
signature.asc
Description: This is a digitally signed message part.
Processing commands for cont...@bugs.debian.org:
> reassign 521343 lilo
Bug#521343: Can't repair a lilo+root-on-LVM system
Bug reassigned from package `general' to `lilo'.
> forcemerge 520645 521343
Bug#520645: linux-image-2.6.26-1-amd64: after update, system doesn'
On Thu, Mar 26, 2009 at 10:36:39PM +0200, Eddy Petrișor wrote:
> After reboot I was surprised to see the boot process failing and
> dropping me in the initrd shell. More investigation and hours later I
> realised that inside the initrd /dev/root was created with major
> number 253 while the root LV
Hi Eddy,
On Freitag, 27. März 2009, Eddy Petrișor wrote:
> I agree this was user error. Still, recovering from it should be possible.
> That's what the BR is about.
Well, the problem seems to be that your kernel was installed incorrectly...
> How is it user error when I try to update the initram
Holger Levsen a scris:
> Hi Eddy,
>
> On Donnerstag, 26. März 2009, Eddy Petrișor wrote:
>> Two days ago after upgrading the lenny 2.6.26-1-686 kernel I didn't
>> shut down the system, I put it in hibernate. The next day, when I
>> powered the computer, it failed to boot right after loading the ke
Hi Eddy,
On Donnerstag, 26. März 2009, Eddy Petrișor wrote:
> Two days ago after upgrading the lenny 2.6.26-1-686 kernel I didn't
> shut down the system, I put it in hibernate. The next day, when I
> powered the computer, it failed to boot right after loading the kernel
> and checking the BIOS wit
Package: general
Severity: important
Hello,
Sorry for the general bug, but I can't really say which is the
appropriate package in this case.
Two days ago after upgrading the lenny 2.6.26-1-686 kernel I didn't
shut down the system, I put it in hibernate. The next day, when I
powered the computer,
7 matches
Mail list logo
