Greetings,
This seems to be the end result after BIOS upgrade now that UEFI RAID is incorporated into the BIOS and not in a Legacy Option ROM. You are the second person I've talked with, and it is certainly concerning for those of us who use RAID. I'm on SSD's with an option ROM. Its the m.2's that appear to be susceptible to this hazard.
Since you are past troubleshooting, we can only speculate on what you might have been able to try. Did you try removing one drive, and setting the existing RAID values in BIOS without creating a new array and writing metadata to the remaining disk member? If so and that failed, the only remaining option is to re-create the array and restore an image from back up. (or re-install)
Of course nothing replaces a system image. Hardware breaks, Arrays fail and the harder lessons are the self inflicted ones. Painful for sure and new build or old, I feel for you man.
In these cases, a back up should always be your first step. I always disconnect my drives when performing a BIOS upgrade. But I have not yet performed a BIOS update on a UEFI RAID z170/z270 BIOS with m.2's.
SOP is that you upgrade and restore from back up. Its just common practice, but its easy to get caught off guard as the whole implementation of M.2 support in the main BIOS has been evolving rapidly the last few years. Hopefully you are stable now and won't need to upgrade again. If you do , the back up you mentioned will ease the pain.