Attempting to recover from drive failure, can't find RAID

  • Hello All!


    I have a OMV based NAS I build with spare parts. Here are the relivant details.


    • OMV 2.2.5 (running off of a 8GB USB Thumb Drive)
    • AMD Phenom II x4 945 CPU, 4GB RAM, MSI MS7599 v3.1 MotherBoard
    • 7x 2TB HDD of various makes and models Configured into a RAID-6 Array


    Earlier this week one of the hard drive died taking the power supply with it. I have since replaced the Power Supply and the failed drive. I booted the system back up and logged onto the Web Interface. Under Storage -> Physical Disks, I can see 7 drive, the six working 2 TB HDD and the 8GB USB boot drive, however when I go to Storage -> RAID, no RAID is listed.


    I was expecting to see the RAID-6 array in a degraded state, but nothing is listed. I am not a Linux expert, so I need help in figuring out if the data is still recoverable and how to go about getting the RAID array recognized and working again. I have a replacement drive for drive 7 on the way, but since I was using RAID-6, I should still be able to function.


    My Questions:

    • Is my RAID-6 array with my data still out there and if so how can I get OMV to recognize it so that I can access the Data?


    -Uneventful


    The following is the output from my SSH session on the server.


    login as: root
    root@omv's password:
    Linux omv 3.2.0-4-amd64 #1 SMP Debian 3.2.81-1 x86_64


    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Wed Jul 15 19:57:07 2015
    root@omv:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md0 : inactive sdc[0] sda[5] sdg[4] sdf[3] sde[2] sdd[1]
    11720301072 blocks super 1.2


    unused devices: <none>
    root@omv:~# blkid
    /dev/sdd: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="8f953c1e-fcd2-0716-d978-3cb2a38a34f9" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sde: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="c6a24cc9-b776-d524-3ce2-eeb129c16170" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sdg: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="7cfe7408-47d0-5f02-95a6-cacf00b05a01" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sda: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="40712e3d-d65e-25be-b225-3fb03de020ff" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sdf: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="acb098f2-704f-b691-6087-6c0fec34ddde" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sdc: UUID="c803cd1c-123e-20b6-33b1-f08dfa085133" UUID_SUB="8ba0b609-2a87-dec9-47ec-d88209632f5f" LABEL="omv:Data" TYPE="linux_raid_member"
    /dev/sdb1: UUID="8b1879a6-8ba3-4f4e-8941-387bb382c884" TYPE="ext4"
    /dev/sdb5: UUID="b73e3bac-d6a5-41ca-8eba-6bc765795107" TYPE="swap"
    root@omv:~# fdisk -l


    Disk /dev/sda: 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/sda 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


    Disk /dev/sdg: 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/sdg doesn't contain a valid partition table


    Disk /dev/sdf: 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/sdf doesn't contain a valid partition table


    Disk /dev/sde: 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 / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000


    Disk /dev/sde 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 / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000


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


    Disk /dev/sdb: 7776 MB, 7776239616 bytes
    255 heads, 63 sectors/track, 945 cylinders, total 15187968 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: 0x000c79da


    Device Boot Start End Blocks Id System
    /dev/sdb1 * 63 14458499 7229218+ 83 Linux
    /dev/sdb2 14458500 15181424 361462+ 5 Extended
    /dev/sdb5 14458563 15181424 361431 82 Linux swap / Solaris
    root@omv:~# 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/md0 metadata=1.2 name=omv:Data UUID=c803cd1c:123e20b6:33b1f08d:fa085133
    root@omv:~# mdadm --detail --scan --verbose
    ARRAY /dev/md0 level=raid6 num-devices=7 metadata=1.2 name=omv:Data UUID=c803cd1c:123e20b6:33b1f08d:fa085133
    devices=/dev/sdc,/dev/sdd,/dev/sde,/dev/sdf,/dev/sdg,/dev/sda
    root@omv:~#

    • Offizieller Beitrag

    Try


    mdadm --stop /dev/md0
    mdadm --assemble --force --scan /dev/md0 /dev/sd[acdefg]

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • That worked! Thank you for your help.


    Just wondering if anyone knows if future versions of OMV might have this information and option available in the web interface or if this is something that will always be something you have to dig into the command line to fix?

    • Offizieller Beitrag

    I don't know how you would do this from the web interface. What is the problem with the command line? Generally, if you have server grade hardware, you don't have these issues.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!