After hard update the Raid 1 hdd shown as empty

    • OMV 5.x (beta)
    • geaves wrote:

      The you'll need to run omv-mkconf mdadm
      Done, without any issues.


      geaves wrote:

      Going back to your post 7 running mdadm --readwrite /dev/md127 should have brought the array back up as active.
      Done after but the result is:


      root@openmediavault:~# mdadm --readwrite /dev/md127
      mdadm: failed to set writable for /dev/md127: Device or resource busy

      Now the second drive weren't recognized.

      I feel like a noob right now !
    • geaves wrote:

      Nah, all been there, OK mdadm --stop /dev/md127 then run the command
      Done.

      root@openmediavault:~# mdadm --stop /dev/md127
      mdadm: stopped /dev/md127
      root@openmediavault:~# omv-mkconf mdadm
      update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.4-amd64
      W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      root@openmediavault:~#

      What the problem is, I don't know. No step forward, no solution. I'm getting desperate.
    • omv-mkconf mdadm should only be run after you have a working array. I would mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc] (not sure about the drives). If it is fine, then run the omv-mkconf command. If it is auto read only, run the readwrite command.
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.9
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Done

      root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sdc
      mdadm: looking for devices for /dev/md127
      mdadm: /dev/sdc is identified as a member of /dev/md127, slot 0.
      mdadm: no uptodate device for slot 1 of /dev/md127
      mdadm: added /dev/sdc to /dev/md127 as 0
      mdadm: /dev/md127 has been started with 1 drive (out of 2).
      root@openmediavault:~#
      root@openmediavault:~#
      root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sdb
      mdadm: looking for devices for /dev/md127
      mdadm: Found some drive for an array that is already active: /dev/md127
      mdadm: giving up.
      root@openmediavault:~# omv-mkconf mdadm
      update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.4-amd64
      root@openmediavault:~#

      Now from the recognized drive almost 400 Gb is taken and this seems to be the amount of stored data when I start these unexpected odyssey. The second drive still unrecognized.
    • I'll check that both drives are connected.

      Update:

      Checked and now the second drive is now recognized.


      root@openmediavault:~# lsblk
      NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
      sda 8:0 0 119.2G 0 disk
      ├─sda1 8:1 0 113.8G 0 part /
      ├─sda2 8:2 0 1K 0 part
      └─sda5 8:5 0 5.5G 0 part [SWAP]
      sdb 8:16 0 1.8T 0 disk
      sdc 8:32 0 1.8T 0 disk
      └─md127 9:127 0 1.8T 0 raid1
      root@openmediavault:~#

      The post was edited 1 time, last by Triebwerk ().

    • geaves wrote:

      cat /proc/mdstat
      root@openmediavault:~# cat /proc/mdstat
      Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
      md127 : active (auto-read-only) raid1 sdc[0]
      1953383360 blocks super 1.2 [2/1] [U_]

      unused devices: <none>
      root@openmediavault:~#


      geaves wrote:

      cat /etc/mdadm/mdadm.conf
      root@openmediavault:~# cat /etc/mdadm/mdadm.conf
      # mdadm.conf
      #
      # Please refer to mdadm.conf(5) for information about this file.
      #

      # by default, scan all partitions (/proc/partitions) for MD superblocks.
      # alternatively, specify devices to scan, using wildcards if desired.
      # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      # used if no RAID devices are configured.
      DEVICE partitions

      # 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>

      # definitions of existing MD arrays
      ARRAY /dev/md127 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
      root@openmediavault:~#

      geaves wrote:

      mdadm --detail --scan --verbose
      root@openmediavault:~# cat /etc/mdadm/mdadm.conf
      # mdadm.conf
      #
      # Please refer to mdadm.conf(5) for information about this file.
      #

      # by default, scan all partitions (/proc/partitions) for MD superblocks.
      # alternatively, specify devices to scan, using wildcards if desired.
      # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      # used if no RAID devices are configured.
      DEVICE partitions

      # 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>

      # definitions of existing MD arrays
      ARRAY /dev/md127 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
      root@openmediavault:~# ^C
      root@openmediavault:~# mdadm --detail --scan --verbose
      ARRAY /dev/md127 level=raid1 num-devices=2 metadata=1.2 name=openmediavault:Raid1 UUID=6f6bc262:bb6c50ca:ca2f7080:3ec12977
      devices=/dev/sdc
      root@openmediavault:~#

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().

      Post by Triebwerk ().

      This post was deleted by ryecoaaron: dupe ().
    • Ahmmm, I think posting only once is enough.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit