mdadm: only give one device per ARRAY line: /dev/md0 and metadata-1.2

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • mdadm: only give one device per ARRAY line: /dev/md0 and metadata-1.2

      I recently added a drive to my RAID 5 array in OMV to go from 4 drives to 5. The drives are 3TB each so the new capacity is roughly 12TB. The process went smoothly and everything seems to check out; however, I began getting a mail notification each day that has these two lines in the body of the email.


      /etc/cron.daily/openmediavault-mdadm:
      mdadm: only give one device per ARRAY line: /dev/md0 and metadata-1.2


      I went to the chron entry and ran the same command manually and get the same output as line two above. All my searching seems to point to my mdadm.conf file, but I can't figure out what the issue is. Here is my mdadm.conf file

      Shell-Script: mdadm.conf

      1. # mdadm.conf
      2. #
      3. # Please refer to mdadm.conf(5) for information about this file.
      4. #
      5. # by default, scan all partitions (/proc/partitions) for MD superblocks.
      6. # alternatively, specify devices to scan, using wildcards if desired.
      7. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      8. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      9. # used if no RAID devices are configured.
      10. DEVICE partitions
      11. # auto-create devices with Debian standard permissions
      12. CREATE owner=root group=disk mode=0660 auto=yes
      13. # automatically tag new arrays as belonging to the local system
      14. HOMEHOST <system>
      15. # definitions of existing MD arrays
      16. ARRAY /dev/md0 metadata-1.2 name=omv:primary UUID=6001aebd:0b9b04ab:b6821595:72f5f027
      17. # instruct the monitoring daemon where to send mail alerts
      18. MAILADDR <my email address here>
      19. MAILFROM root
      Display All
      I am not an expert, but everything I can find seems to say this is correct. The output of the command "mdadm --detail /dev/md0" shows

      Source Code

      1. root@omv:~# mdadm --detail /dev/md0
      2. mdadm: only give one device per ARRAY line: /dev/md0 and metadata-1.2
      3. /dev/md0:
      4. Version : 1.2
      5. Creation Time : Mon Jan 1 00:40:30 2018
      6. Raid Level : raid5
      7. Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
      8. Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB)
      9. Raid Devices : 5
      10. Total Devices : 5
      11. Persistence : Superblock is persistent
      12. Intent Bitmap : Internal
      13. Update Time : Thu Jan 3 10:45:28 2019
      14. State : clean
      15. Active Devices : 5
      16. Working Devices : 5
      17. Failed Devices : 0
      18. Spare Devices : 0
      19. Layout : left-symmetric
      20. Chunk Size : 512K
      21. Name : omv:primary (local to host omv)
      22. UUID : 6001aebd:0b9b04ab:b6821595:72f5f027
      23. Events : 47740
      24. Number Major Minor RaidDevice State
      25. 0 8 48 0 active sync /dev/sdd
      26. 1 8 16 1 active sync /dev/sdb
      27. 2 8 0 2 active sync /dev/sda
      28. 3 8 32 3 active sync /dev/sdc
      29. 4 8 64 4 active sync /dev/sde
      Display All
      Any ideas about what is causing this error to show up? Again, the array seems to be working fine, but it does hold the family jewels (so to speak) so I am loathe to leave it as-is. Any help or insight is much appreciated. BTW; I upgraded to the latest OMV (4.1.x Arrakis) to see if that would clear it... nope.

      Thanks