On 07/05/2023 02:29, Alex Elder wrote:
On 5/6/23 6:28 PM, Wol wrote:
On 06/05/2023 23:29, Hannes Reinecke wrote:
Device Role : Active device 2
Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)
root@meat:/#
mdadm manage /dev/md127 --add /dev/sdd ?
OMG NO!
That really will trash your array ...
Cheers,
Wol
This is why I sent the original message; I really
want to avoid losing my data because of a dumb
misunderstanding. I did look at the Linux_Raid
page on raid.wiki.kernel.org but was not confident
I knew the right thing to do. I'm very familiar
(as a developer) with storage software, just not
MD and the tools to manage its volumes.
I suspect that putting a proper MD superblock on the
middle partition (sdc1, out of sd{b,c,d}1) might be
enough to get it to assemble again. After that I
think I'll be able to rebuild the newly replaced
drive and also rename it to /dev/md/z.
Is it an easy command? Is any more information required?
mdadm array --add /dev/sdc1
The reason I reacted with horror at the previous message is that
/dev/sdd1 is already part of the array. Adding /dev/sdd (which is quite
possible) would destroy /dev/sdd1 and you'd be left with only one
working partition out of three - that's the array gone ...
Read the wiki on how to add a drive. I suspect that's where you went
wrong in the first place. Make sure you've got the right drive to add -
it said you had sdb1 and sdd1, so sdc1 is missing and that's the one you
want to add (CHECK BEFORE YOU ADD). The kernel can move things around so
make sure between booting and adding that nothing "weird" has happened.
Then you should be good to go. Just CHECK. And DOUBLE CHECK.
Cheers,
Wol
