[SOLVED] RAID5 Missing?

  • Hello everyone i have or at least use to have a Raid5 in ext4 FS with 3 disk 1TB each, suddenly now is missing i am runnig a old version of OVM 0.2.7.4 after some forum check and google this is the data that i could collect so far:


    fdisk -lu


    Disk /dev/sda: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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: 0x0004caa7


    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 308584447 154291200 83 Linux
    /dev/sda2 308586494 312580095 1996801 5 Extended
    /dev/sda5 308586496 312580095 1996800 82 Linux swap / Solaris


    Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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/sdd: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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/sdd doesn't contain a valid partition table


    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.



    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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/sdb doesn't contain a valid partition table


    cat /proc/mdstat
    Personalities :
    md127 : inactive sdc[0](S) sdb[2](S) sdd[1](S)
    2930284680 blocks super 1.2

    unused devices: <none>


    grep mdadm /var/log/syslog
    Feb 19 11:47:01 nasdmz mdadm[6128]: DeviceDisappeared event detected on md device /dev/md/nasdmz:RAID5
    Feb 19 11:52:51 nasdmz mdadm[1883]: DeviceDisappeared event detected on md device /dev/md/nasdmz:RAID5
    Feb 19 13:49:19 nasdmz mdadm[2106]: DeviceDisappeared event detected on md device /dev/md/nasdmz:RAID5
    Feb 19 14:20:44 nasdmz kernel: [ 1952.046471] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.046476] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.070001] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.070005] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.071244] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.071248] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.077297] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.077301] mdadm: sending ioctl 1261 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.077426] mdadm: sending ioctl 800c0910 to a partition!
    Feb 19 14:20:44 nasdmz kernel: [ 1952.077430] mdadm: sending ioctl 800c0910 to a partition!


    so if anyone can give a hand, or drop some light over here would be great. Thanks for your time and for OMV.
    Sorry for my english.

    • Offizieller Beitrag

    All the drives are marked as spares. Just went through this with another forum member. I don't think it ever worked though. Not sure what causes it. I would read that topic and still try the following:


    mdadm --assemble /dev/md127 /dev/sd[bcd] --verbose --force

    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!

  • Ok, this is what hapens first


    mdadm --assemble /dev/md127 /dev/sd[bcd] --verbose --force


    and i get this


    mdadm: looking for devices for /dev/md127
    mdadm: cannot open device /dev/sdb: Device or resource busy


    so i stop the the md127 with


    mdadm --stop /dev/md127


    then try again and:


    mdadm: looking for devices for /dev/md127
    mdadm: /dev/sdb is identified as a member of /dev/md127, slot 2.
    mdadm: /dev/sdc is identified as a member of /dev/md127, slot 0.
    mdadm: /dev/sdd is identified as a member of /dev/md127, slot 1.
    mdadm: added /dev/sdd to /dev/md127 as 1
    mdadm: added /dev/sdb to /dev/md127 as 2
    mdadm: added /dev/sdc to /dev/md127 as 0
    mdadm: /dev/md127 has been started with 2 drives (out of 3). This can't be good.


    after that i try
    mdadm --assemble --scan --force and get:


    mdadm: /dev/md/nasdmz:RAID5 assembled from 1 drive - not enough to start the array


    any idea? the data is lost :(


    Thank for you time.

    • Offizieller Beitrag

    What do you get from cat /proc/mdstat now?

    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!

  • this is what it shows


    cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md126 : inactive sdb[2](S)
    976761560 blocks super 1.2

    md127 : active raid5 sdc[0] sdd[1]
    1953522688 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]

    • Offizieller Beitrag

    That is much better than the other thread. We have something to work with and the data should not be lost :) You should actually be able to mount /dev/md127 and see your files. The following will stop md126, zero the superblock, and add it to the old raid. It will have to rebuild which will take a long time but it should be ok.


    mdadm --stop /dev/md126
    mdadm --zero-superblock /dev/sdb
    mdadm --add /dev/md127 /dev/sdb

    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!

  • So muchhh tahnks right now is rebuilding:


    Personalities : [raid6] [raid5] [raid4]
    md127 : active raid5 sdb[3] sdc[0] sdd[1]
    1953522688 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
    [>....................] recovery = 1.2% (12259328/976761344) finish=177.5min speed=90551K/sec

    unused devices: <none>


    it will take some time like you said 3hr almost but that is OK thanks again i will make a backup of the data afterward, one more question, it is safe to upgrade the system, there are any chance of losing any data?

    • Offizieller Beitrag

    Upgrading the system should not cause you to lose the data on the array. You might want to move to 0.3 and then 0.4 when upgrading.

    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!