Description of problem: I set up RAID0 with 1 ssd disk and 2 normal disks and I tried it with 2 normal disks in RAID0. Then I run installation from F22 Live-Workstation RC2. Everything worked fine. But after reboot there is no bootable system. Even when I try UEFI entry Fedora it doesn't boot. From disk it doesn't boot to grub. When I look into anaconda's program.log there is output from new-kernel-pkgs which isn't there normally. Part of it: 3:45:42,105 INFO program: Running... new-kernel-pkg --mkinitrd --dracut --depmod --update 4.0.2-300.fc22.x86_64 13:46:03,104 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:2414: invalid line: ffffffffatch 13:46:03,104 INFO program: 13:46:03,104 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:4992: invalid line: ffffffff810firq 13:46:03,104 INFO program: 13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:5832: invalid line: ffffffff811m_stop 13:46:03,105 INFO program: 13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:5913: invalid line: ffffm_stop 13:46:03,105 INFO program: 13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:6702: invalid line: fffffffstroy_buf ... ... ... Version-Release number of selected component (if applicable): 4.0.2-300.fc22.x86_64 F22 RC2 Additional info: I propose this as blocker. It violates beta criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices."
Created attachment 1028115 [details] anaconda's program.log after the installation
This may be hardware-dependent. I just installed successfully on a four-disk RAID0 array provided by LSI hardware on a Dell PowerEdge T620. I installed on EFI. I experienced no errors like those Petr saw above and it booted just fine. I'm -1 to blocking on this.
Petr tested with 4.0.4-301 which has the fix from bug 1223332 on the same machine. He said that worked fine, so I'm going to mark this as a duplicate. *** This bug has been marked as a duplicate of bug 1223332 ***