Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: elliottlock on December 23, 2010, 12:13:21 pm
-
Hi,
Firstly here is my spec:
Motherboard: Gigabyte GA-X58A-UD5 Intel X58 (Socket 1366) DDR3 Motherboard
CPU: Intel Core i7 930 2.80GHz (Bloomfield) (Socket LGA1366) - OEM
SSD 1 (Boot drive): OCZ Vertex 2E 120GB 2.5" SATA-II Solid State Hard Drive (OCZSSD2-2VTXE120G)
HDD 1: Western Digital Caviar Black 500GB
HDD 2: Western Digital Caviar Black 500GB
DVD / BluRay: Samsung SH-B083L/BSBP 8x BluRay ROM / 16x DVD±RW Drive - Black (OEM)
I can currently only use my SSD on its own. The SSD is plugged into the ICH10R controller along with my Samsung SH-B083L/BSBP DVD.
When I plug in my two extra HDDs (Western Digital Caviar Black 500GB) into my Gigabyte controller (or any other controller in fact). The SSD is not found in the bios. It disappears. Because of this my system will not boot.
The ICH10R controller is set to AHCI and the Gigabyte controller is set to RAID/IDE.
I can't figure this problem out at all. Can anyone help me.
Many Thanks,
EL
-
Hi and welcome to the Gigabyte Forum.
Firstly are you runnning the two WD Blacks as a RAID array?
Are they SATA2 ?
Have you got the latest firmware on the SSD?
-
Yes I was running the WD Blacks in a Raid 1
The WD Blakcs are SATA II
The SSD has the 2nd latest firmware. From what I can see the latest firmware has only a very specific fix related to other manchines nad not mine. The fix is:
"Fixed rare corner case where sequential write with IOMETER 2006 could cause errors"
Cheers,
EL
-
Also here are the Known open issues with my SSD. I don't think these should affect my issue:
S.M.A.R.T. command B0 occasionally returns incorrect status
TRIM command response for short trims takes longer than test expects
Temperature reporting in S.M.A.R.T. data not correct (typically ½ actual value)
Slow format command in Windows using PMC-Sierra maxRAIDBR5225-80 RAID HBA
Compatibility issue with Intel 3100 chipset
Compatibility issue with NVIDIA MCP55 chipset under Red Hat Linux 5.4
-
Is the SSD drive still showing with the WDB drives connected to the controller but not the power?
-
Just tried this. That also causes the issue.
I plugged in both WD HDDs into the Gigabyte controller minus their power supplys and the SSD was no long detected.
-
In that case I would suggest that maybe one or both of the disks are faulty. Well you could change the data cables just to be sure.
-
K i've just tried another HDD (WD Raptor 740) and that works fine. Both the HDD and SSD are detected. But when I go to plug in the new WDs again I get nothing. This seems odd to me :/
I even tried a new cable. I can't believe both WD HDDs are broken. Also I can see the WD HDDs if I plug them in. They just stop me from seeing the SSD.
-
What happens if you plug them in as single drives instead of a RAID?
-
Yea same thing. I can't see the SSD. But I can see the HDD.
-
Do I take it that you have ported these drives over from another machine?
If so you will have to clean them and start agan.
-
Nope the drives are fresh and never have been used before. The used drive from an old machine I just tested is the ones that work.
-
Have you got another machine there then that you could try them in and see if the same thing happens?
-
Um maybe I could give it a go.
Here is something interesting though right.
I plug in a old HDD via the old power molex and that works k.
These new drives run on the new power cables so I thought I'll see if it could be related to the power.
I plugged one in. Only the power not the SATA cable and that stops it from working. Very odd!
My PSU is 850W so I can't see how it can't keep up :/
-
Does sound wrong doesn't it? If you have another PSU you could just jury rig it for now to try it out on another power supply.
-
I dont :(
I'm not to sure whats going on here I'm mega stumped.
-
Well it looks from what you have tested so far to be either the PSU or the drives. It is an unusual problem though.
Are you using the latest BIOS version?
-
Right i've just plugged in 3 old HDDs. These all work fine.
As soon as substitute one of those 3 HDDs for a new WD HDD though I get the issue. Its almost like the HDD is cutting the power is some way. So weird :/
-
As far as I am aware the power comes from the same rails for the drives whether supplied from the molex or SATA connections.
-
But im so baffled as to why adding 3 extra HDDs to my SDD would work but adding either of my new WD HDDs stops my SSD from being detected. Especialy considering the test i did was only plugging in the power cable not the SATA cables.
-
Well as I said earlier it must be either the drives or the PSU. Western Digital have allowed the quality of their drives to slip recently and there have been reports of numbers of drives being faulty not just singly.
-
WTF!
Okay get this. The 2 WD HDDs where in my PC case. At this time these drives did not work and the external ones that I hadn't mounted as I was just testing did work.
I've now switched these drives around as I thought the old drives where working and the new ones where not. AND GUESS WHAT!
The new ones not work outside the case and the old ones in the case no longer work! I ask you, WTF! LOL
Somehow the case much be messing up the drives but i have zero idea as to how.
-
It sounds to me like you have trouble with the internal wiring or there is a short somewhere. Very weird though.
-
OMG I found out what the issue was. I hope your as stunned as me!
The object causing the issue. Was the OCZ casing shipped with the OCZ drive. The casing looks as if its so close to the drive it was causing it to in some way short out. I've changed the casing for a Akasa one and now all works fine. Next stop OCZ for some major complaining. Its taking me 4 months to figure out this issue! LOL
-
Never mind we got there in the end and it makes a nice Christmas present for you now. I said it sounded like a short so fairly close really.
Happy holidays.
-
Arr f*** ok that wasnt the issue. f***! lol something is definitely shorting it but its not that.
-
Ah! So broke out the bubbly to early eh? Keep looking.