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
Reply to: