OMV 2.2.5 Mirror Raid lost after every reboot, no superblock

    • OMV 2.x
    • OMV 2.2.5 Mirror Raid lost after every reboot, no superblock

      I know there is an OMV 3.0 thread about this, if it's applicable please close this and I can post there even though it is OMV 2.0.

      I'm changing my raid setup from 3x 3TB in Raid5 to 2x 3TB in Raid1 + Rsnapshot to spare 3TB drive. After dismantling my Raid5 and wiping the discs I created a Raid1 mirror of the two 3TB drives. Reloaded my data, restarted and my Raid was gone. I'm gone ahead and re-creatred the Mirror Raid, rebooted, gone. I've tried to assemble the raid as many posts instructed but no luck. The mirror raid drives are sdb and sdc. I can't figure this one out, any help would be greatly appreciated!

      mdadm --assemble --force --verbose /dev/md0 /dev/sd[bc]

      Source Code

      1. mdadm: looking for devices for /dev/md0
      2. mdadm: Cannot assemble mbr metadata on /dev/sdb
      3. mdadm: /dev/sdb has no superblock - assembly aborted




      cat /proc/mdstat

      Source Code

      1. Personalities :
      2. unused devices: <none>
      blkid

      Source Code

      1. /dev/sdd1: UUID="275e2463-bb97-472c-a0e8-6962e0538355" TYPE="ext4" LABEL="OS"
      2. /dev/sdd5: UUID="e45fde5b-7be1-45cf-a124-02e16fda8d82" TYPE="swap"
      3. /dev/sde1: LABEL="DataB" UUID="7593ba61-3aca-4f16-b04a-0ed2ce37a51a" TYPE="ext4"
      4. /dev/sda1: LABEL="MediaA" UUID="4c940230-d646-4d63-93ae-c5b0a71bcc6e" TYPE="ext4"
      5. /dev/sdf1: LABEL="temp" UUID="5b2e9bfa-e671-4976-824c-68dbf0c0b86b" TYPE="ext4"


      fdisk -l

      Source Code

      1. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      2. Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
      3. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      4. Units = sectors of 1 * 512 = 512 bytes
      5. Sector size (logical/physical): 512 bytes / 4096 bytes
      6. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      7. Disk identifier: 0x00000000
      8. Device Boot Start End Blocks Id System
      9. /dev/sdb1 1 4294967295 2147483647+ ee GPT
      10. Partition 1 does not start on physical sector boundary.
      11. Disk /dev/sdd: 20.0 GB, 20014718976 bytes
      12. 255 heads, 63 sectors/track, 2433 cylinders, total 39091248 sectors
      13. Units = sectors of 1 * 512 = 512 bytes
      14. Sector size (logical/physical): 512 bytes / 512 bytes
      15. I/O size (minimum/optimal): 512 bytes / 512 bytes
      16. Disk identifier: 0x12a8e921
      17. Device Boot Start End Blocks Id System
      18. /dev/sdd1 * 2048 29364223 14681088 83 Linux
      19. /dev/sdd2 29364224 39090175 4862976 5 Extended
      20. /dev/sdd5 29366272 39090175 4861952 82 Linux swap / Solaris
      21. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
      22. Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
      23. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      24. Units = sectors of 1 * 512 = 512 bytes
      25. Sector size (logical/physical): 512 bytes / 4096 bytes
      26. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      27. Disk identifier: 0x00000000
      28. Device Boot Start End Blocks Id System
      29. /dev/sdc1 1 4294967295 2147483647+ ee GPT
      30. Partition 1 does not start on physical sector boundary.
      31. WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
      32. Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
      33. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      34. Units = sectors of 1 * 512 = 512 bytes
      35. Sector size (logical/physical): 512 bytes / 4096 bytes
      36. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      37. Disk identifier: 0x00000000
      38. Device Boot Start End Blocks Id System
      39. /dev/sde1 1 4294967295 2147483647+ ee GPT
      40. Partition 1 does not start on physical sector boundary.
      41. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
      42. Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
      43. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      44. Units = sectors of 1 * 512 = 512 bytes
      45. Sector size (logical/physical): 512 bytes / 4096 bytes
      46. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      47. Disk identifier: 0x00000000
      48. Device Boot Start End Blocks Id System
      49. /dev/sda1 1 4294967295 2147483647+ ee GPT
      50. Partition 1 does not start on physical sector boundary.
      51. WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util fdisk doesn't support GPT. Use GNU Parted.
      52. Disk /dev/sdf: 120.0 GB, 120034123776 bytes
      53. 256 heads, 63 sectors/track, 14536 cylinders, total 234441648 sectors
      54. Units = sectors of 1 * 512 = 512 bytes
      55. Sector size (logical/physical): 512 bytes / 512 bytes
      56. I/O size (minimum/optimal): 512 bytes / 512 bytes
      57. Disk identifier: 0x00000000
      58. Device Boot Start End Blocks Id System
      59. /dev/sdf1 1 234441647 117220823+ ee GPT
      Display All


      cat /etc/mdadm/mdadm.conf

      Source Code

      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=nas:DataA UUID=2b9f2ad4:73d43eeb:fe93f168:f33e43de
      Display All
    • Don't use partitioned disks to conform mdadm raids, just use plain raw block devices sdb, sdc, etc. not sdb1 or sdc1. Go to the physical disk section and wipe the disks until the partition table had been erased. Then create the mirror again, format, mount and reboot to check persistentency.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server