Created attachment 340183 [details] storage.log Description of problem: Existing system with RAID1 partitions show up under custom partitioning with 0 size. Trying to use format the md device as Physical Volume (Encrypted) and then making a VG causes LUKS device to show up with a size of -8.00 MB. Version-Release number of selected component (if applicable): 11.5.0.45 How reproducible: always Steps to Reproduce: 1. have existing RAID1 /dev/md0, /dev/md1, etc. made with two identical disks 2. boot anaconda and choose custom partitioning 3. look at RAID Devices in list 4. try to format one as Physical Volume (LVM) and check 'Encrypt' 5. click LVM to create a LVM Volume Group. Actual results: On my disk I have /dev/md0 through /dev/md12, and they all show up as Size (MB) 0. On step 5 above, I see "[x] luks-md1 -8.00 MB" in the LVM screen. Expected results: Show correct sizes of md devices. Allow formatting/installing to existing md devices. Additional info: Some of the other existing md devices have other existing LVM VGs with encryption which were not detected at all. F11 Beta did detect those and request the passphrases for them, but 11.5.0.45 no longer does this, probably due to this 0-size bug.
Created attachment 340184 [details] program.log
Created attachment 340185 [details] anaconda.log
Created attachment 340186 [details] udevadm info --exportdb
Created attachment 340187 [details] mdadm --examine /dev/sda2; mdadm --examine /dev/sdb2
Created attachment 340188 [details] output of /proc/mdstat
Please retest with anaconda-11.5.0.47-1 or later. Several fixes related directly to pre-existing md devices were first included in that version.
Verified fixed.