Is there a reason why after a software raid install (from kickstart) that md1 is always unclean. md0 seems fine.
boot screen says md1 is dirty and cat /proc/mdstat show md1 as being rebuilt.
Any ideas?
Jerry
--------------- my kickstart -------------- echo "bootloader --location=mbr --driveorder=$HD1SHORT --append="rhgb quiet" " > /tmp/partition-information echo "clearpart --all --initlabel " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=20000 " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT swap --asprimary --bytes-per-inode=4096 --fstype="swap" --size=4000 " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT raid.02 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=1 --grow " >> /tmp/partition-information echo "part --ondisk=$HD2SHORT raid.03 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=20000 " >> /tmp/partition-information echo "part --ondisk=$HD2SHORT swap --asprimary --bytes-per-inode=4096 --fstype="swap" --size=4000 " >> /tmp/partition-information echo "part --ondisk=$HD2SHORT raid.04 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=1 --grow " >> /tmp/partition-information echo "raid / --bytes-per-inode=4096 --device=md0 --fstype="ext3" --level=1 raid.01 raid.03 " >> /tmp/partition-information echo "raid /home --bytes-per-inode=4096 --device=md1 --fstype="ext3" --level=1 raid.02 raid.04 " >> /tmp/partition-information
Jerry Geis wrote:
Is there a reason why after a software raid install (from kickstart) that md1 is always unclean. md0 seems fine.
boot screen says md1 is dirty and cat /proc/mdstat show md1 as being rebuilt.
Immediately after they're constructed, all RAID arrays are dirty and need to be rebuilt. Most likely, md0 completes its rebuild during your installation, but md1 does not. After reboot, md1's rebuild needs to complete.
What you're seeing sounds perfectly normal.