Am 14.05.19 um 20:19 schrieb Eric Valette: > On 14/05/2019 20:13, Reindl Harald wrote: >> >> >> Am 14.05.19 um 17:48 schrieb Eric Valette: >>> I have a dedicated hardware nas that runs a self maintained debian 10. >>> >>> before the hardware disk problem (before/after) > >> how does that matter on any proper setup? >> *never* use /dev/xyz anywhere > > Fine. Does available online documentation makes it explicit? No .I > carefully read it before raid creation several years ago that /dev/sdX changes *randomly* depending on which drives are available and in which order they appear is common knowledge and exactly what you don't want in a setup which shouldn't care if a random drive is missing >> [root@srv-rhsoft:~]$ cat /etc/mdadm.conf >> MAILADDR root >> HOMEHOST localhost.localdomain >> AUTO +imsm +1.x -all >> >> ARRAY /dev/md0 level=raid1 num-devices=4 >> UUID=1d691642:baed26df:1d197496:4fb00ff8 >> ARRAY /dev/md1 level=raid10 num-devices=4 >> UUID=b7475879:c95d9a47:c5043c02:0c5ae720 >> ARRAY /dev/md2 level=raid10 num-devices=4 >> UUID=ea253255:cb915401:f32794ad:ce0fe396 > > So what? the question was how do I add array member using symbolic > names. Of course I can use /dev/by--xxx/ but when dumping I do not know > if it will be lost or net. the above *is not* about /dev/by... it's about the UUID of the 3 RAID devices itself > Thanks for non helping and only blaming. Glad others have helped instead bla, as you can see my mdadm.conf don't contain *any* devices it don't contain any scan stuff but the kernel line contains mentioning the 3 raid-arrays explicit rd.md.uuid=1d691642:baed26df:1d197496:4fb00ff8 rd.md.uuid=b7475879:c95d9a47:c5043c02:0c5ae720 rd.md.uuid=ea253255:cb915401:f32794ad:ce0fe396
