can't bind in Raid5 after reinstall from OMV3

    • Offizieller Beitrag

    Select each drive from the array in the Physical Disks tab and click Wipe.
    Create new in raid management.
    Create new filesystem in filesystems tab.
    Mount new filesystem.

    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!

  • ok,
    last question before I do this.
    What will be happen with the data on it, loose I them after that ?


    And which methode for wipe recommend you " secure or quick?


    edit
    at the moment I'm not sure to wipe my disk.
    So I type the last commands from this thread in putty ,and now
    have I another output for cat /etc/mdadm/mdadm.conf & mdadm --assemble --scan


    • Offizieller Beitrag

    The data seems to be gone now. It will really be gone after wiping it. I would use quick.


    The duplicate line should be removed from mdadm.conf but I don't think that is causing the problem.

    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!

  • confuse error in fstab , because blkid says the ext4 is on sdc


    Code
    root@DoggiNas:~# blkid
    /dev/sda: UUID="de78e9c6-c5a2-647e-c01c-f1092ad82856" UUID_SUB="7f0aba23-2979-7069-f5ac-a365ec4c5f55" LABEL="DoggiNas:doggi" TYPE="linux_raid_member"
    /dev/sdb: UUID="de78e9c6-c5a2-647e-c01c-f1092ad82856" UUID_SUB="b159821d-29ff-751b-d736-63e0bb49cf05" LABEL="DoggiNas:doggi" TYPE="linux_raid_member"
    /dev/sdc1: UUID="6a490532-3b24-46aa-a584-ae49e6a07abe" TYPE="ext4" PARTUUID="a21f89a7-01"
    /dev/sdc5: UUID="90d69f5d-117d-47ca-81a5-436ef36083e2" TYPE="swap" PARTUUID="a21f89a7-05"
    /dev/sdd: UUID="de78e9c6-c5a2-647e-c01c-f1092ad82856" UUID_SUB="89f2e673-dc6d-e87e-d4f3-13de30e2973d" LABEL="DoggiNas:doggi" TYPE="linux_raid_member"
    • Offizieller Beitrag

    sdc is your OS drive.

    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!

  • :( there was no solution to rescued my data from the old Raid,
    So I have wipe it and created an new ext4 sys.



    Big thanks to you ryecoaaron for you support and your patience



    This thread can be closed

Jetzt mitmachen!

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