Fwd: Bug#398957: lilo uses wrong root= parameter

Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org
Wed Dec 13 11:29:48 CET 2006


reassign 398957 lvm2
thanks

I made some more tests during the recent upgrade from kernel 2.6.17 to
2.6.18. I had the same problem as during last update.

I think that the problem is that vgscan creates devices with different
minor than the one used in the previous boot (with a different kernel).

I made these steps:

1. deleted all device files in /dev/.static/dev/mapper/
2. copied all device files from /dev/mapper/ to /dev/.static/dev/mapper
3. update kernel (this also update initrd and run lilo)
4. reboot

the boot did not worked, once again, because the root device was fd00 on
the previous boot, and is now fd01. So trying to mount fd00 as root did
not work.

In order to boot this machine, I had to specify root=fd01 at the lilo
prompt. This is shown by /proc/cmdline

casa:~# cat /proc/cmdline
BOOT_IMAGE=linux ro root=fd00 root=fd01
casa:~#

I am now inclined in thinking the problem is about vgscan/vgmknodes. So
I am reassigning this bug to lvm2.

Bye,
Giuseppe




More information about the pkg-lvm-maintainers mailing list