Raid 1 Missing After Reboot

    • OMV 2.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Seems ok, try this update-initramfs -u and if the raid1 is in sync try reboot.
      Note: if assembly fails again at boot, your raid will enter degrade and again you'll start another rebuild process.

      USB flash drive should be ok if you know at least is new and you're using the flash memory plugin.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • @subzero79, I executed the command but I am not sure the RAID changed as it did not appear in the GUI. Do you want me to resync the RAID, or should it already be in sync?

      Source Code

      1. update-initramfs -u
      2. update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
      Images
      • omv_fs_image_1.png

        39.52 kB, 1,188×495, viewed 157 times
      • omv_raid_image_1.png

        31.22 kB, 824×487, viewed 164 times
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.

      The post was edited 2 times, last by DeviousDog ().

    • No, you have to rebuild,
      But before that why don't you upgrade your kernel to backport one? That platform looks quite new,
      Go to omv-extras press the button install backport kernel, reboot and then resync again and run initramfs update as before.

      If that doesn't work, then maybe @ryecoaaron can help you and has more ideas

      Last option would be to discard the sw raid and mirror contents from one drive to another using rsync one or two times a day.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Raid 1 Missing After Reboot

      I am currently re syncing the drives. During the backports kernel install, even though it completed successfully, near the end it said there was a possibly missing firmware with the file ending .fw. When should I run initramfs update? After re sync or during re sync?
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.

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

    • Raid 1 Missing After Reboot

      I did update-initramfs -u again and below is the output.

      Display Spoiler

      Source Code

      1. update-initramfs -u
      2. update-initramfs: Generating /boot/initrd.img-3.16.0-0.bpo.4-amd64
      3. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
      4. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
      5. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
      6. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
      7. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
      8. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
      9. W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • Ok so I did reboot after rebuild and initramfs update and the HW RAID did vanish. I know the firmware missing has to do with the Realtek Gigabit Ethernet Controller (I know, not the best for Linux). The backports kernel had many updates pending so I installed them and the fw missing vanished. Does the motherboard have to be RAID Compatible for SW RAID because I know B150 does not support RAID? I believe until I upgrade to an Xeon or AMD Zen platform and get HW RAID, i'll backup my Data to a USB HDD and use rsync for the HDDs.
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • Raid 1 Missing After Reboot

      I'll do that but RSYNC will have to do if RAID disappears. Maybe the RAID issue is a configuration problem and doing what you said above should work.
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • In an attempt to make a backup of my data through windows 7 with EXT2FSD, I observed that the HDD were formatted in RAW Format, which is unusual as during a RAID Rebuild as soon as the disks finished resyncing, they were recognized as EXT4 FS HDD. Could the disks being identified as RAW FS by OMV cause the issues?
      Images
      • omv_RAW_FS_HDD_1.png

        25.46 kB, 631×506, viewed 159 times
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • @subzero79 After I backup the data, should I perform a quick or secure wipe on the HDD?
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • After I performed a quick wipe and rebuild the RAID 1 Array, for some reason the data and the file system were still on the drives. I believe that a secure wipe will be necessary. My question is as to why would the file system persist after a quick wipe?
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • This is extremely strange and unusual. After performing the quick wipe and rebooting the server, the RAID persisted. Would it be possible that dual file systems on a HDD caused the conflicts?
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.

      The post was edited 1 time, last by DeviousDog: clarity ().

    • Below are some of the relevant configurations after the persistent RAID after reboot if it assists anyone with a similar issue.

      cat /proc/mdstat

      Display Spoiler

      Source Code

      1. ​cat /proc/mdstat
      2. Personalities : [raid1]
      3. md0 : active raid1 sda[0] sdb[1]
      4. 1953383360 blocks super 1.2 [2/2] [UU]
      5. unused devices: <none>


      blkid

      Display Spoiler

      Source Code

      1. ​blkid
      2. /dev/sdc1: UUID="7da352e3-1578-4917-9069-2627852d9716" TYPE="ext4"
      3. /dev/sdc5: UUID="336fba35-418a-4060-81bd-e0b23a83d3ce" TYPE="swap"
      4. /dev/sdb: UUID="77926dd5-6090-65bc-476d-09c5983cffbd" UUID_SUB="dbf65560-ba99-57ee-8d7d-cdcf44a62de0" LABEL="OpenMediaVault:WDRaid1" TYPE="linux_raid_member"
      5. /dev/sda: UUID="77926dd5-6090-65bc-476d-09c5983cffbd" UUID_SUB="0927140f-6dbd-bd54-fbf0-394305e84870" LABEL="OpenMediaVault:WDRaid1" TYPE="linux_raid_member"
      6. /dev/md0: LABEL="WDRaid1" UUID="52e47c5e-01d3-4fca-ba05-dcbafc611780" TYPE="ext4"


      fdisk -l

      Display Spoiler

      Source Code

      1. ​ fdisk -l
      2. Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
      3. 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
      4. Units = sectors of 1 * 512 = 512 bytes
      5. Sector size (logical/physical): 512 bytes / 512 bytes
      6. I/O size (minimum/optimal): 512 bytes / 512 bytes
      7. Disk identifier: 0x00000000
      8. Disk /dev/sdb doesn't contain a valid partition table
      9. Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
      10. 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
      11. Units = sectors of 1 * 512 = 512 bytes
      12. Sector size (logical/physical): 512 bytes / 512 bytes
      13. I/O size (minimum/optimal): 512 bytes / 512 bytes
      14. Disk identifier: 0x00000000
      15. Disk /dev/sda doesn't contain a valid partition table
      16. Disk /dev/md0: 2000.3 GB, 2000264560640 bytes
      17. 2 heads, 4 sectors/track, 488345840 cylinders, total 3906766720 sectors
      18. Units = sectors of 1 * 512 = 512 bytes
      19. Sector size (logical/physical): 512 bytes / 512 bytes
      20. I/O size (minimum/optimal): 512 bytes / 512 bytes
      21. Disk identifier: 0x00000000
      22. Disk /dev/md0 doesn't contain a valid partition table
      23. Disk /dev/sdc: 15.5 GB, 15522070528 bytes
      24. 255 heads, 63 sectors/track, 1887 cylinders, total 30316544 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: 0x000968db
      29. Device Boot Start End Blocks Id System
      30. /dev/sdc1 * 2048 28983295 14490624 83 Linux
      31. /dev/sdc2 28985342 30314495 664577 5 Extended
      32. /dev/sdc5 28985344 30314495 664576 82 Linux swap / Solaris
      Display All
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • @subzero79 yes it is now working correctly. I believe the issue had something to do with partition issues and OMV creating 2 file systems on the same HDD, which can cause issues. My question is as to why OMV would not recognize the partitions and /or indicate that there is an already existing filesystem.
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.
    • I've did not notice that the actual disks had a GPT already before being conformed into an array. In general mdadm has no trouble handling devices with a partition table, but I've learned from experience in this forum that having one or more devices conforming the array with a partition present causes this kind of issues. I mentioned it in this thread, but i missed your fdisk post, otherwise that would've been my first suggestion, destroy and create again.

      bottom line, mdadm works better with plain raw block devices.
      New wiki
      chat support at #openmediavault@freenode IRC | Spanish & English | GMT+10
      telegram.me/openmediavault broadcast channel
      openmediavault discord server
    • Raid 1 Missing After Reboot

      Thank you for your assistance @subzero79 and @ryecoaaron. Hopefully this assists someone as I have seen in the forums that there are many issues with RAID.
      "It is better to offer no excuse than a bad one." -George Washington

      Current OMV Server Configuration: 8GB Avexir DDR4 Ram, Pentium G4400 Dual Core CPU, Corsair CS550M Power Supply, Fractal Design Core 1100, 2X2 TB WD RE4 HDD, MSI B150M-PRO VD, 2X ISTARUSA 5.25 to Hot Swap Drive Trays.