https://bugzilla.novell.com/show_bug.cgi?id=406554 User heiko.schroeder@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406554#c6 Heiko Schröder <heiko.schroeder@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heiko.schroeder@t-online.de --- Comment #6 from Heiko Schröder <heiko.schroeder@t-online.de> 2008-07-12 04:09:02 MDT --- I have exactly the same problem and want to provide a few additional observations: The setup-lvm2.sh script checks if any of the blockdevices needed for the root filesystem or for resume are using LVM2. If yes, it sets the root_lvm2 flag and adds the volume groups to vg_roots. The root_lvm2 flag will make the boot-lvm2.sh script check if the root filesystem is on LVM2. If yes, it sets vg_root the volume group. If vg_root OR vg_roots is set, it will then set root_major to the major device number of the device mapper. This will make the check_for_device functions check not only if the device for the root filesystem exists but additionally if it has the "correct" major number. In this case, thiw will oviously never happen as the root filesystem is not on LVM2. I think, there are two possible solutions to the problem: 1. fix setup-lvm2.sh to set the root_lvm2 flag only if the root system is really on an LVM2 disk 2. let boot-lvm2.sh set root_major only if vg_root is set. This should only happen if the root filesystem is really on an LVM2 device (Of course, solution 1 seems to be the cleaner one, though solution 2 should solve the problem equally well, if my observations are correct.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.