RAID5: Missing 2/4 Devices

  • Hi,this is my first post in this forum. Due to the fact that I may loose data, it would be nice if you give me support to find the right people who can help me.my Raid5 ((1.18 Kralizec) failed to start after runing stable since months.


    After Reboot:
    1. All disks are available, showing temprature and more
    2. S.M.A.R.T showing 0 errors for every device, all checks are passed
    3. Storage -> Raid Management: is empty
    4. Storage -> Filesystems: no md0 available
    5. Fdisk -l
    xxx:~# fdisk -lDisk /dev/sdb: 160.0 GB, 160041885696 bytes255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0x000a989cDevice Boot Start End Blocks Id System/dev/sdb1 * 2048 299839487 149918720 83 Linux/dev/sdb2 299841534 312580095 6369281 5 Extended/dev/sdb5 299841536 312580095 6369280 82 Linux swap / SolarisDisk /dev/sda: 160.0 GB, 160041885696 bytes255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0x0001eb1bDevice Boot Start End Blocks Id System/dev/sda1 * 2048 299839487 149918720 83 Linux/dev/sda2 299841534 312580095 6369281 5 Extended/dev/sda5 299841536 312580095 6369280 82 Linux swap / SolarisDisk /dev/sde: 3000.6 GB, 3000592982016 bytes255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk identifier: 0x00000000Disk /dev/sde doesn't contain a valid partition tableDisk /dev/sdd: 3000.6 GB, 3000592982016 bytes255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk identifier: 0x00000000Disk /dev/sdd doesn't contain a valid partition tableDisk /dev/sdf: 3000.6 GB, 3000592982016 bytes255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk identifier: 0x00000000Disk /dev/sdf doesn't contain a valid partition tableDisk /dev/sdc: 3000.6 GB, 3000592982016 bytes255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk identifier: 0x00000000Disk /dev/sdc doesn't contain a valid partition table


    6. cat /proc/mdstatPersonalities : [raid6] [raid5] [raid4]
    md0 : inactive sdd[2] sde[3]
    5860271024 blocks super 1.2
    unused devices: <none>


    I checked the health of the filesystem every week. It can not imagine, that two disks will faile at the same time twice within 6 Months on differen arrays. I had the same problem with different disks on a differen server some months before.Any idea if and how I can recover my data?


    With my best regards

    • Offizieller Beitrag

    Thank you for putting the output in a code box but that is brutal to read (if you are human) when the line feeds are gone.


    Try:
    mdadm --stop /dev/md0
    mdadm --assemble /dev/md0 /dev/sd[cdef] --verbose --force


    If it starts re-assembling, keep checking the output of: cat /proc/mdstat


    By the way, what kind of drives are these?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

    Einmal editiert, zuletzt von ryecoaaron ()

Jetzt mitmachen!

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