From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Description of problem:
The FC2 installer uses kernel 2.6.5-1.358 as its install kernel. In
addition to bug 109251 (raid5 parity resync skipped on anaconda
installs, which has affected every RH/FC installation I've seen), if
the installer creates a raid5 by hand or patched to actually do the
initialization, a bad raid5 array is *STILL* created because
2.6.5-1.358 has buggy raid5 resync code (it's fixed in 2.6.6-1.435.x).
The only way to work around this is to upgrade the kernel used for
installation. Once the raid5 is created bad, there's apparently no
way to easily correct the parity.
Note, the machine will install perfectly. Once a disk drops from the
RAID5 array, though, the filesystem on the array will most likely be
corrupt. The likelihood of this depends on whether or not fresh disks
are being used (don't use fresh install disks, use normal disks)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install raid5 array with FC2 installer
2. fail out drive
3. fsck filesystem on degraded array
Actual Results: Filesystem will be corrupt
Expected Results: Drive fails out normall and filesystem is not corrupt.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.