mako
New Member
Posts: 2
|
Post by mako on Jun 15, 2008 6:16:33 GMT 7
I just rebuilt my PC complete with new motherboard and in the process also changed the config on my Thecus 2050 from a mirror to a stripped RAID config. I needed more usable space.
For whatever reason, I am not able to see the connected Thecus volume even though the BIOS sees the 1GB volume. This is hanging off a secondary onboard controller on my Asus Striker II Extreme NSE. The controller sees it in the POST (which I have configred as a AHCI since the Thecus handles the RAID config itself).
The Thecus would also have its lights flash across the front panel from left to right a few times during boot causing Vista to take about 10 minutes to boot (normally about 45 seconds).
Has anyone come across this issue or have any ideas?
Thanks
|
|
|
Post by chaser on Jun 19, 2008 15:27:59 GMT 7
Are you using the onboard eSata controller? If so, I looked up your motherboard specs, it looks like you have a Jmicron eSata chipset.
Thecus recommends using eSata boards with a Silicon Image chipset, otherwise you might encounter incompatibility issues.
|
|
mako
New Member
Posts: 2
|
Post by mako on Jun 21, 2008 8:02:27 GMT 7
Thanks for the reply.
Yes, I currently have a jmicron chipset. I just upgraded my PC from an older motherboard which did have a Silicon Image controller. I guess I can use the card that came with it and use that and disable the jmicron. Thanks again for the sanity check. I had not seen where they recommend certain chipsets over others.
|
|
|
Post by chaser on Jun 22, 2008 6:04:17 GMT 7
Glad to be of help ;D
|
|