On Sun, Jan 26, 2020 at 3:11 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
Now I will try to actually fail the now shuffled around old sdb smaller physical disk, or maybe the other small sdc physical disk and then add the second larger physical disk. I will then need to clone the GPT and partition table information stuff from the first larger physical disk I guess to make them actually kind of identical in partition layout.
Progressing here now: As my smaller sata drives had previously been inside a sata enclosure, I wanted to move the newer larger drives as quickly as possible into that sata enclosure. So thats why as well shuffled around the first old smaller drive, thus bringing it to the outside. The first new larger sata drive is now inside the sata enclosure, together with the second older smaller sata drive. So now it was time to fail that second smaller still enclosure encased sata drive, first identifying it by its real serial number, or better say looking up the serial number of the still hidden second smaller sata drive inside the sata enclosure via:
smartctl --all /dev/sdb1 | more
then making sure that serial number displayed there was not the serial number of the now-outside smaller sata first drive. then failing and remove and then physically disconnecting it from inside the sata enclosure, turning off power of that sata enclosure slot and ejecting it.
mdadm --fail /dev/md127 /dev/sdb1 mdadm --remove /dev/md127 /dev/sdb1
Now attaching the new second larger sata disk physically into the freed sata enclosure slot. Giving me again a now newly populated physical sata device named sdb again. Now with the help of sgdisk tool, for gpt disk handling, backing up the gpt and partitioning table information from my first larger sata hdd disk added previousl, first saving table information into a file named "table"
sgdisk --backup=table /dev/sdc
Then writing this information from sdc to tne new larger physical disk now named sdb:
sgdisk --load-backup=table /dev/sdb
And finally randomizing this cloned information and its UUID stuff for real world use with sgdisk again:
-G, --randomize-guids Randomize the disk's GUID and all partitions' unique GUIDs (but not their partition type code GUIDs). This function may be used after cloning a disk in order to render all GUIDs once again unique.
sgdisk -G /dev/sdb
This giving it a proper near identical cloned sdb1 partition layout, cloned from sdc (sdc1). Then I turned off the bitmap again:
mdadm --grow /dev/md127 --bitmap=none
and adding the second large sata hdd, named sdb1 to the md127 raid1 device:
mdadm --add /dev/md127 /dev/sdb1
And then growing the outer md raid device to make use of all the three disks for its raid1:
mdadm --grow --raid-devices=3 /dev/md127
Now waiting for a proper sync/rebuild, showing via e.g.
mdadm -QDv /dev/md127 State : clean, degraded, recovering Rebuild Status : 19% complete ... 1 8 49 0 active sync /dev/sdd1 2 8 33 1 active sync /dev/sdc1 3 8 17 2 spare rebuilding /dev/sdb1
.... waiting for completion to then continue with removing the leftover first small hdd and be done with physical stuff, then still needing to regrow the md127 device to larger capacity of the newer larger hdd disks used for it, and later regrowing the filesystem as well to make use of the additonal space as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org