RAID 5 Missing

    • OMV 1.0
    • Resolved
    • RAID 5 Missing

      Hi all,

      I had a disk fail and now my RAID 5 is missing. I replaced the faulty HDD, but still no luck. I have had a look through some of the threads and tried a few things, but nothing has worked. Here is what seems to be the required information:

      blkid:
      /dev/sda1: UUID="0f72f2fc-e1fe-4266-8b68-6d161df6914e" TYPE="ext4"
      /dev/sda5: UUID="70a0f915-bdb1-4b73-9514-68bde5029345" TYPE="swap"
      /dev/sdc: UUID="37f96e4f-5cda-2828-282b-10765bd12256" UUID_SUB="8b21a8d7-f0a5-bc26-8fad-c07da9964417" LABEL="openmediavault:Data" TYPE="linux_raid_member"
      /dev/sdd: UUID="37f96e4f-5cda-2828-282b-10765bd12256" UUID_SUB="6000a1ca-f8a0-102a-1848-1bb7ec55dc77" LABEL="openmediavault:Data" TYPE="linux_raid_member"


      cat /proc/mdstat
      Personalities : [raid6] [raid5] [raid4]
      md127 : inactive sdc[3] sdd[4]
      3907027120 blocks super 1.2

      unused devices: <none>


      Any suggestions on how I might go about resurrecting my RAID? I am relatively inexperienced at linux, so simple, step-by-step help appreciated.

      Thanks in advance :)
    • Thanks - I missed that. Here is the rest of the information:

      fdisk -l
      Disk /dev/sda: 250.1 GB, 250059350016 bytes
      255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00084bdc

      Device Boot Start End Blocks Id System
      /dev/sda1 * 2048 468553727 234275840 83 Linux
      /dev/sda2 468555774 488396799 9920513 5 Extended
      /dev/sda5 468555776 488396799 9920512 82 Linux swap / Solaris

      Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
      255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk identifier: 0x00000000

      Disk /dev/sdb doesn't contain a valid partition table

      Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
      255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk identifier: 0x00000000

      Disk /dev/sdc doesn't contain a valid partition table

      Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
      255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk identifier: 0x00000000

      Disk /dev/sdd doesn't contain a valid partition table


      cat /etc/mdadm/mdadm.conf
      # mdadm.conf
      #
      # Please refer to mdadm.conf(5) for information about this file.
      #

      # by default, scan all partitions (/proc/partitions) for MD superblocks.
      # alternatively, specify devices to scan, using wildcards if desired.
      # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      # used if no RAID devices are configured.
      DEVICE partitions

      # auto-create devices with Debian standard permissions
      CREATE owner=root group=disk mode=0660 auto=yes

      # automatically tag new arrays as belonging to the local system
      HOMEHOST <system>

      # definitions of existing MD arrays
      ARRAY /dev/md/Data metadata=1.2 spares=1 name=openmediavault:Data UUID=37f96e4f:5cda2828:282b1076:5bd12256

      # instruct the monitoring daemon where to send mail alerts
      MAILADDR
      MAILFROM root


      mdadm --detail --scan --verbose
      mdadm: cannot open /dev/md/Data: No such file or director


      The disks (all 2TB) are:
      sda VB0250EAVER
      sdb TOSHIBA DT01ACA2
      sdc WDC WD20EFRX-68E
      sdd TOSHIBA DT01ACA2

      Thanks.

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

    • mdadm --stop /dev/md127
      mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
      update-initramfs -u
      omv 4.1.13 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!
    • Thanks very much for that. I had to change
      mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]

      to
      mdadm --assemble --force --verbose /dev/md127 /dev/sd[cd]

      and then add the new drive, but it is now assembling. Thanks for your help!

      Would I be better off (in terms of backup) changing from RAID 5 to 2 x RAID 1?