Bug 508109

Summary: Can't boot from LVM partition (Milestone 2)
Product: [openSUSE] openSUSE 11.2 Reporter: Piotrek Juzwiak <piotrek.juzwiak>
Component: BasesystemAssignee: E-mail List <bnc-team-screening>
Status: VERIFIED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P1 - Urgent CC: piotrek.juzwiak
Version: Milestone 1   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Piotrek Juzwiak 2009-05-29 10:12:37 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4) Gecko/20090426 SUSE/3.5b4-7.1 Firefox/3.5b4

Can't boot to a LVM root partition. System has been set on the same volume group as openSUSE 11.1 which boots fine. The boot partition has been installed on a separate /boot partition with ext2 filesystem. GRUB has been installed on MBR.

While booting i get such informations:
"mkdir: cannot create dir '/dev/mapper': File exists
mknod: '/dev/mapper/control': File exists
creating device nodes with udev
udevd-event[362]:device node '/dev/mapper/control' already exists, link to '/dev/device-mapper' will not overwrite it

After that system waits for the root partition named /dev/SYSTEM/ROOT_FACTORY

After waiting for some time it wants to fall back to the same device which is unsuccesfull.
After waiting time i get to the busy box?

openSUSE 11.1 is installed on the same volume group (/dev/SYSTEM/) and boots fine. 

P.S. I tried to create "fresh" volume group to install on but it still doesn't work

Reproducible: Always

Steps to Reproduce:
1.Set root partition to a LVM based partition
2.Try to boot
3.
Actual Results:  
System is waiting for the logical volume to become active which never happens

Expected Results:  
System should boot fine :)??
Comment 1 Piotrek Juzwiak 2009-05-29 10:13:36 UTC
I'm using Milestone 2 but it is of course prior to that
Comment 2 Piotrek Juzwiak 2009-05-30 10:22:12 UTC

*** This bug has been marked as a duplicate of bug 505670 ***