Linear RAID suddenly disappeard

  • Hi,


    I rebooted my NAS, and ... i've lost my RAID . It was a linear one. All my disks seems ok. My filesystem still exist but can't found the raid .. .When i go in the RAID management section, i try to create a new one ... I can't because it don't find any hard drive ... Any chance to get back my data and raid (i've got a backup but i hope to not use it...)


    Thanks a lot for the help, i'm totally lost :(

  • i've found this on another topic and tried :


    Code
    cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : inactive sda[0] sdh[5](S) sdg[4] sdf[3] sde[2] sdc[1]
          23441325072 blocks super 1.2

    and i've launched



    seems my raid is still there .. .but inactive. how can i active it back ?
    i got an error on the sdb2 ?


    Thanks

    • Offizieller Beitrag

    seems my raid is still there .. .but inactive. how can i active it back ?
    i got an error on the sdb2 ?

    Inactive doesn't mean you will be able to get it back. Hope you have backup. You need to stop the old array first.


    mdadm --stop /dev/md0
    mdadm --assemble --verbose --force /dev/md0 /dev/sd[ahgfec]

    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!

  • thanks for your message. Yes, i guess it's possible to lose .. .i hope i wont but i got a backup, if i can avoid the restoring time, it's cool ;)
    the commands gave me thoses results :


    root@bart-nas:/sharedfolders# mdadm --stop /dev/md0
    mdadm: stopped /dev/md0


    root@bart-nas:/sharedfolders# mdadm --assemble --verbose --force /dev/md0 /dev/sd[ahgfec]
    mdadm: looking for devices for /dev/md0
    mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
    mdadm: /dev/sde is identified as a member of /dev/md0, slot 2.
    mdadm: /dev/sdf is identified as a member of /dev/md0, slot 3.
    mdadm: /dev/sdg is identified as a member of /dev/md0, slot 4.
    mdadm: /dev/sdh is identified as a member of /dev/md0, slot -1.
    mdadm: added /dev/sdc to /dev/md0 as 1
    mdadm: added /dev/sde to /dev/md0 as 2
    mdadm: added /dev/sdf to /dev/md0 as 3
    mdadm: added /dev/sdg to /dev/md0 as 4
    mdadm: added /dev/sdh to /dev/md0 as -1
    mdadm: added /dev/sda to /dev/md0 as 0
    mdadm: failed to RUN_ARRAY /dev/md0: No such device or address

    • Offizieller Beitrag

    What is the output of: ls -al /dev/md*


    I haven't seen this error before. If there is a different node in the output from above, use that node. Otherwise, try:


    mdadm --assemble --verbose --force --update=summaries /dev/md0 /dev/sd[ahgfec]

    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!

  • root@bart-nas:/sharedfolders# ls -al /dev/md*
    brw-rw---- 1 root disk 9, 0 oct. 19 14:51 /dev/md0


    and


    root@bart-nas:/sharedfolders# mdadm --assemble --verbose --force --update=summaries /dev/md0 /dev/sd[ahgfec]
    mdadm: looking for devices for /dev/md0
    mdadm: --update=summaries not understood for 1.x metadata

    • Offizieller Beitrag

    Ok, what is the output of cat /proc/mdstat Maybe it didn't stop?

    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!

  • root@bart-nas:/sharedfolders# cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : inactive sda[0](S)
    3906887512 blocks super 1.2


    unused devices: <none>



    (thanks for your time !!)

    • Offizieller Beitrag

    Try the stop and assemble commands again from my earlier post.

    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!

  • root@bart-nas:/sharedfolders# mdadm --stop /dev/md0
    mdadm: stopped /dev/md0



    root@bart-nas:/sharedfolders# mdadm --assemble --verbose --force /dev/md0 /dev/sd[ahgfec]
    mdadm: looking for devices for /dev/md0
    mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
    mdadm: /dev/sde is identified as a member of /dev/md0, slot 2.
    mdadm: /dev/sdf is identified as a member of /dev/md0, slot 3.
    mdadm: /dev/sdg is identified as a member of /dev/md0, slot 4.
    mdadm: /dev/sdh is identified as a member of /dev/md0, slot -1.
    mdadm: added /dev/sdc to /dev/md0 as 1
    mdadm: added /dev/sde to /dev/md0 as 2
    mdadm: added /dev/sdf to /dev/md0 as 3
    mdadm: added /dev/sdg to /dev/md0 as 4
    mdadm: added /dev/sdh to /dev/md0 as -1
    mdadm: added /dev/sda to /dev/md0 as 0
    mdadm: failed to RUN_ARRAY /dev/md0: No such device or address



    it's the same ... the -1 is not weird ?

    • Offizieller Beitrag

    it's the same ... the -1 is not weird ?

    strange. Maybe it was a spare? How many drives are in the array? Try the commands again but remove the h from the brackets in the assemble command.

    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!

  • looks better i guess


    root@bart-nas:/sharedfolders# mdadm --assemble --verbose --force /dev/md0 /dev/sd[agfec]
    mdadm: looking for devices for /dev/md0
    mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
    mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
    mdadm: /dev/sde is identified as a member of /dev/md0, slot 2.
    mdadm: /dev/sdf is identified as a member of /dev/md0, slot 3.
    mdadm: /dev/sdg is identified as a member of /dev/md0, slot 4.
    mdadm: added /dev/sdc to /dev/md0 as 1
    mdadm: added /dev/sde to /dev/md0 as 2
    mdadm: added /dev/sdf to /dev/md0 as 3
    mdadm: added /dev/sdg to /dev/md0 as 4
    mdadm: added /dev/sda to /dev/md0 as 0
    mdadm: /dev/md0 has been started with 5 drives.



    but .. still no access to my data


    spare disk is a free disk not in the raid ? (it was with a S flag i saw in another command)

    • Offizieller Beitrag

    i see it in the web GUI .. should i mount it ? (i prefer ask than break all)

    No. that will cause it to create a new entry. mount -a from the command line should mount everything.

    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!

    • Offizieller Beitrag

    Can i ask you something more, can we know why this crashed ?

    I wish I knew that answer. Sometimes it is because the system was not shutdown properly. Other times, it is because the hardware spins up the drives too late. Never found the reason for a lot of these issues. While I have never had issues with raid, I don't use it on most of my systems now (mergerfs and rsnapshot are good enough for most of my uses).

    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!

  • ok ok ... well, i guess i can't change to mergefs ?


    I got 2 omv NAS (this one as main and one backup). I'm looking for a nice backup ... should i watch rsnapshot or Greyhole ? (in anothers words, wich is the easiest and the most reliable ?)


    actually, i make the sync manually, that's painful

    • Offizieller Beitrag

    i guess i can't change to mergefs ?

    Nope. You need to format each drive to use it in this case.


    should i watch rsnapshot or Greyhole ?

    I use rsync to sync two OMV systems. Then I use rsnapshot on both systems. This does use a lot of space but very reliable and I have lots of safety factors involved. Greyhole isn't support as a plugin anymore.

    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!

Jetzt mitmachen!

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