Originally posted by: Marine
This info isn't really germane to the problem.
Not sure if that's directed to adapter/disk info, or to the mobo/RAM info. But if it's the former, I'd say that it's extremely relevant. People lump true hardware controllers, Promise/Highpoint hybrids, and Windows dynamic disks under the "RAID" label. But each of those is quite different as far an OS is concerned, especially for booting.
The SCSI array is built on Adaptec 320 host adapter and IBM 10K disks. The EIDE array is Promise on the Mobo.
OK, now I'm with you. So the "install" of the IDE array was the creation of array inside the controller BIOS after the machine POST'ed, correct?
The issue is simply that when I added the EIDE array to a stable fast working machine, I no longer can access the OS which is written to the SCSI RAID.
A couple things could be happening, I think. First off, both the Promise and the Adaptec arrays will appear to be SCSI devices, which could be confusing your boot order. Most RAID-capable mobo BIOS'es have a toggle to choose between a "true" SCSI controller and a Promise/Highpoint controller in cases where both are installed and the machine is set to boot to SCSI (your situation). See if your BIOS has such a toggle and make sure it is set to SCSI. Second, since both arrays will be seen as SCSI devices, they may appear differently to the boot loader when both are installed. But I think that that should be OK, provided that you set the boot order correctly. What happens if you turn off the Promise controller? Will it boot correctly, then? Finally, I've heard of rare situations where the expansion ROM's between two disk controllers just don't play well together. That's pretty unlikely, though. If you see boot-time messages for both the Adaptec and Promise cards, you should be fine. If not, you may need a different IDE RAID controller, or more black magic than I can provide.
I have tried to recover with both a boot disk and also with the WinXP CD. Neither can locate a Windows install.
That's odd - you should see the Windows install unless you accidently hosed your partition table. But I can't see why that would happen. Are you certain you've loaded necessary drivers (with F6) just after the CD starts up? I doubt XP has drivers for a U320 RAID card built-in, though I may be mistaken there.
So, again any recommendations to recover my existing OS would be best. Acceptable would be how to configure the machine to recognize both disk arrays in which case I'll just start from scratch. Thanks!
Again, I think you were going in the right general direction, but obviously something went wrong. I would install the base OS to the SCSI array with the Promise controller turned off in the BIOS. Then switch on the RAID controller in the BIOS, reboot, and ensure drivers are properly loaded before actually attaching the IDE drives and initializing the array. If it gets that far, but can't boot after attaching drives, then it's almost certainly a device ordering/addressing problem that can be fixed one way or another.
edit: clarified the last bit