On 10/19/19 6:54 PM, Reindl Harald wrote:
Am 20.10.19 um 02:06 schrieb Curtis Vaughan:
After updates I decided to reboot, but it would never reboot until I
removed the new drive. I'm wondering if it has something to do with
needing to installl grub on the new drive?
surely, a workaround would have been switch the cables so that the first
disk is the one which still has grub
grub is at the begin of the drive outisde the array itself and so for
real working redundacy and i posted you days ago my script for drive
replacemnets which clearly installs grub on the new one
[root@srv-rhsoft:~]$ cat /scripts/raid-recovery.sh
#!/usr/bin/bash
GOOD_DISK="/dev/sda"
BAD_DISK="/dev/sdd"
# --------------------------------------------------------------------------
echo "NOT NOW"
exit
# --------------------------------------------------------------------------
# clone MBR
dd if=$GOOD_DISK of=$BAD_DISK bs=512 count=1
# force OS to read partition tables
partprobe $BAD_DISK
# start RAID recovery
mdadm /dev/md0 --add ${BAD_DISK}1
mdadm /dev/md1 --add ${BAD_DISK}2
mdadm /dev/md2 --add ${BAD_DISK}3
# print RAID status on screen
sleep 5
cat /proc/mdstat
# install bootloader on replacement disk
grub2-install "$BAD_DISK"
OMG. The funny thing is that I was looking for this information, but I
was sure it was on a website and never searched my emails....
Thanks for reminding me!
