Description of problem: My workstation has 3 disc setup: /dev/md0 /dev/sd{a,b,c}1 RAID 1 -> ext3 (/boot) /dev/md1 /dev/sd{a,b,c}2 RAID 5 -> PV -> VG -> LV ext3 ubuntu (/) -> LV ext3 fedora (/) -> LV LUKS data I attempted to install F9 Beta onto the LV "fedora". Anaconda would not allow this. I then attempted to create a new LV in the VG (the VG has ~ 50 G unallocated). Annaconda would not allow this either. Version-Release number of selected component (if applicable): 9 Beta x86-64 How reproducible: 100% Steps to Reproduce: 1. Produce disc setup above 2. Boot F9 beta install media 3. Try to either view/edit existing LV or create a new LV Actual results: Error dialog of: "Not enough physical volumes At least one unused physical volume partition is needed to create an LVM volume group" Expected results: For it to work. Additional info: Whilst Anaconda was able to display the volume group and logical volumes, the physical volume /dev/md1 was marked with a type of "foreign". Clicking delete on /dev/md1 gives an error of: "Unable to delete This partition is part of the LVM volume group 'NAME_OF_MY_VOLUME_GROUP' Anaconda did let me delete the LV "fedora", but I was unable to edit/create LVs otherwise.
Can you grab the /tmp/anaconda.log and /tmp/lvmout from this attempt?
Created attachment 299717 [details] anaconda.log
Created attachment 299718 [details] lvmout File gets zeroed out on custom partitioning screen. Output here after clicking back to choose partition layout.
Created attachment 299719 [details] /tmp/syslog
Created attachment 299721 [details] vg metadata Produced by vgcfgbackup
Information attached
I think that this should be fixed in the preview release which should be out in the next day or so. Can you try again with it?
Confirmed that bug is fixed with preview release. Thanks!