Thats a whole lot of information you left out of your first post
Two logicals, plus RAID array, both SSD and traditonal HD, Win 7 sys installed on RAID by mistake
Didnt think that was relevant to solve your prob?
FWIW, Win 7 needs boot files to be on a prim partition thats active.
The boot have to be on "C", they cant be on the sys reserved 100mb hidden no drive latter partition. But if you install with no reserved, and you only have one O/S, at boot Win will make it "C", no matter where it is and that partition whatever it was must be actve and contain bootmgr
If you are the type of person who is constantly changing things you should never make any extended/logicals, only primaries - 4 allowed per HDD
Based on tthis new info, and the fact no repairing options were allowed means you lost path continuity to active, or lost active designation for Win 7 in RAID. I still dont know the full story here, but you may also have created an active on each HDD, which means boot order is critical. In essence - your PC suffers from "confusion", not hardware breakdown
if it still doesnt work with what you are doing, you will have to study your disk management graphic - from another PC HDD if needed
For simpiest example here - the hidden reserved is primary/active with sys. The O/S is on "C" also primary not active with the boot files
Over and out!