Mirror RAID from QNAP to OMV

1. offizieller Beitrag

    Hello,

    I decided to move my drives from QNAP to OMV. In QNAP I had 2x2TB drives as a mirror. After inserting them into PC with OMV, the partitions appear in the Software RAID menu:

    Details: as follow:



    I care about the data on disk, so I don't want to format the drives, but I can't mount them as a File system. Maybe I'm doing something wrong? Please give me some tips :)

    • Offizieller Beitrag

    What is the output of:


    cat /proc/mdstat

    sudo blkid

    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!

    cat /proc/mdstat




    sudo blkid

    • Offizieller Beitrag

    sudo mdadm --readwrite /dev/md126 will make it readwrite.

    then I think you will have to do

    sudo vgscan

    sudo lvscan

    Then post the output of

    sudo blkid

    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 received two warnings:


    vgscan

    Code
    WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update.
Found volume group "vg1" using metadata type lvm2

    lvscan

    Code
    WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update.
inactive '/dev/vg1/lv544' [<18.54 GiB] inherit
inactive '/dev/vg1/lv1' [1.79 TiB] inherit



    And output of blkid

    • Offizieller Beitrag

    Run this:

    for vg in $(sudo vgs --noheadings --options vg_name); do echo "${vg}"; sudo vgck --updatemetadata ${vg}; done

    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!

    Output:


    Code
     WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update.
vg1
  WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update.
  WARNING: updating PV header on /dev/md126 for VG vg1.
    • Offizieller Beitrag

    sudo vgs

    sudo lvs

    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!

    • Offizieller Beitrag

    sudo ls -al /dev/mapper/


    You might actually see the filesystem in the Filesystems tab now too.

    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!

    ls -al /dev/mapper/

    Code
    total 0
drwxr-xr-x  2 root root      60 Dec 27 18:33 .
drwxr-xr-x 19 root root    3700 Dec 27 18:34 ..
crw-------  1 root root 10, 236 Dec 27 18:33 control

    Unfortunately, I can't see the filesystem

    • Offizieller Beitrag

    Ok


    sudo blkid

    sudo ls -al /dev/vg1

    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!

    blkid


    ls -al /dev/vg1

    Code
    ls: cannot access '/dev/vg1': No such file or directory
    • Offizieller Beitrag

    I would try rebooting and see if the filesystem shows up in the Filesystems tab after that. I'm not out of options but it is hard to not see everything.

    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!

    • Offizieller Beitrag
    Zitat von P_314

    Or is there some way to copy the data from one of these drives to another I have in OMV. It would be good enough for me.

    That is the point I am trying to get you to.


    sudo find /dev -name "vg1*"

    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!

    • Offizieller Beitrag

    sudo vgscan

    sudo lvscan

    sudo pvs

    sudo vgdisplay

    sudo lvdisplay

    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!

    • Offizieller Beitrag

    Ah, they are inactive.


    sudo lvchange -ay /dev/vg1/lv544

    sudo lvchange -ay /dev/vg1/lv1


    Then they should show up in the filesystems tab.

    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!

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden