http://bugzilla.opensuse.org/show_bug.cgi?id=1156086 Bug ID: 1156086 Summary: Combination of RAID5 with (encrypted) logical volumes blows up system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: oen999@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: After creating a RAID5 array and using it (entirely) for LVM, the creation of multiple (encrypted) LVs leads to insurmountable problems. The RAID5 (although not specifically named) is seen as 'dirty'. During re-install, the RAID5 is visible but the volume group and LVs seem to have disappeared. After re-install the RAID5 is visible in Yast2, but again without VG and LVs; moreover, the RAID5 can not be removed and submitting a bug report is requested. I've been away from the Linux world for 10 years and only recently returned, but I'm not exactly a 'beginner' in computer land. This problem (which was very hard to pinpoint) has come up several times, and also occurs in Tumbleweed. In fact, if the phantom RAID5 array is present the installation of Tumbleweed won't get past the selection of the desktop. Reproducible: Always Steps to Reproduce: 1. Build a RAID5 array (I used 3 8TB hard drives, giving 14.55 TB net) 2. Build a volume group, consisting of the complete RAID5 array. 3. Build encrypted logical volumes; I think the first LV won't cause problems, and maybe the 2nd is OK too, but with 3 LVs the system goes bonkers. Actual Results: Booting the system usually, but not always, fails. After booting, Yast2 lists the RAID5 array but without volume group and without any logical volumes. Even so, the RAID5 can not be removed. It is possible to remove the RAID5 using mdadm, but it's not very useful as the problem will re-occur next time RAID5 and LVM are set up. The Yast2 logs will be added to this bug report. -- You are receiving this mail because: You are on the CC list for the bug.