Note: I don't recommend this solution. There are a lot of problems that can / will appear along the way, and there is the possibility that the system will be unstable due to version conflicts.
The steps I followed.
1) Find the newest LiveCD recognize hardware mirroring. That happened to be Fedora 20.
Search Terms - Fedora Archives LiveCD Download
2) Find an upgrade path to the next release or highest release available. That happened to be Fedora 21.
> yum install fedora-upgrade
> fedora-upgrade
Search Terms - Fedora Upgrade Package Manager Wiki
At Fedora 21, Dracula (dracut) failed, claiming that the initramfs needed to be rebuilt. The recommended resolution was to run the Fedora 21 Live CD and run Dracula to fix the problem. (I'm purposely calling it Dracula, because I'm dyslexic, and more importantly it's a huge time suck! The system should just KNOW that it's a RAID set.)
a) open File Manager, and confirm the partitions were listed
Note: a standard user can't change anything on the Live CD or the RAID partitions. You will need to execute the following commands as root.
Note: LiveCD does allow you to open FTP connections and use other USB devices. Copy the configuration files and last two initramfs images off the boot drive for interested developers.
b) open a terminal session
> su
> cd /dev/mapper/ddf1_BOOT/boot
> mkdir backup
> cp initramfs-xx.xx.xx-fc20-x86_64.img backup
> cp initramfs-xx.xx.xx-fc21-x86_64.img backup
> mkinitrd -f -v /boot/initrd-$(uname -r).img $(uname -r)
Write down the name of the interramfs and initrd files on a piece of paper.
> reboot or shutdown -r now
At GRUB, press [e] to edit the current boot option, and edit initrd
initrd /boot/initrd-xx.xx.xx-fc21-x86_64.img ... or ...
initrd /boot/initramfs-xx.xx.xx-fc20-x86_64.img
While you're in GRUB, tell the kernal to be VERBOSE .. by removing the word quiet
One of these two images should load.
At this point in the Fedora Releases, they changed the boot method. The kernel is no longer responsible for finding and mounting storage devices, it's Dracula's job. Dracula does this by creating a ramdisk filled with commands and settings configured to your systems specifications. So, if you move a boot drive to a new motherboard, you will need to update this ramdisk image to allow it to boot there, via the procedure described above.
It is also Dracula's job to understand how your storage devices are configured and create this ramdisk .. initramfs or initrd. But for some strange reason, only the developers are aware of, it is not properly recognizing the RAID array the SuperMicro H8SGL motherboard uses. And, I tried all LiveCDs from 28 through 20, before one would recognize the RAID array properly.
3) Find the next upgrade path to the next highest release available. That happened to be Fedora 27. Fedora 28 required dnf-utilis, which would not load into Fedora 21. Though Fedora 27 ... (more)
I was able to install Fedora 20 and then upgrade to 21. However, I have to use initramfs from fc20, as fc21 does not contain something needed to properly recognize the raid array.
I was able to install Fedora 27 through dnf system-upgrade. This required 2 things to occur: 1) manually importing the repo key. 2) adjusting /etc/fstab to use the device path /dev/mapper/ddf1_BOOT .. instead of the UUID. if I'm successful at install Fedora 28, I will try to write a summary of the issues I faced and how I resolved them so that developers can issue bug reports and resolve issues.
opened a bugzilla report with Fedora .. https://bugzilla.redhat.com/show_bug....
opened a bugzilla report with Fedora, concerning upgrade bath below .. https://bugzilla.redhat.com/show_bug....
I have not found a solution to this problem at this time. What I decided to ultimately do, as I needed to get my server up and running, was to place the OS on a single drive, and place all the data on mirrored drives. In doing this, I found that mdadm was still needed to manage the mirrors.
If there is a solution to loading Fedora 28 onto mirrored hard drives, it probably lies in manually calling setting up the mirrors via mdadm, and running parted mklabel msdos, before attempting to run the install process.