Raid 5 fails to mount and rebuild?

  • Greetings I found out that one of my Raid 5 array of 4, 3TB WD RED disks failed. OMV would not recognize the file system either but still showed the disks.

    I have never used mdadm until now but from what I have tried this command seemed to be the silver bullet for most people in a similar situation as me.

    Code
    sudo mdadm --assemble --scan --verbose --force

    And here is the output.

    Any guidance on how to either get the three disks to mount together so I can off load the data or rebuild and new disk back into it would be much appreciated. Thank you.

  • ChibiButo

    Changed the title of the thread from “Raid 5 fails to rebuild” to “Raid 5 fails to mount and rebuild?”.
  • ssh into omv as root and post the output of the following;


    cat /proc/mdstat

    blkid

    cat /etc/mdadm/mdadm.conf

    fdisk -l | grep "Disk "

    Raid is not a backup! Would you go skydiving without a parachute?

  • I was able to mount my other good array (Nyaruko.local:Saber) on Linux Mint but not the one that had a disk with bad sectors.


    sudo cat /proc/mdstat

    Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]

    unused devices: <none>


    blkid

    /dev/sda1: UUID="52a72b84-5397-4119-b1ae-50cf47498c1e" TYPE="ext4" PARTUUID="3f88fd3a-01"

    /dev/sda3: UUID="6448-9AD7" TYPE="vfat" PARTUUID="3f88fd3a-03"

    /dev/sda5: UUID="e7911c56-e6a9-4f64-be74-71aa5ddb067a" TYPE="swap" PARTUUID="3f88fd3a-05"

    /dev/sda6: UUID="fefb9941-b289-4aec-837b-3ff02f3f953e" TYPE="ext4" PARTUUID="3f88fd3a-06"

    /dev/sdc: UUID="a01c8059-c7cc-3bef-6a07-3a4ab4728597" UUID_SUB="0cb1d5c5-113d-b61a-bf50-8f78562da6fb" LABEL="Nyaruko.local:Saber" TYPE="linux_raid_member"

    /dev/sdd: UUID="a01c8059-c7cc-3bef-6a07-3a4ab4728597" UUID_SUB="c06f1fe4-001e-024d-87a0-ff0760776a6e" LABEL="Nyaruko.local:Saber" TYPE="linux_raid_member"


    cat /etc/mdadm/mdadm.conf

    cat: /etc/mdadm/mdadm.conf: No such file or directory


    sudo fdisk -l | grep "Disk "

    Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors

    Disk model: INTEL SSDSCKKF18

    Disk identifier: 0x3f88fd3a

    Disk /dev/sdc: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors

    Disk model: WDC WD30EFRX-68E

    Disk /dev/sdd: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors

    Disk model: WDC WD30EFRX-68E

    Disk /dev/sde: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors

    Disk model: WDC WD30EFRX-68E

    Disk /dev/sdf: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors

    Disk model: WDC WD30EFRX-68E


    r18RCZz.png

  • Judging by the output from the above this is not an OMV issue;


    1) cat /proc/mdstat lists no raid information

    2) blkid lists 2 drives that have a possible raid signature

    3) mdadm conf shows no raid configuration

    4) fdisk whilst it may see the drives and list their information that's all the system is doing 'seeing them'

    5) The image is not of OMV

    Raid is not a backup! Would you go skydiving without a parachute?

  • Its really weird. I'm wondering if I should hook it up to a windows machine and use a retail piece of software just to see if it does anything.

  • I'm wondering if I should hook it up to a windows machine and use a retail piece of software just to see if it does anything.

    I don't see how that is going to help!!


    What hardware is this running on

    How did you set this raid up

    Have you run SMART tests on the 4 drives

    blkid sees only 2 of the 4 drives, if only one drive has failed it should see 3


    output of mdadm --detail /dev/md127

    Raid is not a backup! Would you go skydiving without a parachute?

  • Well it seems that 2 drives have failed which is par the course for my luck level. Looks like im just gonna have to switch to raid 6 in the future or use SSDs on raid 5 not sure exactly at least most of my photos where backed up on Google Photos.

Participate now!

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