Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten
> <valentijnscholten@hotmail.com> wrote:
>> Hello Luke,
>> Thanks for jumping in.
>> I only have a /boot/initrd.img-2.6.32-5-amd64 at the moment.
>> This is the one probably generated (reinstalled) after I reinstalled Squeeze
>> on top of the existing problematic install.
>
>  ah.  _drat_.  that's exactly what i did, and it overwrote...
>
>> There's no initrd img for 2.6.39, there's the kernel image itself however.
>
>  oh wait... let me get this straight: there's *no* 2.6.39 initrd??
>
>  so, let us be clear: you installed 2.6.39-bp0.2-amd64 and yet there
> is no file /boot/initrd-2.6.39-bp0.2-amd64 to match??


 so - let's repeat the steps.  could you confirm, yes or no, that you
took the following steps, and/or correct them if necessary:

 * you installed debian, which gave you a 2.6.32-5-amd64 kernel
 * you installed backports linux-image-2.6.39-bp0.2-amd64
 * 2.6.32 was removed (due to a conflict with 2.6.39-bp0.2) during the install
 * you booted up and got that "Kernel Panic, unknown <0-0>"
 * you got a CD and booted up Squeeze
 * you REINSTALLED 2.6.32 (Squeeze) on top
 * you DID NOT do anything else (specifically DID NOT touch the 2.6.39 kernel)

now.

could you please describe the exact steps involved in what you say
"you reinstalled squeeze on top of the existing problematic install"?

as in: could you please describe the commands that you did?  did you
just boot up from the CD and then do "apt-get install
linux-image-2.6.32-5-amd64" or... what did you do?

 i want to know why the heck it is that there is a 2.6.39 kernel but
no corresponding initrd, because that is, i believe, exactly what
happened to me (except i went and "recovered" my system and of course
cannot now repro it).

 l.