RAID 1 has been degraded OMV 2.2 Stoneburner

  • Hi Guys, I`m new to this forum. However already read a lot of threads regarding this magic operating system. Never got any problems, but...!!


    RAID-1 array stopped working after reboot. Each reboot it starts from one of the hard drives and shows the data previously synced + new data saved only at this partition. Need to dafe the data and remount the RAID without data loss. Is it possible? Please help :(


    I got new motherboard ASrock J3160DC-ITX and use it with 65W 19VDC adapter.
    I use 2x3TB WD RED hard drives
    OMV installed on the 2.5 HDD
    I use 3 cooulers 140mm x 1 + 80mm x2


    Here is what you`ve been recently asking
    1.
    root@UncleJack-NAS:~# cat /proc/mdstat
    Personalities :
    unused devices: <none>


    2.
    root@UncleJack-NAS:~# blkid
    /dev/sdb1: LABEL="Raid1" UUID="fe802f3e-2ff0-4d84-b58e-cc3eb8353e8f" TYPE="ext4"
    /dev/sda1: UUID="e0d05c9b-94ff-4b23-82e9-4e26eebdb9e3" TYPE="ext4"
    /dev/sda5: UUID="c4ecfb61-3b32-4560-b749-6726038e1b97" TYPE="swap"
    /dev/sdc1: LABEL="Raid1" UUID="fe802f3e-2ff0-4d84-b58e-cc3eb8353e8f" TYPE="ext4"


    3.
    root@UncleJack-NAS:~# fdisk -l | grep "Disk "


    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.



    WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    Disk identifier: 0x0000556f
    Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
    Disk identifier: 0x00000000
    Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
    Disk identifier: 0x00000000
    4.
    root@UncleJack-NAS:~# cat /etc/mdadm/mdadm.conf
    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #


    # by default (built-in), scan all partitions (/proc/partitions) and all
    # containers for MD superblocks. alternatively, specify devices to scan, using
    # wildcards if desired.
    #DEVICE partitions containers


    # auto-create devices with Debian standard permissions
    CREATE owner=root group=disk mode=0660 auto=yes


    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>


    # instruct the monitoring daemon where to send mail alerts
    MAILADDR root


    # definitions of existing MD arrays


    5.
    root@UncleJack-NAS:~# mdadm --detail --scan --verbose
    root@UncleJack-NAS:~# mdadm --detail --scan --verbose
    root@UncleJack-NAS:~# mdadm --assemble --scan
    mdadm: No arrays found in config file or automatically
    root@UncleJack-NAS:~#


    # This file was auto-generated on Mon, 29 Jun 2015 06:41:20 +0000
    # by mkconf 3.2.5-5


    Many Thanks!

    • Offizieller Beitrag

    I have yet to figure out how to keep arrays from disappearing on reboot.


    mdadm --assemble --verbose --force /dev/md127 /dev/sd[ab]1
    omv-mkconf mdadm

    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!

  • Hi ryecoaaron!


    Tried the below commands - doesn`t work!


    root@UncleJack-NAS:~# mdadm --assemble --verbose --force /dev/md127 /dev/sd[bc]1
    mdadm: looking for devices for /dev/md127
    mdadm: no recogniseable superblock on /dev/sdb1
    mdadm: /dev/sdb1 has no superblock - assembly aborted




    root@UncleJack-NAS:~# omv-mkconf mdadm
    update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
    W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
    W: mdadm: no arrays defined in configuration file.


    Thank you!

Jetzt mitmachen!

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