Ask Your Question
0

Fedora 28 Anaconda install Hardware Raid Mirror

asked 2018-05-27 15:26:18 -0600

enetarch gravatar image

This system previous ran Fedora 15 with mirrored drives.

When loading Fedora 28 onto SuperMicro H8SGL, with 2 1T sata drives mirrored via hardware - Adaptec, Anaconda doesn't see the mirrored drive. parted -l can list them. dmraid -l can list them.

I can install Fedora 28 when the mirror is broken, and drives are used as individual drives.

I would prefer hardware mirroring as it requires less CPU resources.

edit retag flag offensive close merge delete

Comments

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.

enetarch gravatar imageenetarch ( 2018-05-27 21:33:30 -0600 )edit

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.

enetarch gravatar imageenetarch ( 2018-05-28 02:51:31 -0600 )edit

opened a bugzilla report with Fedora .. https://bugzilla.redhat.com/show_bug....

enetarch gravatar imageenetarch ( 2018-05-29 13:30:31 -0600 )edit

opened a bugzilla report with Fedora, concerning upgrade bath below .. https://bugzilla.redhat.com/show_bug....

enetarch gravatar imageenetarch ( 2018-05-29 13:55:42 -0600 )edit

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.

enetarch gravatar imageenetarch ( 2018-06-04 09:30:56 -0600 )edit

3 Answers

Sort by ยป oldest newest most voted
0

answered 2018-06-06 12:43:07 -0600

enetarch gravatar image

An idea I hadn't considered while running into this problem was loading the OS on one of the drives, creating a mirrored raid set on a single drive, then copying the OS to the mirrored raid set, and then adding the drive into the mirrored raid set.

It's not a time optimal solution, but could probably be done.

The following URLS provide details on how to do this:

Setting Up RAID using mdadm on Existing Drive https://www.guyrutenberg.com/2013/12/...

5.9.9.2. Rebuilding a RAID array https://access.redhat.com/documentati...HatEnterpriseLinux/4/html/IntroductionToSystemAdministration/s3-storage-raid-day2day-add.html

Mdadm Cheat Sheet http://www.ducea.com/2009/03/08/mdadm...

Mdadm Cheat Sheet https://gist.github.com/plepe/52ecc9f...

edit flag offensive delete link more
0

answered 2018-06-04 10:02:18 -0600

enetarch gravatar image

What I found while loading Fedora 28 onto a single drive and then creating the mirrored partitions, was that Linux ignored the hardware raid capabilities of the SuperMicro H8SGL and the StarTek RAID controllers. Instead, it continued to treat the drives as individual drives, till mdadm was configured. While the hardware reports that the RAIDS are optimal, I'm no longer sure which is performing the work .. Linux or the Controller. Or if both are doing the work.

If there is a solution to upgrading to Fedora 28 onto mirrored hard drives, it probably lies in manually setting up the mirrors via mdadm, and running parted mklabel msdos, before attempting to run the install process.

Below is the process I used to setup the mirrors after installing the OS on a single drive, and then mirror 2 data drives.

> lsblk -f
> mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sda /dev/sdb 
> cat /proc/mdstat
> mdadm --detail --scan | tee -a /etc/mdadm/mdadm.conf
> parted /mnt/md0 mklabel msdos ext4 0% 100%
> parted /mnt/md0 mkpart primary 
> mkfs.ext4 -l [volume name] /dev/md0
> mkdir -p /mnt/md0
> mount /dev/md0 /mnt/md0
> update-initramfs -u
> vi /etc/fstab
...
UUID=[/dev/md0 UUID] /mnt/md0 ext4 default 0 2

=====

How To Partition and Format Storage Devices in Linux https://www.digitalocean.com/communit...

ow to Mount and Unmount Filesystem / Partition in Linux (Mount/Umount Command Examples) https://www.thegeekstuff.com/2013/01/...

Hardware vs. Software RAID in the Real World https://backdrift.org/hardware-vs-sof...

How To Create RAID Arrays with mdadm on Ubuntu 16.04 https://www.digitalocean.com/communit...

edit flag offensive delete link more
0

answered 2018-05-28 07:12:51 -0600

enetarch gravatar image

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)

edit flag offensive delete link more

Comments

found that the drive / partition UUIDs are appearing as garbage in Fedora 28, but not 27. Thus fc28 cannot mount the drive, because it can't find it. Nor can I manually mount it. Opened a bugzilla report with Fedora about this .. https://bugzilla.redhat.com/show_bug....

enetarch gravatar imageenetarch ( 2018-05-29 13:58:18 -0600 )edit

While I was successful at getting to Fedora 27, I was never able to get to Fedora 28. The UUID's to the mirrored drives always became formatting strings, or looked like garbage. If there is a solution to loading Fedora 28 onto mirrored hard drives, it probably lies in manually setting up the mirrors via mdadm, and running parted mklabel msdos, before attempting to run the install process.

enetarch gravatar imageenetarch ( 2018-06-04 09:32:56 -0600 )edit

Question Tools

Stats

Asked: 2018-05-27 15:26:18 -0600

Seen: 860 times

Last updated: Jun 06 '18