yours,
mdadm -Es
ARRAY /dev/md/5 metadata=1.1 UUID=aa...aa name=urras.penguinpee.nl:5
ARRAY /dev/md/1 metadata=1.1 UUID=bb..bb name=urras.penguinpee.nl:1 spares=1
ARRAY /dev/md/54 metadata=1.2 UUID=cc..cc name=urras.penguinpee.nl:54
cat /etc/mdadm.conf
ARRAY /dev/md/5 metadata=1.1 name=urras.penguinpee.nl:5 UUID=aa...aa
ARRAY /dev/md/54 metadata=1.2 name=urras.penguinpee.nl:54 UUID=cc..cc
ARRAY /dev/md/1 metadata=1.1 spares=1 name=urras.penguinpee.nl:1 UUID=bb..bb
mine,
mdadm -Es
ARRAY /dev/md/0 metadata=1.2 UUID=ee..ee name=svr041:0
ARRAY /dev/md/1 metadata=1.2 UUID=ff..ff name=svr041:1
ARRAY /dev/md/2 metadata=1.2 UUID=dd..dd name=svr041:2
cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid10 num-devices=4 metadata=1.2 UUID=ee..ee name=svr041:0
ARRAY /dev/md1 level=raid10 num-devices=4 metadata=1.2 UUID=ff..ff name=svr041:1
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=1.2 UUID=dd..dd name=svr041:2
i explicitly add the
level=
num-devices
i've had issues long ago with mis-assembly that that cured.
whether it's STILL a problem, i don't know; all my array spec contain contain
these, and don't cause harm. it's now SOP here.
i'd at least consider checking ...