A stall at 99 % might indicate that the recovery process is having trouble retargeting the restored system to the hardware. This might sound strange, but the recovery process does have to account for the new hard disk(s) in the process, even where everything else remains the same. Even changing partition sizes on the original disk(s) can trigger the need to retarget the image to what is perceived as new disk hardware. If the drive controller and everything wlse remains the same, then there is generally no need to do a Restore Anyware when just changing disks.. When changing to the controller on the mainboard, you were correct to do a Restore Anyware
I have on occasion run into the situation were new drives were just not compatible with the controller. Sometimes the restores would go off without a hitch, but still not be able to use the drive(s) due to controller and drive incompatibilities.
A original array being degraded could be contributing to the problem. BESR is definitely Garbage In, Garbage out (GIGO) sensitive. Sometimes, imaging the array with the option to skip bad sectors can help you bypass this issue. A verification of the image with the Recovery Point Browser would at least prove that all the files in the image can be opened.
If I were in your shoes, what would I try next? Regardless of which controller and the fact that it is the same hardware, I would do a Restore Anyware with the -DED (Delete Existing Drivers) switch checked off. The hope is that this will force the recovery process to redetermine the RAID and NIC drivers needed and get past the stalled retargeting process. There is a -PFD (Prompt for Drivers) switch too, but that is a last resort use switch. In any case have your drivers handy because you may be prompted for them anyway. Info on accessing the Restore Anyware switches below:
http://seer.entsupport.symantec.com/docs/293847.htm
Best of Luck
