[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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??

 btw also - you mentioned "2.6.38" - i assume (given the listings
you've shown below) - i assume that you meant "2.6.39", is that
correct?

> root@NAS2:/boot# ls -l
> total 19460
> -rw-r--r-- 1 root root   106088 Mar  8 01:18 config-2.6.32-5-amd64
> -rw-r--r-- 1 root root   124738 Jul 26 14:02 config-2.6.39-bpo.2-amd64
> drwxr-xr-x 3 root root     4096 Aug 22 00:32 grub
> -rw-r--r-- 1 root root 10977315 Mar 24 08:24 initrd.img-2.6.32-5-amd64
> -rw-r--r-- 1 root root  1662514 Mar  8 01:18 System.map-2.6.32-5-amd64
> -rw-r--r-- 1 root root  1887188 Jul 26 14:02 System.map-2.6.39-bpo.2-amd64
> -rw-r--r-- 1 root root  2418720 Mar  8 01:12 vmlinuz-2.6.32-5-amd64
> -rw-r--r-- 1 root root  2691792 Jul 26 13:59 vmlinuz-2.6.39-bpo.2-amd64
>
> I don't understand how the initrd.img-2.6.32-5-amd64 might help, but I can
> upload it somewhere. just tell me where.
>
> I might be able to reproduce the problem by installing the 2.6.39bpo again,
> but first I have to find out how to do that,

 well, that's exactly what i did, and, by doing so, i found that it
was then *NOT* possible to reproduce the problem.

 so please do not do anything right now! :)  unless you have a
completely unusable system of course

 so it would appear that the problem is that initramfs-tools is *NOT*
generating the initrd file!

 l.



Reply to: