Official GIGABYTE Forum

Should I RMA my GA-X58A-UD5?

Joe.da.Shmoe

  • 7
  • 0
  • My first PC was an XT
Should I RMA my GA-X58A-UD5?
« on: August 13, 2011, 06:06:44 pm »
Hello All,

I build a new config as below.

GA-X58A-UD5 Rev 2.0 - BIOS Ff1
I7 960 with Noctua NH-U12P SE2
G.Skill Extreme3 3 x 2 Go PC16000 Trident
ATI Saphire 6900 2GB
2X Sony - AD-7260S-0B DVD SATA drives
Cooler Master Silent Pro Gold 700 W
Gigabyte Gigabyte iSolo 230 case
HDD WD3000HLFS SATA 2 Raptor  (Since moved to another PC)
HDD WD4500HLHX SATA 3 Raptor
HDD WD1002FAEX SATA 3 Cavier Black
2X HDD Seagate SATA 2 ST31000528AS
HP LP2475W Monitor
Windows 7 Professional N x64

French Gigabyte Tech support (I’m an expat) wrote that I should RMA my Motherboard, I think they’ve got it wrong.  I think I should wait for an improved set of drivers for the Marvel controller and wait for BIOS improvements.

Here’s the problem.
I installed Win7 x64 on the WD3000HLFS SATA 2 Raptor 300GB Drive (IDE mode in the Bios) on the GSATA3_6 Position.  It Worked.  Same is true for the AHCI mode.  Same is true for other SATA plug positions on the Motherboard.  It works.

The above is applicable for the WD1002FAEX SATA 3 Cavier Black also.

The above does not work for the WD4500HLHX SATA 3 Raptor.  It is not a disk problem, as I am using it now as my C: drive but on GSATA3_7 and the 1000GB Caviar Black is on Position GSATA3_6.  The WD4500HLHX SATA 3 Raptor works on all positions except the GSATA3_6.  All other disks work as the systems C: Drive on the GSATA3_6 position, in both IDE and AHCI modes).

Providing the marvel drivers during the install of windows doesn’t change anything.  The install just hangs at the copy files stage, or various other install points.

As it is today, the build is fairly stable…  hasn’t just frozen up needing a reset to get going again for a few days.

I still have the startup problem described in this post titled “Post restarts/corruption" even after following the fix instructions.

So … Should I RMA the motherboard or wait for Gigabyte or Marvel to provide better drivers.  Or just give up on the Marvel all together for a while?

Sorry folks.. I don't get it..   I think the tech support did not/could not read the problem in English correctly and just blew me off to the RMA route.

As I wrote... the system is running and stable.  but disk "A" will not work on Marvel Sata6 position "0"..   This looks much more like an incompatibility between one particular HDD and the GSATA3_6 position.  all other disks work, and the disk in question works on all other sata plug positions..

Why RMA just to RMA... if the problem is Marvel hardware in the end, for which there is no solution?  (honestly.. taking this all apart again putting it back in the boxes and waiting 4 weeks for the same problem after losing weeks building it.. does not seem like much fun.)

please tell me why I only have the problem with 1 disk on one plug, knowing that that same disk works fine on all other plugs.. .. and that all other disks work fine on all plugs including the plug where the first disk does not work?

The French tech team just did not want to be bothered with the issue or problem.. they blew me off and took the easy road... RMA.

Whereas everything in the forum points to erratic problems with the Marvel SATA3 chip that no drivers or firmware will/can solve.  (maybe in the future something will be developed or we will go the sandy bridge route)

So I'm just going to take this all apart box it up and do with out a PC for a month, because tech support is at 50% of staff because they basically close down for the summer over here in France and can't be bothered.

let down because the industry was duped by Marvel, let down because the machine will not/never work as designed, let down because quality control is being done by the end user, let down because tech support couldn't give a hoot!  I'm having a great time ..  Smiley



Dark Mantis

  • *
  • 18405
  • 414
  • 10typesofpeopleoneswhoknow binaryandoneswhodont
    • Dark Mantis
Re: Should I RMA my GA-X58A-UD5?
« Reply #1 on: August 14, 2011, 08:53:28 am »
You are getting the problem because you have the Velociraptor connected to the Marvell port and this won't support fast drives. That is why your other drives will work fine on it but not the Velo. The Marvell ports are just crap on these boards!
« Last Edit: August 14, 2011, 08:54:03 am by Dark Mantis »
Gigabyte X58A-UD7
i7 920
Dominators 1600 x6 12GB
6970 2GB
HX850
256GB SSD, Sam 1TB, WDB320GB
Blu-Ray
HAF 932

Gigabyte Z68X-UD5-B3
i7 3770K
Vengeance 1600 16GB
6950 2GB
HCP1200W
Revo Drive x2, 1.5TB WDB RAID0
16x DLRW
StrikeX S7
Full water cooling
3 x 27" Iiy