Recap of this thread:
- there is a compatibility mode for optical drives (IDE) if the controller is set to AHCI
- set it to RAID (if available) and use appropriate drivers
- BIOS modding on mobile devices is very risky and therefore not recommended
/vote for sticky or wiki
I set it to raid and tried to get the optical drive to work on two raid options.
1. using the embedded controller
2. set the bios to raid and use RST and i think i have tried every version of RST drivers that are compatible with my system.
from this site the classic drivers (original and modded) 11.2.0.1006 which best match to my Rom version , did not work no no matter what i tried. windows 7 8.1 and 10
the only thing that driving me crazy is when i set the bios to raid and use RST 11.2.0.1006 to build the raid-0. the kicked out the optical drive from the array but this is the only circumstance that banchmarking the optical drive SSD provides 550\550
this is unbelievable. why the bay drive gets kicked out from the array?
what happens in the raid building process that makes the SSD to work as it should(as a single drive after it get kicked from the array) because banchmarking the drive in any other way would give me a 100\100 banch,.
there is one fact here. the optical SSD drive does work as it should . the SATA 2 and the bay DVD caddy adapter dont interfere.
help please?
Which Intel RAID driver did you use instead?
Because the optical bay and the system drive are obviously using different sorts of Intel SATA Controllers. If you want to create a RAID0 array, both drives have to be connected to the same sort of SATA Controller. The fact, that the drive, which was connected to the optical bay, has been kicked out of the RAID0 array, has nothing to do with the version of the Intel RAID ROM module.
hi
the fact that the drive was kicked out of the array doesnt bother me. what does is why only after the drive was part of the array then after a system reboot the drive provides 550\500 benchmark.
so my question is, if the bay drive as you said is not connected to the same SATA port --a raid could not be created, OK, make sense but, to which SATA port the bay drive is connected to after
it gets kicked out from the array? fact is, after the bay drive is out of the raid i reboot the system and the bay drive provides an SSD full benchmark performance (500\550)
Being kicked off a RAID array does not mean, that the SATA port will be changed, where the drive is connected.
fact is, after the bay drive is out of the raid i reboot the system and the bay drive provides an SSD full benchmark performance (500\550)[/quote]That is a strange behaviour, which may have been cause by the special and absolute extraordinary SATA port configuration of your system.