Package: lilo Followup-For: Bug #398957
Hello, first sorry for my little bad english. After dist-upgrading vom sarge to etch i could not boot the new etch kernel 2.6.18-4-k7. I run always into the busybox cause the LVM isn't activated. My root device is on an LVM-LV. With the old sarge kernel i don't have the problem (2.6.8-3-k7) I mailed with a guy from LVM2 team and we find a cause. Booting the new kernel always failed when the root= in lilo.conf is positioned either in the main section or in the image section. Booting the new kernel works when putting the root= parameter in the append line of this image. Here my lilo.conf (shortened, only for explain) Don't work: boot=/dev/hda root=/dev/mapper/vg1-lv1 image=/vmlinuz label=Linux initrd=/initrd.img append="rootdelay=9" Don't work: boot=/dev/hda image=/vmlinuz label=Linux initrd=/initrd.img root=/dev/mapper/vg1-lv1 append="rootdelay=9" Work: boot=/dev/hda image=/vmlinuz label=Linux initrd=/initrd.img append="rootdelay=9 root=/dev/mapper/vg1-lv1" It seems, that in the non working situations lilo transmit some "silly" information about the root device. Running in the busybox we found some information which may be usefull for you: cat /proc/cmdline auto ROOT_IMAGE=Linux ro root=fe00 rootdelay=9 ls -l /dev/mapper/vg1-lv1 brw-rw---- 1 0 6 254, 1 Apr 13 07:32 /dev/mapper/vg1-lv1 ls -l /dev/root brw------- 1 0 0 254, 0 Apr 13 07:32 /dev/root And here this friend found the solution to put root= in the append line. He mentioned that lilo give a faulty root= (not root=fe06). lilo thinks that root is on major 254 and minor 0 but the real root device has major 254 and minor 6 I hope this information help for maybe fixing this. The original bug report is already a little old but i think i could add mine here. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-3-k7 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Versions of packages lilo depends on: ii debconf 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libdevmapper1.02 2:1.02.08-1 The Linux Kernel Device Mapper use ii mbr 1.1.9-2 Master Boot Record for IBM-PC comp lilo recommends no packages. -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/liloconf_incompatible: lilo/bad_bitmap: liloconfig/use_lba32: true lilo/upgrade: liloconfig/liloconf_exists: liloconfig/configuring_base: lilo/runme: false liloconfig/use_current_lilo: true liloconfig/wipe_old_liloconf: false liloconfig/instruction: liloconfig/activate_error: liloconfig/select_bitmap: /boot/coffee.bmp liloconfig/lilo_error: lilo/new-config: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/install_mbr: false liloconfig/no_changes: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
