What is going on with this Raid 1 configuration?

    • OMV 3.x

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

    • What is going on with this Raid 1 configuration?


      I'm a new user and I need some help interpreting what's going on.

      I set up my two hard drives as a RAID 1 configuration. They got split up into drives
      • /dev/md0 (2.73TB)
      • /dev/md0p1 (1.90TB)
      • /dev/md0p3 (1.39TB)
      The last two are still in state "false". The capacities don't add up (the hard drives are 2.73TB each).

      Is this ok?
      What is happening here?
      • openmediavault control panel.png

        23.51 kB, 936×436, viewed 204 times

      The post was edited 1 time, last by nasusr77 ().

    • The only thing that I can think of, that might be related:

      Was one or more of these drives ever used in RAID1 before?

      When mdadm RAID is set up, much like LVM and GPT partitioned drives, "stuff" (like the super block) is written as partition data. In some cases, a quick wipe doesn't always overwrite this data. This comes to mind because some partition types, flags, etc., can be damx persistent, requiring something like Darik's Boot and Nuke (DBAN) to clear it out.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk