Bug#505613: Kernel unable to mount file system and to exec..

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.

The system is entirely on LVM. Partitions comes from the same Volume Group:
/ (root file system)
/tmp
/usr
/var
/home
/usr/local
swap
/media/empty

While the system was unbootable (see bug report #505609), I've used the rescue
mode of the Debian installer CD-ROM to boot, to mount the root and the /var
partitions (and also /proc et /sys) and reinstall the package linux-
image-2.6.26-1-amd64-2.6.26-9.deb (which was still on the hard drive). There
was no errors in the output.
I've rebooted, Lilo launch the new kernel, as slow as before (see my bug
report 505579), the kernel boot and failed to mount filesystem and execute
init. Here's the output:
---------
Begin: Mounting root file system... Begin: Running /scripts/local-top...
[ 6.588232] device-mapper: uevent: version 1.03
[ 6.588970] device-mapper: ioctl: 4.13.0-ioctl (2007-10-1 initialized: dm-
devel DeleteThis @redhat.com
8 logical volume(s) in volume group "debian" now active
done.
Begin: Running /scripts/local-premount... kinit: name_to_dev_t
(/dev/mapper/debian-swap) = dm-5 (254,5)
kinit: trying to resume from /dev/mapper/debian-swap
[ 6.819292] PM: Starting manual resume from disk
kinit: no resume image, doing normal boot...
resume: libgcrypt version 1.4.1
done.
mount: mounting /dev/root on /root failed: No such device
Begin: Running /scripts/local-bottom... done.
done.
Begin: Running /scripts/init-bottom... mount: mounting /dev on /root/dev
failed: No such file or directory
done.
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: no such file or directory
Target file system doesn't have /sbin/init
No init found. Try passing init=bootarg.
-----
Then I got a shell in the initrd image.

cat /proc/cmdline:
BOOT_IMAGE=Linux ro root=fd00
(which is correct, Lilo -q -v5 shows me that 0xFD00 is /dev/debian/root)


I've rebooted the system using Debian installer, and tried to:
reinstall kernel
run mkinitramfs
run lilo
but nothing change after that.

please tell me if you need more informations.

regards
--
Xavier
xavier DeleteThis @alternatif.org



--
To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

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 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
> uuid.

Thanks for the explanation.
I didn't use device number. Actually /etc/lilo.conf contain:
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/mapper/debian-root

I was very surprised to see the content of /proc/cmdline and checked also in
/etc/initramfs-tool/* and /etc/lvm/* files (found nothing related).

I'm sorry I should have provide more informations, but I was unable to access
the hard drive. I've just finish to install another system on the hard drive
and can access it now (my DSL live CD couldn't). Tell me if you need more
informations (log files, etc.).

Please reopen the bug.
regards
--
Xavier
xavier RemoveThis @alternatif.org



--
To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org