Sytem Files issue on RAID1 from single drive setup

  • Hi all,


    A few days ago I got a new HDD and wanted to create a RAID1 from my original OMV setup that only included 1 drive (4TB WD Blue). To do so, I based myself on the following thread: Create RAID 1 with existing Data Disk


    All went pretty smoothly,





    => except for one thing: 2 lines in the System Files don't seem to be in order.



    - the 1st one appeared once I wiped out the original disk before including it in the RAID : as a result, "N/A" and "Missing" status.


    - the 2nd one: "linux_raid_member" and "N/A" which points to the original HDD since it's in the RAID



    Here is the content of "fdisk -l" command:



    As a result I get there's an issue in the partition table, but I don't know how to fix it.


    Many thanks in advance for your help!

    Edit : more results from the following commands


    - cat /proc/mdstat command:

    Code
    $ sudo cat /proc/mdstat
    Personalities : [raid1]
    md0 : active raid1 sdc1[2] sdb1[1]
          3906886272 blocks super 1.2 [2/2] [UU]
    
    
    unused devices: <none>


    - blkid command:

    Code
    $ sudo blkid
    /dev/sda1: UUID="a9e79f7b-2764-4388-a69a-b9c9de5de7e4" TYPE="ext4"
    /dev/sda5: UUID="34f08ca6-0e01-4e06-ad33-b5dbcd3402ff" TYPE="swap"
    /dev/sdb1:
     UUID="b01f8082-be76-9175-127b-400da1aff51b" 
    UUID_SUB="f3d835c8-a2c1-3ce3-b031-be6fc00f3366" LABEL="ServeurMaison:0" 
    TYPE="linux_raid_member"
    /dev/md0: UUID="89460968-4bc6-4ce1-9958-5621dbb13270" TYPE="ext4"
    /dev/sdc1: LABEL="rd1" UUID="5e8305ea-1f49-41ec-9600-906a0394c686" TYPE="ext4"


    - mdadm --detail --scan --verbose command:

    Code
    $ sudo mdadm --detail --scan --verbose
    ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=ServeurMaison:0 UUID=b01f8082:be769175:127b400d:a1aff51b
       devices=/dev/sdc1,/dev/sdb1
    • Offizieller Beitrag

    You have extra entries in the mntent section of /etc/openmediavault/config.xml from not unmounting drives before wiping. You need to manually clean up the config.

    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!