Description of problem: Rebuild does not continue after reboot. After reboot RAID volume is in normal state, but rebuild did not finished and data is inconsistent (out-of-sync). Version-Release number of selected component (if applicable): mdadm 3.2.3-6.el6 and 3.2.3-7.el6 How reproducible: Always Steps to Reproduce: 1. Create IMSM container: # mdadm -C /dev/md/imsm -amd -e imsm -n 2 /dev/sdb /dev/sdc -R 2. Create RAID1 (of size at least 20G): # mdadm -C /dev/md/raid -amd -l1 -n 2 /dev/sdb /dev/sdc -R -f # mdadm --wait /dev/md/raid 3. Add spare disk to the container: # mdadm --add /dev/md127 /dev/sdd 4. Turn off HDD /dev/sdb 5. Wait for start of rebuild 6. Save config file: # mdadm -Ebs > /etc/mdadm.conf 7. Reboot system 8. Enter OROM and check whether the volume "raid" is in Rebuild state OR 9. Boot system and check whether rebuild process is going on. Actual results: In OROM the volume is in Normal state and rebuild seems to be finished. After system's start-up RAID volume is in auto-read-only state and metadata is in Dirty state. Rebuild seems to be finished but it is not. Data is inconsistent (out-of-sync). Expected results: Rebuild continues and correctly finishes. Additional info: The bug occured after applying the patch "mdadm-2.5.2-static.patch" from mdadm-3.2.3-6.el6.x86_64.rpm, which changes the path of mdmon's pid file (MDMON_DIR) in Makefile. The patch has been accepted by Neil and is upstream now: http://neil.brown.name/git?p=mdadm;a=commitdiff;h=7ce05701813496571e1f7f79c726aa6e4868bd5f
mdadm-3.2.3-9.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.3-9.fc17
mdadm-3.2.3-9.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.3-9.fc16
mdadm-3.2.3-9.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mdadm-3.2.3-9.fc15
Package mdadm-3.2.3-9.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.3-9.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7105/mdadm-3.2.3-9.fc17 then log in and leave karma (feedback).
mdadm-3.2.4-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.4-2.fc17
mdadm-3.2.4-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.4-2.fc16
mdadm-3.2.4-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mdadm-3.2.4-2.fc15
mdadm-3.2.4-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.4-3.fc17
mdadm-3.2.4-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.4-3.fc16
mdadm-3.2.4-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mdadm-3.2.4-3.fc15
mdadm-3.2.5-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.5-1.fc17
mdadm-3.2.5-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.5-1.fc16
mdadm-3.2.5-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mdadm-3.2.5-1.fc15
mdadm-3.2.5-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
mdadm-3.2.5-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
mdadm-3.2.5-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mdadm-3.2.5-3.fc17
mdadm-3.2.5-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.