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.

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?

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.

I would backup data.
Wipe the raid, wipe the disks, zero superblock. Check with mdadm the disks have no metadata and then reconstruct the array, put some irrelevant data and reboot to see if this time persists.

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?

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?

@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.

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.