ABR 11.5 MkRescue Rescues to the wrong disk when there is data onit

We are using the MkRescue utility for ABR11 and the TIB was created with the ASD4 boot media. The target system has a RAID-1 mirror and a RAID-5 array connected to an Intel RAID controller. The RAID-0 is LUN0 and shows up as sda from the Linux prompt and the RAID-5 as "sdb" in MkRescue (command prompt CTRL-ALT-F2). When you run "acrocmd list contents" on the TIB on the bootmedia from MkRescue command prompt (CTRL_ALT-F2) to view the contents of the TIB file it says "sda" and you see the partitions so it should go down on sda. All is good. When you Restore to the system and the RAID-1 is just initialized and blank the installation gets put on the RAID-1 as expected (and I can peek from the command prompt and run fdisk and see dev/sda is the RAID1). If there is data on the RAID-1 then MkRescue still sees the RAID-1 as "sda" (I can see this from the linux prompt BUT it puts the image down on the RAID-5! I see the RAID-5 getting hammered and fdisk shows the RAID-1 as sda and the RAID=5 as sdb. If we go into the RAID BIOS and re-initialize the RAID-1 then MkRescue puts the image on the RAID-1 like we expect.

The command being run is something like:

acrocmd restore disk --disk=all --loc=XXXX -aarc=Win7.tib (I am going off the top of my head)

MkRescue has the TIB file setup to deploy on sda and sda is the RAID-1 even if there is data on it but MkRescue is putting it on sdb (RAID-5) if data (an OS) is on the RAID-1.

Do you know how to prevent this?

Todd