I'm looking for a document that describes how to perform a fresh CentOS 7.3 installation on a physical machine that includes multiple hard drives (formatted and configured with CentOS 6.9) utilizing software RAID-1; five physical NICs.

The creation of this environment is to me a simple act using CentOS 6. What should I be concerned about using the CentOS 7.3 install?

I've created a KVM environment to do some testing.

Is help available?

Gene

OK, I did install CentOS 7.3 x86_64 into a KVM environment on a system running CentOS 6.9 x86_64. Here's what I found:

The base virtual environment is 2 vCPU; 4GB RAM, 2 - 256GB qcow2 disks, 2 - 1GB virtual NICs

I had to cancel and start the install over 3 times because I was unaware of how to create the required PVS, VGS, and LVM along with the required RAID-1. WHY is it totally different from RHEL4, RHEL5, RHEL6, CentOS4, CentOS5, CentOS6??? Since I'm doing this at home and only have 8 machines, this will be impossible in a arena with 200 - 300 servers.
How do you make a custom ISO where all you have to do is give the server name and IP address???

Thank goodness CentOS 6 EOL is 2020. I think in the end this is going to be worse than Windows XP unless everyone starts migrating now.

Next step is to make the mods required so that if sda goes bad it will boot from sdb. and do we really need a GUI?

Gene

OK, here's the command used to create the mentioned virtual machine:

virt-install --connect qemu:///system -n jpd3vm06 -r 4096 --vcpus=4 -f /jpdvmnfs/jpd3vm06a.qcow2 -s 256 -f /jpdvmnfs/jpd3vm06b.qcow2 -s 256 \
-c /jpd3storage/jpdesigns/isoimages/centos/CentOS-7-x86_64-DVD-1708.iso --vnc --os-type linux --os-variant generic26 \
--accelerate --network=bridge=br0 --network=bridge=br1 --hvm


I'm really concerned about the changes made to the grub configuration file.
CentOS 6.9 grub.conf example:
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_jpd3opsys-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/md0 <<<------ Manually altered to boot from the /boot RAID-1 device
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz <<<<------ This points to /dev/sda1
# splashimage=(hd1,0)/grub/splash.xpm.gz <<<<------ This points to /dev/sdb1 Use this entry if /dev/sda fails
hiddenmenu
title JPDSYS3c (2.6.32-696.16.1.el6.x86_64)
kernel /vmlinuz-2.6.32-696.16.1.el6.x86_64 ro root=/dev/mapper/vg_jpd3opsys-lv_root rd_NO_LUKS rd_LVM_LV=vg_jpd3opsys/lv_root LANG=en_US.UTF-8 rd_MD_UUID=3f2254fc:db7980cb:046e8474:c671b305 rd_LVM_LV=vg_jpd3swap/lv_jpd3swap SYSFONT=latarcyrheb-sun16 rd_MD_UUID=84710083:3596fe2d:db1dffed:0944cd1d KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet vga=31B crashkernel=auto amd_iommu=on
initrd /initramfs-2.6.32-696.16.1.el6.x86_64.img


How do I modify grub2 to solve the multi-disk boot issue?