mdadm on omv 4.1.27-1

    • OMV 4.x
    • Resolved
    • Source Code

      1. # mdadm --details --scan
      2. mdadm: unrecognized option '--details'
      3. Usage: mdadm --help
      4. for help
      do nothing..
      do you mean

      Source Code

      1. # mdadm --detail --scan
      2. ARRAY /dev/md/raid metadata=1.2 name=nas:raid UUID=264e1924:4cba2353:1a44a0f8:6fd1dda6
      or

      Source Code

      1. # mdadm --examine --scan
      2. ARRAY /dev/md/raid metadata=1.2 UUID=264e1924:4cba2353:1a44a0f8:6fd1dda6 name=nas:raid
      or

      Source Code

      1. # mdadm --detail /dev/md/raid
      2. /dev/md/raid:
      3. Version : 1.2
      4. Creation Time : Thu Sep 12 20:34:42 2019
      5. Raid Level : raid5
      6. Array Size : 5860150272 (5588.67 GiB 6000.79 GB)
      7. Used Dev Size : 1953383424 (1862.89 GiB 2000.26 GB)
      8. Raid Devices : 4
      9. Total Devices : 4
      10. Persistence : Superblock is persistent
      11. Intent Bitmap : Internal
      12. Update Time : Sun Nov 10 06:00:55 2019
      13. State : clean
      14. Active Devices : 4
      15. Working Devices : 4
      16. Failed Devices : 0
      17. Spare Devices : 0
      18. Layout : left-symmetric
      19. Chunk Size : 512K
      20. Name : nas:raid (local to host nas)
      21. UUID : 264e1924:4cba2353:1a44a0f8:6fd1dda6
      22. Events : 3765
      23. Number Major Minor RaidDevice State
      24. 0 8 48 0 active sync /dev/sdd
      25. 1 8 64 1 active sync /dev/sde
      26. 2 8 80 2 active sync /dev/sdf
      27. 3 8 96 3 active sync /dev/sdg
      Display All
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • Rd65 wrote:

      do you mean
      I was able to type the right command the other few times but added an 's' that time. The first output is what I wanted. After trying on one of my systems, I get the same error but it doesn't cause a problem since the line only adds a "ARRAY <ignore> devices=*" line to mdadm.conf on devices that have NO arrays. On devices with no arrays, the command works since there is no output with spaces from mdadm --detail --scan. So, you can safely ignore this error since it is harmless (people never see it from the web interface). I don't know if Volker with worry about fixing it since the code is not in OMV 5.x.
      omv 5.2.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.2
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!