That's definately the safest bet, I had read forums where there was success migrating a RAID1 by first removing the disks from the array (i.e. making them single disks that are no longer part of a RAID) then putting them into a new system with a different chipset and letting that chipset detect the drives as a damaged array, creating but not initializing the array.
However, as I couldn't find susbstantial proof and that the old system is hosed (unable to remove the drives from the array, which I guess removes some of the important proprietary metadata), the point is somewhat moot. There is no doubt in my mind that you'd be able to recover data using various forensic tools (some freely available), but it would require copious ammounts of time and work.
@coyoty_tm, at this point I'd try to figure out the chipset on the old board (maybe look at old receipts for a model muber of the board or system?) and try to either find a direct replacement or at least one with the same chipset. If you can't do any of that, might just want to throw caution to the wind, get a decent board, plug 1 pf the devices in and see if the controller recognizes it as part of a damaged RAID1 array, letting the new board rebuild it (after shutting down and plugging in the second one).
Edit: Also proves the value of using a backup scheme that doesn't have a single point of failure. Even though I could setup a redunant RAID on my hardware RAID card, I instead image it weekly to another drive that'd not on the controller. In case of mobo or RAID card failure, I'd be set back no more than a week since that image drive is readable in any system that supports SATA.
Facebook
Twitter
Instagram