Red Hat Bugzilla – Bug 597423
Installer leaves Intel BIOS Raid 1 in unsynchronized state
Last modified: 2010-05-31 16:06:54 EDT
Description of problem:
After installing a F13/WinXP dual boot system on Intel ICH8R BIOS RAID 1 and rebooting to WinXP, the Intel Matrix RAID manager reports that the RAID array is unsynchronized and starts a multi-hour rebuilding process.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install to RAID 1
RAID requires rebuilding
RAID array is clean and ready to use
Intel DG965WH motherboard, 2x WD 1TB drive in RAID 1.
The installed F13 system can be booted exactly once, reboot fails and the system needs reinstallation.
Thanks for the report. I've spend some time today analyzing it, and here is what
is going on:
When moving to stage2 we rename the initrd /lib to /lib_old and add
a symlink from /lib to /mnt/runtime/lib. When shutting down we unmount
filesystems and then after unmount try to run mdadm to wait for
any Intel BIOS RAID arrays to have their metadata updated that they
were cleanly shutdown to avoid a resync of the entire array on the next boot.
But at this point /lib is a dangling symlink, so no elf interpreter gets
found (nor libc) and the mdadm call we do fails, leaving the array unclean.
I've written a patch restoring the old /lib after unmount, and posted it to the list for review:
Once reviewed I'll commit this, so that this will be fixed for F-14. I'm afraid there is nothing we can do for F-13 to retroactively fix this.
(In reply to comment #1)
> The installed F13 system can be booted exactly once, reboot fails and the
> system needs reinstallation.
If you can reproduce this consistently please file a new bug report for this, although it might be good to first wait and see what comes out of the rescue mode bug you filed, the 2 are likely related.