RAID Array lost after powerfail

1. offizieller Beitrag

    Hi, I've been using OMV for several years now with no real problems, until now that is.


    Having had a power outage last night I've noticed this morning that I couldn't access anything stored on my OMV server. Initial (and basic) diag. from the WebGUI shows that my RAID array (named 'vol1') is status Online but not mounted.


    When I try to mount I get the error "Failed to mount '118297fb-5785-45e3-9210-3e202a280839': mount: no such partition found" Physically the disks are still there, as is the config for the array which shows it as clean, I'm simply unable to mount it.


    This isn't the first time the OMV server has been powered off accidentally, but this is the first time it has caused an issue.


    What else should I checked and what else can I do to try and restore it without data loss?


    Thanks in advanced,
    Gavin

    • Offizieller Beitrag

    Post the output from the commands in this thread.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | 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!

    • Offizieller Beitrag

    Sorry if my post was confusing. I just meant post the output on this thread from the commands on the other thread. Moved it for you and put in a code box.


    Try:


    mdadm --stop /dev/md127
    mdadm --assemble /dev/md127 /dev/sd[bc] --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.6 | 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!

    I realized what I'd done after I'd done it, sorry.


    Code
    root@omv:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@omv:~# mdadm --assemble /dev/md127 /dev/sd[bc] --verbose --force
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: added /dev/sdb to /dev/md127 as 0
mdadm: /dev/md127 has been started with 2 drives.
root@omv:~#


    Having ran that is there anything else I need to do as the volume is still showing as online but un-mountable.

    • Offizieller Beitrag

    Try rebooting if the output from cat /proc/mdstat doesn't show that it is syncing.

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | 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!

    Code
    root@omv:~# cat /proc/mdstat
Personalities : [raid1]
md127 : active (auto-read-only) raid1 sdb[0] sdc[1]
      1953513424 blocks super 1.2 [2/2] [UU]


unused devices: <none>


    Does that show that it's syncing or not?


    The server has since been shutdown/booted properly several times, but to no avail.

    • Offizieller Beitrag

    It shows that it is read only. Try


    mdadm --readwrite /dev/md127

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

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | 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!

    I see that now, though even after that it still wouldn't mount.


    I have now managed to get the array /dev/md127 mounted at /dev/vol1 using fstab and can ls the file structure from CLI. Good news.


    Bad news is that the file permission seem to be screwed. In as much that the WebGUI says the user 'gavinhatton' has read/write access to various SMB shares, but when accessing these from a windows client access is denied, is this likely to be related or this is this another issue altogether?

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden