• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SATA/SCSI boot issues

V

Vertigo Acid

2(-log[H+])4u
Joined
May 31, 2003
Messages
12,410
I've been running my OS off of a SCSI drive, 18gb 15K RPM IBM Ultrastar on an LSIU160 SCSI card, and had my SATA/PATA drives on a Promise SATA150 TX2+ card, and had no problems when I set the BIOS to boot off of SCSI. Now, I upgraded my SATA card to a Highpoint RocketRAID 1540 4 channel SATA card, but my system refuses to boot off the SCSI drive, instead just hanging around after the Highpoint is done detecting drives. I know it's not just literally freezing because it continues on to my Intel Pro 1000 MT NIC's BIOS options, and it'll boot if I don't have any drives attached. Seems to me like the BIOS doesn't know which "SCSI" card to boot off of, and so it's trying to boot from the SATA card instead. I've tried moving around the order of the cards, from SCSI in the top to SCSI in the bottom, and like it should it changed what order the each card reported its BIOS options, but I still can't make it boot off the SCSI. Any ideas? The only thing i've thought of is to put a boot-loader on the raptor I have lying around and then have it boot to the SCSI, but have no idea how make that work
 
find your PIRQ table

alternately play round robin with the controllers in the PCI slots
there could also be an issue with BIOS space
 
I'm betting you have too many boot ROMs. Yeah, same number as before, but the new one occupying too much UMB space. You can have no more than 128KB for boot devices (video cards, NICs, storage controllers). Download and run msd.exe and see how many KB each ROM occupies. If it's greater than 128KB (131,072 B), you're busted. You could try disabling the boot functionality of some of these devices, or disabling their BIOSes altogether.
 
You must log in or register to reply here.
Back
Top