root[~]# mdadm -Es
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3122811b:6c853b3a:b02c8dab:77ca0c55
root[~]# mdadm -As --config=partitions
[b]mdadm: No arrays found in config file[/b]
root[~]# mdadm -C /dev/md0 --assume-clean --level=1 --raid-devices=2 /dev/sdb /dev/sdc --homehost=archiv
mdadm: /dev/sdb appears to be part of a raid array:
level=raid1 devices=2 ctime=Thu Dec 31 19:37:11 2009
mdadm: /dev/sdc appears to be part of a raid array:
level=raid1 devices=2 ctime=Thu Dec 31 19:37:11 2009
Continue creating array? yes
mdadm: array /dev/md0 started.
root[~]# mdadm -As --homehost=archiv
mdadm: /dev/md/0 has been started with 2 drives.
I would like that mdadm finds the devices itself and assembles it by itself according to same homehost or uuid in each md superblock.
Last edited by damNageHack on 8. Jan 2010, 21:51, edited 1 time in total.
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
The point is that I have to provide the --homehost parameter for Assemble mode explicitly. But when I use the Examine mode, mdadm can find it by itself. Strange and confusing behaviour, isn't it?
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
JRD wrote:It's not that I don't want to help...I just don't have the skills, sorry.
My (and others ?) thoughts exactly!
No problem. Then I will try to get help from the mdadm developers, reasons why they did it this way (manpage says something, but not clear to me)
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
