Gigabyte X58A-UD3R with Raid 0 issues

Happyhammer7 · 29 Jan 2011 at 21:42

I thought I would make a thread on this in the hardware section as I believe my motherboard is faulty.

I opted to implement raid 0 on my system using the onboard intel ICH10R controller. Upon setting the BIOS to XHD Raid, I then configured the array using a 128kb data strip.

I loaded the latest raid drivers on a USB stick and installed these prior to the OS.

Once all installed, I booted into the OS, and started the driver installation. I then noticed that the system was "not responding constantly, and the resource manager showed excessive activity.

See below

Happyhammer7 · 29 Jan 2011 at 21:44

I also noticed that the size of the free space on the C: (main array), when installing any drivers/software. This would constantly change to different storage amounts. Although it looks full, it only has a few drivers installed and should have 1.7 TB of free storage.

I thought that one of the samsung F3 drives (used for the array) was faulty so I ran the full diagnostic tests and both drives are 100% functional. I have installed the OS on both drives and it works without error. I also ran memtest86+ to be on the safe side and that was also fine.

Over the past couple of weeks, I also noticed that I was losing connection to my wired mouse (power still be received) and also freezes before post.

Could this be a hardware fault with the SATA/RAID controller itself? Tempted to RMA the board but wanted to be sure before I did it, as I don't really want to be without a system for 2 weeks.

Thanks guys

mupet0000 · 30 Jan 2011 at 04:02

Wouldn't be surprised if it was the motherboard, I've got the V1 of the same board and it's riddled with strange bugs. Never tried raid on it myself though.

1Day · 30 Jan 2011 at 09:00

Please list the model and sizes of the hard drives you wanted to raid.

Happyhammer7 · 30 Jan 2011 at 13:16

1Day said:
Please list the model and sizes of the hard drives you wanted to raid.

Samsung F3 spinpoint 1TB x2.

I have restored it back to a single drive and although the "not responding" issues are mostly gone, the free space on drive c: changes dramatically when writing to the drive.

I have tried this across both individual F3 and I still have this issue.

1Day · 30 Jan 2011 at 14:27

Have you installed all the latest Intel chipset and drivers from the Giga site? Could you list those that you have installed. Will make it easier. It sounds like you have missing management driver.

Happyhammer7 · 30 Jan 2011 at 18:44

1Day said:
Have you installed all the latest Intel chipset and drivers from the Giga site? Could you list those that you have installed. Will make it easier. It sounds like you have missing management driver.

Thanks for your help. See your quite local to me, I am based in Crawley

I have installed the latest Intel RST driver 10.1.0.1008 when I implemented the raid. This was done at before install of the O/S. I then installed the drivers on Gigabyte CD, which included the INF & realtek drivers.

Thing is, the issues exist on raid 0 and on a single disk.

1Day · 30 Jan 2011 at 18:58

Horsham is just 10 min down the road.

You going to Manchester for the next round of the FA Cup? What a fixture eh mate?

I think you need to do the following.

Back up any important data on your primary hard drive.

Download the full compliment of drivers and utilities from the offical site.
Download the latest bios.
Make sure your hard drive can be used as OS in RAID 0 drive. I seem to recall there being some issues with the F3 due to the slow disc speed. The F3 is more a storage drive and not recommended as a OS drive.
Once you have done all that.

S t a r t a g a i n.

Yeah.
Flash the latest BIOS.
And start over.

Happyhammer7 · 30 Jan 2011 at 19:20

1Day said:
Horsham is just 10 min down the road.

You going to Manchester for the next round of the FA Cup? What a fixture eh mate?

I think you need to do the following.

Back up any important data on your primary hard drive.

Download the full compliment of drivers and utilities from the offical site.
Download the latest bios.
Make sure your hard drive can be used as OS in RAID 0 drive. I seem to recall there being some issues with the F3 due to the slow disc speed. The F3 is more a storage drive and not recommended as a OS drive.
Once you have done all that.

S t a r t a g a i n.

Yeah.
Flash the latest BIOS.
And start over.

Asked my Dad if he was up for it so if we can get tickets, definately. We are both Die Hard West Ham fans as we originally come from London, but it would be nice to have a break from them.

Just tried uninstalling some drivers and rebooted, and now I am getting no display on my monitor. This is going from bad to worse. Definately think there is a hardware fault somewhere but I just don't know how to find the root cause

Someone shoot me in the face

1Day · 30 Jan 2011 at 19:53

Right it defiantly needs a fresh install of your OS.

And while you are about it do the whole BIOS update thing too.

And I am not convinced it is hardware.

Happyhammer7 · 30 Jan 2011 at 21:54

1Day said:
Right it defiantly needs a fresh install of your OS.

And while you are about it do the whole BIOS update thing too.

And I am not convinced it is hardware.

Already flashed to the latest FE BIOS. Done a completely new fresh install and low and behold, the bugger is still doing the same thing. Tried it with no drivers installed and all drivers installed. I have literally tried everything and I honestly don't know what to do. This can't be anything other than a hardware issue surely.

I am fed up now and on the verger of stamping on it :mad:

Is there anything else I can do?

I have tried different cables, different hard drive configurations, disconnecting USB devices, fresh installs, bios flashes, different device drivers, rebuilding the PC, hardware utility tools etc etc.

Happyhammer7 · 30 Jan 2011 at 22:43

1Day said:
Right it defiantly needs a fresh install of your OS.

And while you are about it do the whole BIOS update thing too.

And I am not convinced it is hardware.

Already flashed to the latest FE BIOS. Done a completely new fresh install and low and behold, the bugger is still doing the same thing. Tried it with no drivers installed and all drivers installed. I have literally tried everything and I honestly don't know what to do. This can't be anything other than a hardware issue surely.

I am fed up now and on the verger of stamping on it :mad:

Is there anything else I can do?

I have tried different cables, different hard drive configurations, disconnecting USB devices, fresh installs, bios flashes, different device drivers, rebuilding the PC, hardware utility tools etc etc.