Upgraded to stoneburner now raid is missing

    • OMV 2.x
    • Upgraded to stoneburner now raid is missing

      Hi Guys,

      I probably made a mistake by not un-mounting the raid array before upgrading to stoneburner. I made a complete re-install to my ssd system disk but now OMV doesn't see raid array although it sees physical disks.
      I'm really in need of help here.

      Source Code

      1. root@OMVmaxi:~# cat /proc/mdstat
      2. Personalities : [raid6] [raid5] [raid4]
      3. md127 : inactive sdb[0] sdd[2] sdc[1]
      4. 8790406536 blocks super 1.2


      Source Code

      1. root@OMVmaxi:~# blkid
      2. /dev/sdc: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="f7ee4689-fc08-baf4-2cd0-05c11114f104" LABEL="omv2:omv2" TYPE="linux_raid_member"
      3. /dev/sdf: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="4ce9e842-b7e4-783f-5dfa-ece257681110" LABEL="omv2:omv2" TYPE="linux_raid_member"
      4. /dev/sdb: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="0679e4eb-b5fb-832d-382f-d597465f55fc" LABEL="omv2:omv2" TYPE="linux_raid_member"
      5. /dev/sde: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="1256d9c1-a8fa-fdf5-335c-bde3b63400a8" LABEL="omv2:omv2" TYPE="linux_raid_member"
      6. /dev/sdd: UUID="27f66ba7-0bf4-a9fd-48f8-2763f7ad8793" UUID_SUB="05919054-c5eb-d548-8002-a1b658d1c523" LABEL="omv2:omv2" TYPE="linux_raid_member"
      7. /dev/sda1: UUID="f63e4bf3-5f8e-42e8-8884-a4fcec06a9aa" TYPE="ext4"
      8. /dev/sda5: UUID="b7fdbf58-7fcf-4bbd-b9bf-1f3f8569b204" TYPE="swap"


      Source Code

      1. root@OMVmaxi:~# fdisk -l
      2. Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
      3. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      4. Units = sectors of 1 * 512 = 512 bytes
      5. Sector size (logical/physical): 512 bytes / 4096 bytes
      6. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      7. Disk identifier: 0x00000000
      8. Disk /dev/sdb doesn't contain a valid partition table
      9. Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
      10. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      11. Units = sectors of 1 * 512 = 512 bytes
      12. Sector size (logical/physical): 512 bytes / 4096 bytes
      13. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      14. Disk identifier: 0x00000000
      15. Disk /dev/sdc doesn't contain a valid partition table
      16. Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
      17. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      18. Units = sectors of 1 * 512 = 512 bytes
      19. Sector size (logical/physical): 512 bytes / 4096 bytes
      20. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      21. Disk identifier: 0x00000000
      22. Disk /dev/sde doesn't contain a valid partition table
      23. Disk /dev/sda: 60.0 GB, 60022480896 bytes
      24. 255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
      25. Units = sectors of 1 * 512 = 512 bytes
      26. Sector size (logical/physical): 512 bytes / 512 bytes
      27. I/O size (minimum/optimal): 512 bytes / 512 bytes
      28. Disk identifier: 0x000a4e60
      29. Device Boot Start End Blocks Id System
      30. /dev/sda1 * 2048 112383999 56190976 83 Linux
      31. /dev/sda2 112386046 117229567 2421761 5 Extended
      32. /dev/sda5 112386048 117229567 2421760 82 Linux swap / Solaris
      33. Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
      34. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      35. Units = sectors of 1 * 512 = 512 bytes
      36. Sector size (logical/physical): 512 bytes / 4096 bytes
      37. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      38. Disk identifier: 0x00000000
      39. Disk /dev/sdf doesn't contain a valid partition table
      40. Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
      41. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      42. Units = sectors of 1 * 512 = 512 bytes
      43. Sector size (logical/physical): 512 bytes / 4096 bytes
      44. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      45. Disk identifier: 0x00000000
      46. Disk /dev/sdd doesn't contain a valid partition table
      Display All


      Source Code

      1. root@OMVmaxi:~# cat /etc/mdadm/mdadm.conf
      2. # mdadm.conf
      3. #
      4. # Please refer to mdadm.conf(5) for information about this file.
      5. #
      6. # by default (built-in), scan all partitions (/proc/partitions) and all
      7. # containers for MD superblocks. alternatively, specify devices to scan, using
      8. # wildcards if desired.
      9. #DEVICE partitions containers
      10. # auto-create devices with Debian standard permissions
      11. CREATE owner=root group=disk mode=0660 auto=yes
      12. # automatically tag new arrays as belonging to the local system
      13. HOMEHOST <system>
      14. # instruct the monitoring daemon where to send mail alerts
      15. MAILADDR root
      16. # definitions of existing MD arrays
      17. # This file was auto-generated on Mon, 29 Jun 2015 06:41:20 +0000
      18. # by mkconf 3.2.5-5
      Display All


      Source Code

      1. root@OMVmaxi:~# cat /etc/mdadm/mdadm.conf
      2. # mdadm.conf
      3. #
      4. # Please refer to mdadm.conf(5) for information about this file.
      5. #
      6. # by default (built-in), scan all partitions (/proc/partitions) and all
      7. # containers for MD superblocks. alternatively, specify devices to scan, using
      8. # wildcards if desired.
      9. #DEVICE partitions containers
      10. # auto-create devices with Debian standard permissions
      11. CREATE owner=root group=disk mode=0660 auto=yes
      12. # automatically tag new arrays as belonging to the local system
      13. HOMEHOST <system>
      14. # instruct the monitoring daemon where to send mail alerts
      15. MAILADDR root
      16. # definitions of existing MD arrays
      17. # This file was auto-generated on Mon, 29 Jun 2015 06:41:20 +0000
      18. # by mkconf 3.2.5-5
      19. root@OMVmaxi:~# ^C
      20. root@OMVmaxi:~# mdadm --detail --scan --verbose
      21. mdadm: cannot open /dev/md/omv2: No such file or directory
      22. root@OMVmaxi:~#
      Display All
    • You have to activate your inactive raid, see the mdstats output. Use google how to do that.
      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
    • mdadm --stop /dev/md127
      mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcdef]
      mdadm --examine --scan >> /etc/mdadm.conf
      update-initramfs -u
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!

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

    • @ryecoaaron

      Thanks but here it is

      Source Code

      1. ​root@OMVmaxi:~# mdadm --stop /dev/md127
      2. mdadm: stopped /dev/md127
      3. root@OMVmaxi:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcdef]
      4. mdadm: looking for devices for /dev/md127
      5. mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
      6. mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
      7. mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
      8. mdadm: /dev/sde is identified as a member of /dev/md127, slot 3.
      9. mdadm: /dev/sdf is identified as a member of /dev/md127, slot 4.
      10. mdadm: forcing event count in /dev/sdf(4) from 656730 upto 656734
      11. mdadm: clearing FAULTY flag for device 4 in /dev/md127 for /dev/sdf
      12. mdadm: Marking array /dev/md127 as 'clean'
      13. mdadm: added /dev/sdc to /dev/md127 as 1
      14. mdadm: added /dev/sdd to /dev/md127 as 2
      15. mdadm: added /dev/sde to /dev/md127 as 3 (possibly out of date)
      16. mdadm: added /dev/sdf to /dev/md127 as 4
      17. mdadm: added /dev/sdb to /dev/md127 as 0
      18. mdadm: /dev/md127 has been started with 4 drives (out of 5).
      19. root@OMVmaxi:~# update-initramfs -u
      20. update-initramfs: Generating /boot/initrd.img-3.16.0-0.bpo.4-amd64
      21. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
      22. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
      23. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
      24. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
      25. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
      26. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
      27. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
      28. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      29. root@OMVmaxi:~# mdadm --examine --scan >> /etc/mdadm.conf
      Display All




    • You have one failed drive and the other is missing. Check your connectors. You can't start raid 5 with two missing disks.
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Just because smart says it is ok does not mean it is ok. I agree that does probably mean the cable is ok. All I can say is that I help with so many raid issues that I get them mixed up. I am really tired of all these arrays not starting.

      What I do know is that mdadm is saying one drive failed and another drive doesn't have array info. With raid 5, that is very bad. If you zero one drive to re-add it to the array, you might lose all data. You need to be able to start the array with four drives and have it working to zero one drive. Because my other command didn't work, there aren't many options left.

      I would run longer smart tests on each drive.
      omv 4.0.19 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Sorry for the late replay.
      I was out of Country for 14 days and I hadn’t got time to deal with server.
      Made self-long tests for the five disks an all completed without error. I have dumb question. Although I’m nearly sure I haven’t done it. Can it be caused by swapped sata cables?