SCSI Controller appears to take boot priority over on-board SATA controller
Posted on 2008-06-12
I have a WORKING Windows XP Home system with an ASUS A8N-E motherboard and 2 SATA RAID 0 arrays, configured using the on-board SATA RAID controller.
I am attempting to drop in a SCSI RAID 0 array using an Adaptec 2120S controller card from a different machine in order to retrieve the data from it. The machine that the SCSI array came from mysteriously died, however the controller and disks appear to work ok.
With the Adaptec controller card and SCSI disk array in the working system, the ASUS BIOS recognizes the SCSI array. In the BIOS I have set the SCSI array to have a lower boot priority than the primary SATA array, so that I can bring up the working Windows XP home system to copy the data from the SCSI array.
During the bootup cycle, the on-board SATA controller recognizes and verifies the two SATA arrays. Then the Adaptec BIOS is recognized, and verifies the array. I can also go into the Adaptec BIOS and view all the settings.
My problem is AFTER the Adaptec BIOS screen passes, I receive an NTLDR error. If I remove the SCSI array from the system, it boots up perfectly. With the SCSI array in the system, it would appear that the system is trying to boot off of the SCSI array, rather than the SATA array, even though I have specified it as a lower boot priority than the SATA array.
Is this some commonly known problem where SCSI controllers always have a higher boot priority over SATA controllers? What gives?