Bug 600853

Summary:	Installer fails to mount LVM volumes after creation
Product:	[openSUSE] openSUSE 11.3	Reporter:	Sascha Peilicke <sasch.pe>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P0 - Crit Sit	CC:	aschnell, forgotten_1-yzHWP3HO
Version:	Factory
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 logs that remain after installation y2log file just after failure

Description Sascha Peilicke 2010-04-29 10:51:19 UTC

User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.2 (like Gecko) SUSE

The installer fails to mount LVM logical volumes on an encrypted physical   
volume after setting up the (custom LVM) partition layout and thus fails to 
install root image.

The layout was as the following

sda4 (extended part)
 sda5 100MB ext4 /boot (format)
 sda6 170GB Linux LVM  (encrypted)

LVM setup:

 physical volume on sda6
 logical volume 'lv_swap'  swap   (format)
 logical volume 'lv_root'  ext4 / (format)

Tested on openSUSE-KDE-LiveCD-x86_64-Build0577-Media.iso

Reproducible: Always

Steps to Reproduce:
1. Create custom LVM layout as described
2. Continue with the installer
3.
Actual Results:  
Root image can't be installed because mount failed

Expected Results:  
Mount should work after partitioning

Comment 1 Arvin Schnell 2010-04-29 12:12:47 UTC

Please provide YaST logs, see http://en.opensuse.org/Bugs/YaST.

Comment 2 Sascha Peilicke 2010-04-29 12:55:53 UTC

Created attachment 357754 [details]
YaST2 logs that remain after installation

Those are the logs that are found after successful installation. Their usefulness may be limited because I had to use a different disk layout.

Comment 3 Arvin Schnell 2010-04-29 13:12:43 UTC

Those logs are unfortunately useless.

This could be a duplicate of bug #598193 but without logs I cannot say
for sure.

Comment 4 Forgotten User 1-yzHWP3HO 2010-05-14 09:51:23 UTC

I also experiecd the same behaviour with milestone 6, kde live being installed on an EEEPC901. 

What happens is that a normal setup (partitioned as proosed by the installer) works fine.

The installer trips with "Failure occurred during folowing action: Mounting /dev/system/root to /, system error code was -3030. (it will also fail for the other 7 lv's I created)

Went to vc 0 and was not able to mount /dev/system/root to /mnt. Also found out that: 

1) pvdisplay shows the pv.
2) vgdisplay shows also the vg 'system'
3) lvdislay /dev/system/root shows the stats as being unavailable

/dev/system/root is not available

vgchange -a y reports that the 8 required volumes are now active

/dev/mapper/system-root and /dev/system/root are not there.

I'll attach /var/log/YaST2/y2log


ps this is on X86 platform, not 64 bit specific

Comment 5 Forgotten User 1-yzHWP3HO 2010-05-14 09:56:59 UTC

Created attachment 362265 [details]
y2log file just after failure


this is afaik, the required information. It's the file just after the first failure occurs. 

It will also fail on the other 7 LV's and it repeatedly will fail each time you ty to install.

Basically a showstopper.

Comment 6 Arvin Schnell 2010-05-14 10:16:21 UTC

Thanks for the logs. Looks indeed as a duplicate of bug #598193.

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

Comment 7 Forgotten User 1-yzHWP3HO 2010-05-14 11:09:15 UTC

thx.  ps,add info:


as in previous post mentioned -- I did a vgchange -a y and now after a restart of the live iso, the lv's are available.

At this point, I had to re-edit the mountpoint points for local, srv, usr, var and tmp and again selected 'format and disable atime (it's a flash disk)

After formatting, it again fails with unable to mount the root filesystem. The lv's again are unavailable

vgchange -a y leaves the lv's unavailable.

Will continue looking at the other # 598193