Unable to activate Startup Recovery Manager on 3ware RAID Array

This is beginning to annoy me to no end... worst of all, it's my own stupid fault for the problem existing in the first place and now there seems to be no undoing it. I have been running a 465 gig RAID5 array on a 3ware 7506 controller with no problems for quite some time. I do not run my OS (XPsp2) from the array, and instead have it on a separate 160 gig drive. Initially, I created a Secure Zone using True Image (8.0.791) of the same size as my OS partition at the beginning of the array and made countless backups with no problems. I also activated the Startup Recovery Manager with no problems, however, being the perfectionist that I am, I was bothered by the 7+ meg of wasted space at the very beginning of the array because the Secure Zone was not an active partition.

Realizing it probably wouldn't work, but figuring it would be easy enough to undo, I converted the Secure Zone to active using Disk Director (9.0.534). Of course it didn't work and gave me the MBR Error 3 upon rebooting. After some browsing I found the ISO in these forums that replaces the MBR and ran that, which fixed the problem. Then came the real problem, after deleting the Secure Zone and re-creating it True Image gives me the "This disk is not available while booting and you will not be able to restore images except through Windows" error and will not activate the Startup Recovery Manager.

So there I stand... what was not a problem before is a problem now and no amount of updating (to 8.0.826) or reinstalling True Image will change it. Yes I admit it was my own foolishness that brought this on, but I would very much like to have the Startup Recovery Manager working again. Any ideas?

 

Hello Jagur,

Thank you for choosing Acronis Disk Backup Software.

Could you please create Acronis Report in the way described at Acronis Help Post and send it to support@acronis.com along with the link to this thread? We will investigate the problem and your disk/partition layout and provide you with the solution.

Thank you.
--
Ilya Toytman

 

Solved the problem... a silly BIOS setting wasn't allowing the RAID array to be seen as bootable I'm going to go kick myself now...