Raid1 split clean/degraded

    • OMV 2.x
    • Resolved
    • Raid1 split clean/degraded

      Hi all
      After last night weekly reboot, today I've got a split clean/degraded raid.
      I think I didn't built it good at start, and now I've got this trouble.
      Any help will be welcome.

      There's my outputs

      Source Code

      1. root@omv:~# cat /proc/mdstat
      2. Personalities : [raid1]
      3. md127 : active (auto-read-only) raid1 sdb1[0]
      4. 976630272 blocks super 1.2 [2/1] [U_]
      5. md0 : active raid1 sda1[2]
      6. 976630272 blocks super 1.2 [2/1] [_U]
      7. unused devices: <none>

      Source Code

      1. root@omv:~# blkid
      2. /dev/sda1: UUID="ae5367fc-cb91-4e2f-959f-89ca2761b302" TYPE="ext4" LABEL="RAID2"
      3. /dev/sdb1: UUID="9cc05082-eb0c-81a3-8a6d-e2b38bff6c7f" UUID_SUB="fe67fb12-b7c9-b007-6e7f-4009e9a7c0e6" LABEL="omv:0" TYPE="linux_raid_member"
      4. /dev/sdc1: LABEL="Media" UUID="a915c5d4-d6f3-4a46-a93f-ed2cc30bd4ec" TYPE="ext4"
      5. /dev/sdd1: LABEL="3TB" UUID="865844eb-d9c4-427f-badd-d57a09a652bc" TYPE="ext4"
      6. /dev/sde1: LABEL="3TB" UUID="ce82cbd6-c5ef-494a-8cf3-0c09fd23abd0" TYPE="ext4"
      7. /dev/sde2: LABEL="MP3" UUID="43b40d65-511f-4c9b-9995-ae28c6ee5b5a" TYPE="ext4"
      8. /dev/md0: LABEL="RAID" UUID="9d2b7b1d-50fc-4400-9a17-8033849fa72e" TYPE="ext4"
      9. /dev/md127: LABEL="RAID" UUID="9d2b7b1d-50fc-4400-9a17-8033849fa72e" TYPE="ext4"

      Source Code

      1. root@omv:~# fdisk -l
      2. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
      3. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
      4. 256 heads, 63 sectors/track, 121126 cylinders, total 1953525168 sectors
      5. Units = sectors of 1 * 512 = 512 bytes
      6. Sector size (logical/physical): 512 bytes / 4096 bytes
      7. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      8. Disk identifier: 0x00000000
      9. Device Boot Start End Blocks Id System
      10. /dev/sda1 1 1953525167 976762583+ ee GPT
      11. Partition 1 does not start on physical sector boundary.
      12. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      13. Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
      14. 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
      15. Units = sectors of 1 * 512 = 512 bytes
      16. Sector size (logical/physical): 512 bytes / 4096 bytes
      17. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      18. Disk identifier: 0x00000000
      19. Device Boot Start End Blocks Id System
      20. /dev/sdb1 1 1953525167 976762583+ ee GPT
      21. Partition 1 does not start on physical sector boundary.
      22. Disk /dev/sdc: 500.1 GB, 500107862016 bytes
      23. 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
      24. Units = sectors of 1 * 512 = 512 bytes
      25. Sector size (logical/physical): 512 bytes / 512 bytes
      26. I/O size (minimum/optimal): 512 bytes / 512 bytes
      27. Disk identifier: 0x00085558
      28. Device Boot Start End Blocks Id System
      29. /dev/sdc1 2048 976773119 488385536 83 Linux
      30. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
      31. Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
      32. 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
      33. Units = sectors of 1 * 512 = 512 bytes
      34. Sector size (logical/physical): 512 bytes / 4096 bytes
      35. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      36. Disk identifier: 0x00000000
      37. Device Boot Start End Blocks Id System
      38. /dev/sdd1 1 4294967295 2147483647+ ee GPT
      39. Partition 1 does not start on physical sector boundary.
      40. Disk /dev/sde: 163.9 GB, 163928604672 bytes
      41. 255 heads, 63 sectors/track, 19929 cylinders, total 320173056 sectors
      42. Units = sectors of 1 * 512 = 512 bytes
      43. Sector size (logical/physical): 512 bytes / 512 bytes
      44. I/O size (minimum/optimal): 512 bytes / 512 bytes
      45. Disk identifier: 0x0008519b
      46. Device Boot Start End Blocks Id System
      47. /dev/sde1 2048 40962047 20480000 83 Linux
      48. /dev/sde2 40962048 320172031 139604992 83 Linux
      49. Disk /dev/md0: 1000.1 GB, 1000069398528 bytes
      50. 2 heads, 4 sectors/track, 244157568 cylinders, total 1953260544 sectors
      51. Units = sectors of 1 * 512 = 512 bytes
      52. Sector size (logical/physical): 512 bytes / 4096 bytes
      53. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      54. Disk identifier: 0x00000000
      55. Disk /dev/md0 doesn't contain a valid partition table
      56. Disk /dev/md127: 1000.1 GB, 1000069398528 bytes
      57. 2 heads, 4 sectors/track, 244157568 cylinders, total 1953260544 sectors
      58. Units = sectors of 1 * 512 = 512 bytes
      59. Sector size (logical/physical): 512 bytes / 4096 bytes
      60. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      61. Disk identifier: 0x00000000
      62. Disk /dev/md127 doesn't contain a valid partition table
      Display All

      Source Code

      1. root@omv:~# mdadm --detail --scan --verbose
      2. ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=omv:0 UUID=9cc05082:eb0c81a3:8a6de2b3:8bff6c7f
      3. devices=/dev/sda1
      4. mdadm: cannot open /dev/md/0_0: No such file or directory
      omv 2.2.13 stoneburener | 64 bit | omvextrasorg 2.13.9
      Intel Core2Duo @ 2.13 GHz
    • The problem is your array is using partitions (you didn't create with OMV). You want to zero the superblock on the partition instead of the entire disk. mdadm --zero-superblock /dev/sdb1
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      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!
    • Users Online 1

      1 Guest

    • Tags