Bug 157878 - YaST2 LVM - LVM configuration (created during installation) is not detected
Summary: YaST2 LVM - LVM configuration (created during installation) is not detected
Status: RESOLVED DUPLICATE of bug 153573
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-14 09:43 UTC by Lukas Lipavsky
Modified: 2006-03-14 19:07 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
yast logs (2.57 MB, application/x-gzip)
2006-03-14 09:44 UTC, Lukas Lipavsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Lipavsky 2006-03-14 09:43:47 UTC
During the installation I setup LVM for / (boot is on separate partition). The system boots an works without any problem, but if I start yast lvm it behaves like there's no lvm present and tries to create new volume groups etc. Therefore I'm unable to work with the real LVm setup (resizing, ...)

PS. I'm not skilled lvm user so please tell me what logs/setting etc. should I attach to describe it better.

I changed nothing related to lvm since the installation.

fstab:
/dev/system/sl10.1-root /       reiserfs        acl,user_xattr 1 1
/dev/sda5       /boot   ext2    acl,user_xattr 1 2
/dev/sda1       swap    swap    defaults 0 0
proc    /proc   proc    defaults 0 0
sysfs   /sys    sysfs   noauto 0 0
usbfs   /proc/bus/usb   usbfs   noauto 0 0
devpts  /dev/pts        devpts  mode=0620,gid=5 0 0

But in yast partition manager there's different information for root:
device: /dev/dm-0
Type: DM
Mount: /
Comment 1 Lukas Lipavsky 2006-03-14 09:44:56 UTC
Created attachment 72727 [details]
yast logs
Comment 2 Thomas Fehr 2006-03-14 19:07:32 UTC
Problem is caused by the dash in "sl10.1-root"

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