Bug#355013: initramfs-tools: device mapper device ordering breaks boot (sometimes)
tags 355013 moreinfo stop On Sun, 16 Apr 2006, Christian Weeks wrote: On Sun, 2006-04-16 at 11:33 +0200, maximilian attems wrote: ok, adding discs works much better with grub. I know. I've used grub for non-LVM installations. But I also love the reorganizing convenience of LVM. Does grub now work with LVM roots then? This was the reason I used lilo (well, actually, debian-installer selected lilo for me, because I'd done an LVM root installation). I know of and loathe the /boot partition workaround (see RedHat)- it's nasty and uses up disk that I would like for other things. should be fixed with latest lilo that went into Etch. can you confirm? thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#355013: initramfs-tools: device mapper device ordering breaks boot (sometimes)
severity 355013 normal stop On Thu, 02 Mar 2006, Christian Weeks wrote: I use LVM on all my disks. I swapped an old laptop disk into another laptop for testing and my laptop now fails to boot normally but rather drops into the busybox. An analysis of this problem indicates that there are issues with LILO, the initramfs and/or the device mapper. Here's what appears to be happening. I run lilo, and (after spinning the CPU for about 30-60 seconds!) it deduces that my LVM disk cweekslap/root has id FE00 (I am not sure this is correct, however). So it spits this onto the command line. With a single disk in the laptop we will now boot correctly. I add in the second disk and at boot time, for some reason, the secondary disk (helenlap/home!) is now device FE00. Of course helenlap/home is not a valid root disk (it never was) and the system drops to busybox when it can't find init. I have recovered the situation temporarily with one of three fixes: 1. Use a boot parameter root=/dev/mapper/cweekslap-root 2. remount /dev/mapper/cweekslap-root at the /root mountpoint in the initram disk 3. recreate the /dev/root with mknod /dev/root b 254 2 ok, adding discs works much better with grub. lowering the severity as lilo is not default. but please become familiar with the carriage return on your keyboard and format mails to ~80 columns. can you paste your lilo.conf? Nothing is able to work permanently though. I can't make a lilo root= option stick- it turns into numbers. have you tried to use the append=root=/dev/mapper/cweekslap-root instead and without the root lilo.conf param? afaik that is the way that is recommended for evms on lilo too see end http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357538 sorry for the late reply regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#355013: initramfs-tools: device mapper device ordering breaks boot (sometimes)
On Sun, 2006-04-16 at 11:33 +0200, maximilian attems wrote: ok, adding discs works much better with grub. I know. I've used grub for non-LVM installations. But I also love the reorganizing convenience of LVM. Does grub now work with LVM roots then? This was the reason I used lilo (well, actually, debian-installer selected lilo for me, because I'd done an LVM root installation). I know of and loathe the /boot partition workaround (see RedHat)- it's nasty and uses up disk that I would like for other things. lowering the severity as lilo is not default. but please become familiar with the carriage return on your keyboard and format mails to ~80 columns. Evolution is stupid sometimes, my apologies. can you paste your lilo.conf? OK. Here it is. I've edited all the verbage from the installer. As you can see it's a vanilla lilo config generated by the installer. # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', boot=/dev/hda root=/dev/mapper/cweekslap-root map=/boot/map delay=20 vga=normal default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 initrd=/initrd.img image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 initrd=/initrd.img.old Nothing is able to work permanently though. I can't make a lilo root= option stick- it turns into numbers. have you tried to use the append=root=/dev/mapper/cweekslap-root instead and without the root lilo.conf param? afaik that is the way that is recommended for evms on lilo too see end http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357538 I have not. I will look into this. Thank you. I have another tentative solution that I will investigate as well when time permits. It appears that LVM allows you to make the minor node of a partition persistent. I shall see if I can use that to force the minor node of the root partition to zero. Thank you for your help, Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#355013: initramfs-tools: device mapper device ordering breaks boot (sometimes)
Package: initramfs-tools Version: 0.53 Severity: important I use LVM on all my disks. I swapped an old laptop disk into another laptop for testing and my laptop now fails to boot normally but rather drops into the busybox. An analysis of this problem indicates that there are issues with LILO, the initramfs and/or the device mapper. Here's what appears to be happening. I run lilo, and (after spinning the CPU for about 30-60 seconds!) it deduces that my LVM disk cweekslap/root has id FE00 (I am not sure this is correct, however). So it spits this onto the command line. With a single disk in the laptop we will now boot correctly. I add in the second disk and at boot time, for some reason, the secondary disk (helenlap/home!) is now device FE00. Of course helenlap/home is not a valid root disk (it never was) and the system drops to busybox when it can't find init. I have recovered the situation temporarily with one of three fixes: 1. Use a boot parameter root=/dev/mapper/cweekslap-root 2. remount /dev/mapper/cweekslap-root at the /root mountpoint in the initram disk 3. recreate the /dev/root with mknod /dev/root b 254 2 Nothing is able to work permanently though. I can't make a lilo root= option stick- it turns into numbers. Note that versions are probably wrong- this report is being filed from another machine. The actual machine setup is newly upgraded from sid yesterday, with stock 2.6.15 686 kernel and mkinitramfs as the ramdisk generator. Hope this helps, Thanks, Christian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-k8-1 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-10 GNU cpio -- a program to manage ar ii klibc-utils 1.2.2-3small statically-linked utilities ii udev 0.085-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
