mdadm: cannot open /dev/md/diskpool

  • I'm constantly getting the following error when trying to create a notfication service,


    Zitat


    Failed to execute command 'export LANG=C; omv-mkconf mdadm 2>&1': mdadm: cannot open /dev/md/diskpool: No such file or directory


    I'm assuming this has to do with an old software raid I had which died a rather painful death. Not sure on how I should proceed


    There's nothing in /dev/md

    Code
    root@dunder:/# ls -l /dev/md
    total 0


    Any pointers?

    • Offizieller Beitrag

    Is the old array still listed in /etc/mdadm/mdadm.conf?

    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!

  • Is the old array still listed in /etc/mdadm/mdadm.conf?


    No, it isn't


    Does OMV store the array details somewhere in an database perhaps?

    • Offizieller Beitrag

    Nope. Only filesystems. Do you have an n/a filesystem?

    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!

  • Nope. Only filesystems. Do you have an n/a filesystem?


    Yeah, I did (one drive which was/is damaged was listed as N/A and still in the array)


    I fixed the issue by going to File Systems and removed the N/A device. Then in terminal I did

    Code
    mdadm --stop /dev/md127
    mdadm --remove /dev/md127
    mdadm --zero-superblock /dev/sd*


    Now it works as expected :)

    • Offizieller Beitrag

    That was my next plan :)

    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!

  • I had this same issue after switching from a RAID array to using mhddfs and was easily resolved by running these commands:


    Code
    mdadm --stop /dev/md127
    mdadm --remove /dev/md127


    Thank you!! :P

Jetzt mitmachen!

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