RAID Mirror pair state - clean and false

  • I had rebooted my OMV, and was surprised to find my RAID devices gone. Fortunately using this command *seemed* like it restored the /dev/md4 target


    Code
    mdadm --assemble --verbose /dev/md4


    But now I see a /dev/md4 showing in a clean state, and a /dev/md4p1 in a false state (see attachment). How do I clean this up? I can't tell if the Mirror is actually healthy or not. The 'mdadm --query --detail' and '/proc/mdstat' seems to report that it is.


    I had another RAID device that was similar, and thought that since the one looked right, I could delete the /dev/md#p1 - not so! Doing that made both disappear

  • Just a note, you can cut&paste from putty.


    Your output of cat /proc/mdstat doesn't show any problems. What is the query detail of md2?

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I used a print screen to show the OMV RAID Management screen, along with the putty output.


    Correct, the 'cat /proc/mdstat' doesn't show any problems, but what's up with the /dev/md4p1 showing under RAID management? /dev/md4 is an iSCSI block target for a Windows client. I do see that /dev/md4p1 appears under File Systems as an ntfs volume (created by the Windows client), but I didn't expect to see it in either RAID Management or File Systems. Is that normal?

  • I'm seeing the same thing for another iSCSI target to a Linux client, correctly showing it as an ext4 partition.


    These appeared after having rebooted, and having done an "mdadm --assemble --scan".


    So, this bug is just a presentation issue, and not indicating a problem then? As long as the /dev/md4 shows clean, my mirror is "healthy"?

  • So, this bug is just a presentation issue, and not indicating a problem then? As long as the /dev/md4 shows clean, my mirror is "healthy"?

    I think it is just presentation based on your other output.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!