[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



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.
There's no initrd img for 2.6.39, there's the kernel image itself however.

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,
while keeping the old kernel available and bootable from grub.
Any other things I need to do (different) to be able to analyse things for you guys?

-----Original Message----- From: Luke Kenneth Casson Leighton
Sent: Monday, August 22, 2011 7:56 PM
To: Jonathan Nieder ; 636123-quiet@bugs.debian.org
Cc: Valentijn Scholten ; 636123-submitter@bugs.debian.org ; initramfs-tools@packages.debian.org Subject: Re: Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

Valentijn, this is very important:

please can you keep and make available the initrd that was generated
by initramfs-tools?

the file is going to be /boot/initrd.img-2.6.38-2-{insert_arch_name}

DO NOT attempt to "recover" the system right away (unless you take a
backup of /boot/initrg.img-2.6.38-2-{insert_arch_name} first)

right now you have a system which is "correctly faulty" and have
managed to make a repro-case for a bug which was first discovered two
weeks ago.

it is very very important, to determine the problem, that you make
available that (faulty) initrd.

are you able to upload it somewhere?  i can make available an ftp
server if you need one.

l.




Reply to: