Bug#505613: Kernel unable to mount file system and to execute init

2008-11-14 Thread Xavier Brochard
Le vendredi 14 novembre 2008 17:02:41, vous avez écrit : > On Fri, Nov 14, 2008 at 02:54:05PM +0100, Xavier Brochard wrote: > > Le vendredi 14 novembre 2008 12:48:05 Debian Bug Tracking System, vous > > avez > > > > > Device number for lvm is not stable. Don't even try to use it. No bug > > > in th

Bug#505613: closed by Bastian Blank <[EMAIL PROTECTED]> (Re: Bug#505613: Kernel unable to mount file system and to execute init)

2008-11-14 Thread Bastian Blank
On Fri, Nov 14, 2008 at 02:54:05PM +0100, Xavier Brochard wrote: > Le vendredi 14 novembre 2008 12:48:05 Debian Bug Tracking System, vous avez > > Device number for lvm is not stable. Don't even try to use it. No bug in > > the kernel or initramfs as you have to provide a proper device _name_ or >

Bug#505613: closed by Bastian Blank <[EMAIL PROTECTED]> (Re: Bug#505613: Kernel unable to mount file system and to execute init)

2008-11-14 Thread Xavier Brochard
Le vendredi 14 novembre 2008 12:48:05 Debian Bug Tracking System, vous avez écrit : > On Thu, Nov 13, 2008 at 09:33:27PM +0100, Xavier Brochard wrote: > > cat /proc/cmdline: > > BOOT_IMAGE=Linux ro root=fd00 > > (which is correct, Lilo -q -v5 shows me that 0xFD00 is /dev/debian/root) > > Device nu

Bug#505613: Kernel unable to mount file system and to execute init

2008-11-13 Thread Xavier Brochard
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-9 Severity: critical I've downgraded my kernel from 2.6.26-10 to 2.6.26-9 after the system became unbootable (see bug report #505609). Now the system boot, but stop before mounting the file system and executing init. See below for the output.