Description of problem: I have two RAID partitions which mdadm is supposed to initialize early on in rc.sysinit. This does not succeed and therefore later the fsck calls fail and throw me in the panic shell. Booting with enforcing=0 makes things work. Version-Release number of selected component (if applicable): initscripts-8.53-1.x86_64 selinux-policy-2.6.1-1.fc7.noarch mdadm-2.6.1-4.fc7.x86_64 How reproducible: always Steps to Reproduce: 1.boot system with RAID partitions 2. 3. Actual results: RAID not initialized Expected results: RAID initialized, partitions can be mounted Additional info: I don't have the audit message since it's not printed on the console.
Can you replace the call to mdadm in /etc/rc.sysinit with: strace /sbin/mdadm ... bash just to get an idea of where it fails?
There was a bug where mdadm was not allowed to create devices in /dev and then use them. This should be fixed in the updated selinux policies so I think this is fixed.
Should be fixed in the current release