Description of problem: I am using mdadm to assemble an Intel fake RAID on an ICH9-based motherboard and systemd does not properly assemble the container, resulting in the system dropping into a recovery console. Each time the Systemd package is updated, I need to change line 37 in the 'fedora-storage-init' unit to check for the mdadm map in the correct location like so: [ -r /proc/mdstat ] && [ -r /dev/.mdadm/map ] && /sbin/mdadm -IRs Apparently the map file location is in a different spot on Fedora. Version-Release number of selected component (if applicable): systemd-43-4mga2 How reproducible: Always. Steps to Reproduce: 1. Have Intel fake RAID configured. 2. Install mdadm and add /dev/md/XXXX entry to fstab. 3. Reboot.
CC: (none) => mageiaBlocks: (none) => 2120
Intel fake raid used be started by dmraid, but it's being converted to mdadm. You should be able to boot OK by passing "noiswmd" to the command line. Thomas is looking into this via 3972, so I'm tempted to say this is a dupe. *** This bug has been marked as a duplicate of bug 3972 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
Hmm, Sorry, it's not that bug... (I've been copying and pasting too much :() Thomas are you still tracking this? If so, which bug # is this really a dupe of?
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)Assignee: bugsquad => tmb
It's not a dupe. We have been installing mdadm map in /dev/.mdadm/map since mdv days, (fedora uses /dev/md/md-device-map) I've pushed a fix in initscripts-9.34-9.mga2 to match our current mdadm setup. Thanks for the report.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED