"Martin Racette" said:
I want to add another drive to the second controlor, and the BIOS
setting all I have is enable or disable for the second controler
I still don't know if I understand your question. Yes, the Nvidia
interface has some direct control in the BIOS. Remember that the
Nvidia ports are part of the "chipset", and chipset interfaces
get a "place of honor" in the main part of the BIOS.
Add-in controllers, are separate chips. Each chip which is added
to a motherboard, but is not part of the chipset, may have a
body of code called the "Option ROM". This is added to the BIOS
flash file, but is, in a sense, a separate piece of code. In
your case, pressing F4 in the BIOS, gains access to the interface
provided by the Option ROM code.
That being said:
1) In Onboard Devices, set "Silicon SATA Controller" [Enabled]
It is set that way by default. Do a Save and Exit, to save
the new setting. I think that is necessary to get the
controller to appear on the PCI bus. If disabled, you might
not be able to see the chip when using Everest Home Edition
(lavalys.com).
2a) The next time you start the BIOS, press <control-S> or
press F4. The Silicon Image RAID BIOS screen should
appear. See section 5.5.3 in the A8N-SLI Deluxe manual,
for instructions on what to do next. Note - Use this
interface, if you wish to set up a RAID array, or if
you want to do JBOD.
2b) If you want to use the disks separately, as IDE devices
but not as RAID, don't bother entering the RAID BIOS. The
consequences of doing this, AFAIK, is you cannot boot from
that disk, but still use it for data.
3) Install a driver. Now, there are drivers that claim to be
IDE and drivers that claim to be RAID. My suspicion is,
on your Asus board, you use the RAID driver for both
RAID or vanilla IDE use, as the IDE version might not
even install. There is no separate IDE driver for 3114 on
this page (click Driver at top):
http://support.asus.com/download/do...product=1&f_name=&type=Latest&SLanguage=en-us
The large download size of the drivers on the Asus Support
page, likely includes RAID Management software. In fact, the
bare disk driver files, are tiny in size.
If you go here (Silicon Image support)
http://www.siliconimage.com/support/supportsearchresults.aspx?pid=28&cid=3&ctid=2&osid=4&
and select the 1.2.3.1 RAID entry at the bottom, you get a
tiny file.
If you then examine Si3114r5.inf in that download, you can
see entries like PCI\VEN_1095&DEV_3114&SUBSYS_81361043 .
The 1043 is the Subsystem ID for Asus. I don't know how to
decode the 8136 part - it could be per-motherboard or generic.
In any case, the IDE download from the siliconimage.com site
doesn't have a "1043" subsystem entry, so it should not even
install on the Asus board (going to Device Manager and trying
to update the driver with the IDE version, should in my
estimation, fail).
Anyway, I hope some of the above helps. I cannot figure out
exactly what you want to do, but enabling the controller and
installing a RAID driver, should solve most of your problem.
You could press F4 key, when the BIOS starts, and set up a
stripe (RAID 0) of two disks, or you can set up JBOD if you
want to span two disks and make it look like one disk. Both
options will give you 800GB of storage.
Personally, I would run the disks as separate entities, as
data recovery in the future might be easier (i.e. if you have
no backups and like to live dangerously, without a backup).
To operate the disks separately, install the driver, and then
enter Disk Management in Windows and finish the installation
process. I would hope to see two separate disks in that case.
Page 18 through 38 of this Foxconn manual, gives some info
on SIL3114. It says, if you want to run a disk separately
and boot from that disk, specify JBOD. If you want to use
a disk separately as a data only disk, then don't use the
RAID menu to set up the disk. That is my interpretation of
reading this manual (the contents of this manual should
also be in the Manuals folder on your motherboard CD):
http://www.foxconnchannel.com/pdf/925XE7AA-raid manual-EN-V1.0.pdf
The only downside of using JBOD, might be that Windows
prepares the disk as a Dynamic Disk. You should do further
research to see if there are any disadvantages to using
Dynamic Disk. I don't remember all the reasons Dynamic is
bad, but if I find one of my drives is Dynamic in
Disk Management, I strive to return it to Basic if I can.
Just some guesses,
Paul