Raid fail : how to destroy it ?

  • Hi,


    my raid fail, i'd like to destroy it to use mergeFS.
    But it's always say it's busy, so i can't delete it in OMV.


    In the peripheral (sorry, maybe not the right word, i use OMV in french), i see the raid peripheral, but the status is "missing" and i can't do anything (no unmount, no delete etc)


    Thanks for your help , i can't make other file system or anything since the raid fail (but i still got acces to my data and btw, they are backuped on another NAS)

    • Offizieller Beitrag

    That is the correct command if you array is /dev/md0


    Try unmounting the filesystem with umount /dev/md0


    It might be easier to boot a rescue cd (like systemrescuecd) that won't try mounting it.

    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!

  • umount /dev/md0 give no answer


    i've made : mdadm --detail /dev/md0


    /dev/md0:
    Version : 1.2
    Creation Time : Sun Sep 16 23:22:47 2018
    Raid Level : linear
    Array Size : 21487941560 (20492.50 GiB 22003.65 GB)
    Raid Devices : 5
    Total Devices : 5
    Persistence : Superblock is persistent


    Update Time : Sun Sep 16 23:22:47 2018
    State : clean
    Active Devices : 5
    Working Devices : 5
    Failed Devices : 0
    Spare Devices : 0


    Rounding : 0K


    Name : bart-nas:stockage (local to host bart-nas)
    UUID : 8efca549:86714fd7:d3d0ebc2:67a522cc
    Events : 0


    Number Major Minor RaidDevice State
    0 8 0 0 active sync /dev/sda
    1 8 32 1 active sync /dev/sdc
    2 8 64 2 active sync /dev/sde
    3 8 80 3 active sync /dev/sdf
    4 8 96 4 active sync

    • Offizieller Beitrag

    Cannot get exclusive access to /dev/md0:Perhaps a running process, mounted filesystem or active volume group?

    Have you deleted all the share references, SMB, Rsync, Shared Folders. You can delete the share without deleting the content.

    • Offizieller Beitrag

    i have to delete the reference ?

    Technically no :) mdadm should stop the raid, the only other option would be stop services or remove smb, rsync or anything referencing the shares, I think that's why the suggestion using the systemrescuecd might be the better option and you can load from omv-extras.

    • Offizieller Beitrag

    umount /dev/md0 give no answer

    That means it unmounted (that is the Linux way - message on error). You should be able to stop the array now.

    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!

  • i removed all excepted a share (not in samba, the share for the users acces) because i can't...


    I've looked about the rescue CD in omvExtras, i can't find too :( I got an old usb key to boot on it, how can i find a easy rescue CD ?


    and ... THANKS AGAIN to you !!

    • Offizieller Beitrag

    I got an old usb key to boot on it, how can i find a easy rescue CD ?

    http://www.system-rescue-cd.org/

    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

    but i wont have a GUI, so i'll have to destroy the raid with command lines and i don't know how to do (i guess you already realized i'm a bit noob in linux )

    cat /proc/mdstat will show you the array name (probably still /dev/md0) and the drives that are in the array. Post this output if you want help with next commands.
    mdadm --stop /dev/md0 will stop the array
    mdadm --zero-superblock /dev/sdX will wipe the array info from the drive specified (replace the X in sdX with one of your drives)
    wipefs -a /dev/sdX will wipe any signatures from the drive
    dd if=/dev/zero of=/dev/sdX bs=1M count=2000 will zero the first 2000 megs of the drive (just something I like to do).
    repeat until all drives

    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!

  • Thank you very much, it's worked, i don't have any raid now !


    Just a last thing, i still got the old device in file system .... i got n/a in all collumns, and missing in statuts, i can't remove it in web client , there is a way to do with command line ?

    • Offizieller Beitrag

    i got n/a in all collumns, and missing in statuts, i can't remove it in web client , there is a way to do with command line ?

    Does it say it is referenced? You should be able to delete it from the web interface if it is not referenced. If it is referenced, delete the shared folders using it (you will have to remove those shared folders from the services if they are in use).

    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

    he don't allow me to delete (delete button is inactive)

    Then that shared folder is probably still being referenced by plugins and/or services.

    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!

  • weird, i checked all (smb, plex, rsync, virtualbox) ... is there a way to find what still reference it, a log or something maybe ? (transmission doesn't use it, it's on another shared folder/HD)


    it's referenced and missing :/

    • Offizieller Beitrag

    Install the openmediavault-resetperms plugin and it will add a tab - Access Rights Management -> Shared Folders -> Shared Folders in Use. It will show you where it is being referenced.

    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!