Software RAID 1 and mdadm



During boot up, I get the following messages:

mdadm: only specify super-minor once, super-minor=4 ignored.
mdadm: only specify super-minor once, super-minor=1 ignored.
mdadm: only specify super-minor once, super-minor=6 ignored.
mdadm: only specify super-minor once, super-minor=0 ignored.
mdadm: only specify super-minor once, super-minor=3 ignored.
mdadm: only specify super-minor once, super-minor=5 ignored.
mdadm: only specify super-minor once, super-minor=2 ignored.


I figured out that these messages are also generated by:

mdadm --examine --scan


This is what I have in mdadm.conf, which was created
during installation of fedora core 3:

# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md4 super-minor=4
ARRAY /dev/md1 super-minor=1
ARRAY /dev/md6 super-minor=6
ARRAY /dev/md0 super-minor=0
ARRAY /dev/md3 super-minor=3
ARRAY /dev/md5 super-minor=5
ARRAY /dev/md2 super-minor=2



Is it right that the warning messages above were a result
of specify the "super-minor" parameter in mdadm.conf file ...
given that the minor number could be determined from /dev/mdX,
where X is the minor number according to mdadm.conf:

super-minor=
The value is an integer which indicates the minor number
that was stored in the superblock when the array was cre-
ated. When an array is created as /dev/mdX, then the minor
number X is stored.


Also, can the output of 'mdmad --detail --scan' replace
the contents in mdadm.conf ? Here's what I get with 'mdadm --detail --scan':


ARRAY /dev/md4 level=raid1 num-devices=2
UUID=66fc43a3:005cef14:5d5a4e61:f27de595
devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=56faff4d:d6cc8d07:009e9fb8:2032271e
devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md5 level=raid1 num-devices=2
UUID=136c2810:f5586756:405b432e:f13c2d73
devices=/dev/sda3,/dev/sdb3
ARRAY /dev/md6 level=raid1 num-devices=2
UUID=ced64724:00a0a246:4d5d5da8:8fc7ee1f
devices=/dev/sda5,/dev/sdb5
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=4da9cfbc:544d48a5:11a4edbd:85c644f5
devices=/dev/sda7,/dev/sdb7
ARRAY /dev/md3 level=raid1 num-devices=2
UUID=d4daf629:6805ac25:0c5e5630:af8e2e4d
devices=/dev/sda8,/dev/sdb8
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=5ea2f756:59e64953:eb889eb4:cc050a15
devices=/dev/sda6,/dev/sdb6


I like the output better above, since it exactly says
which partitions are part of the raid 1 array.


.



Relevant Pages

  • Software RAID 1 and mdadm
    ... During boot up, ... DEVICE partitions ... of specify the "super-minor" parameter in mdadm.conf file ... ... When an array is created as /dev/mdX, ...
    (comp.os.linux.setup)
  • Re: Problems with software RAID on SATA
    ... Connected to this are two 320GB drives ... >>which I want to turn into a RAID1 array. ... >>I'm almost certain it's a problem with initting the RAID arrays at boot. ...
    (Debian-User)
  • FreeBSD 4.8, ASR2120, SMP, degraded RAID1/mirror => storage failure
    ... upon a RAID array degradation event (a disk is ... The same happens upon boot with a rebuilding/degraded array ... Attached is a tarball with debugging logs. ...
    (freebsd-questions)
  • Problems with mounting RAID5 array at boot
    ... mount a RAID5 array on four drives with some existing data. ... The superblock could not be read or does not describe a correct ext2 ... filesystem, ... Now here I can type control-D to boot up normally or enter the root ...
    (Debian-User)
  • Re: [opensuse] Raid 5 installation
    ... create the software array but I am warned that it will NOT be bootable ... I think the main limitation is GRUB, as it needs to be able to access ... It is simple with boot on your IDE drive. ... GRUB sees the individual drives when looking for boot, ...
    (SuSE)