RAID 5 Missing After Drive Failure

  • I have a 8GB DOM to boot with + 5x 2TB RAID 5 array that had a single drive failure. After replacing the burned drive, the RAID array seems to be missing and I can't find it in the menus any longer to remount it. Here are the outputs of the "cat /proc/mdstat", "blkid" and "fdisk -l" commands. Can someone point out what went wrong here and better yet, how to get my array back? I had a drive fail a month ago and replaced that drive no problem. The array rebuilt and was accessible the whole time. This time it's just nowhere to be found?


  • Try:


    mdadm --stop /dev/md127
    mdadm --assemble /dev/md127 /dev/sd[bcdef] --verbose --force

    omv 5.6.12 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


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

  • Humm. Nope. Since "sdb" is the new drive I just put in, does anything need to be done to it first?


    root@archive:~# mdadm --stop /dev/md127
    mdadm: stopped /dev/md127


    root@archive:~# mdadm --assemble /dev/md127 /dev/sd[bcdef] --verbose --force
    mdadm: looking for devices for /dev/md127
    mdadm: no recogniseable superblock on /dev/sdb
    mdadm: /dev/sdb has no superblock - assembly aborted

  • Try assembling without sdb and then add it later.

    omv 5.6.12 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6.2 | kvm plugin 5.1.6
    omv-extras.org plugins source code and issue tracker - github


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

  • Yep, that did it. The array came back up as clean and degraded. Added sdb back in after and the array is happily rebuilding now.


    Thanks for your help!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!