What Armando Ferreira said is correct.
You just needed to set it to raid mode again.
If you installed windows again after that though you're kinda screwed.
Well, kinda, there is a fix, you have to manually zero out the boot loader that got put there by the new windows install so the raid rom will detect the old boot loader, you may have to manually swap the cables around to force it to detect it.
I spent around a week or 2 working on this, horrible nightmare lol.
Good ole' winhex and testdisk saved my butt.
Lost a few exe's though lol.
But most of my stuff was intact.
Mine wasn't from updating the bios, it was trying to install windows 32bit, the driver on the site is bad for 32bit (it just doesn't work, I eventually found another...).
Windows complained, I didn't care, just thought it odd, my ssd isn't in the array anyways so I went ahead.
Windows wrote a new bootsector on my 2nd raid drive (it had no business doing so...), screwed over detection of my raid rom, lost everything, years of work.
I only figured it out when I was manually looking for files I needed to copy with winhex, by hand, looking for file headers and footers.
That's when I noticed my drives were backwards, the header was 64k after the 1st chunk of data, only noticed that when I recoverd and avi that have it's data swapped.
So I byte swapped it, worked, got the idea to zero out the 1st 64k in the array, and then manaually swaped the cables, and bam, raid rom detect the drives correctly.
Then it was up to testdisk to recover it.
Very freakin scary.
4tb...
