Bug 521367

Summary: openSUSE 11.2 M3 installs, but fails to boot (root filesystem on LVM not found)
Product: [openSUSE] openSUSE 11.2 Reporter: Christian Esken <christian.esken-services>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: brunno, piotrek.juzwiak
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Christian Esken 2009-07-12 13:44:14 UTC 
Hello,

I have installed openSUSE 11.2 Milestone 3 (tested both x86-64 and x86). It installs - the installation is distributed on the HD like this:

Device                       Mountpoint
/dev/sda                     /boot
/dev/mapper/system-SUSE112   /


At the end a dialog box is shown that the machine will be rebooted. The reboot takes place, but hangs very quickly.
The boot process (partly) initializes USB, and during that waits for /dev/mapper/system-SUSE112 to appear. There is no
logfile I could copy/paste from, so I did a screenshot, and typed the interesting part:

------------------------------------------------------------
doing fast boot
mkdir: cannot create directory `/dev/mapper': File exists
[...]
Waiting for device /dev/system/SUSE112 to appear: ...............................Could not find /dev/system/SUSE112.
Want me to fall back to /dev/system/SUSE112? (Y/n)
------------------------------------------------------------

If I boot my regular openSUSE 11.1, I see that /dev/system/SUSE112 exists, and I can mount /dev/mapper/system-SUSE112 without problems.


firefly:~ # ll /dev/system/SUSE112
lrwxrwxrwx 1 root root 26 Jul 12 14:58 /dev/system/SUSE112 -> /dev/mapper/system-SUSE112
firefly:~ # mount | grep SUSE112
/dev/mapper/system-SUSE112 on /root/112 type ext3 (rw)


  Christian
Comment 1 Piotrek Juzwiak 2009-07-29 00:06:59 UTC 
It has been fixed in M4. I had the same problem and i can confirm that this has already been fixed. Thank You
Comment 2 Christian Esken 2009-08-04 21:45:19 UTC 
I confirm that it also works for me in M4.
Comment 3 Brunno Prego 2009-09-16 16:54:37 UTC 

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