Sign in with
Sign up | Sign in
Your question

My Gigabyte motherboard won't recognise HD > 2TB

Last response: in Windows 7
Share
February 12, 2010 10:45:21 AM

Hi

I have a gigabyte EX58-UD4P motherboard for the Intel i7 on my Win 7 64 bit PS, and I am trying to connect an eSata drive to it which is bigger than 2TB.

When I boot up, the BIOS finds the external hard drive correctly, but the next part in booting comes up with a 0.0GB for that drive. From that point on the operating system does not find the drive at all.

I did experiments with different size external eSata drives and found that 2TB worked correctly, but anything larger (eg, 4TB and 8TB), came up as 0.0GB during boot and would not work.

Any ideas?

The BIOS version of the motherboard is F8.

Your help would be greatly appreciated.
a c 302 V Motherboard
a b $ Windows 7
February 12, 2010 1:33:56 PM

Hi newcomer and welcome to the Tom's hardware forum.

Can you see the HDD in your PC?, Can you see the HDD in the disk manager?
m
0
l
February 12, 2010 10:05:50 PM

No, Win 7 does not see it in Disk Manager at all.

Any ideas why the BIOS sees it as 0.0GB?
m
0
l
Related resources
a c 302 V Motherboard
a b $ Windows 7
February 13, 2010 4:27:59 AM

Well 'till I know, windows have problems managment with HDD >2TB, this could be the source of your problem.

Download and use Hiren's boot utilities, and use the partition tools to see if this can recognize your HDD, if the software can recognize your HDD, create some partitions and reboot your PC.
m
0
l
February 13, 2010 5:43:35 AM

Hi Saint19,

No the partition tools cannot see the hard drive. I think the Gigabyte BIOS is hiding it since it thinks it is 0.0GB.

Has anyone else had this problem?
m
0
l
a c 302 V Motherboard
a b $ Windows 7
February 13, 2010 11:18:06 PM

^Well, like you says, could be problem of the mobo. Do you try with the gigabyte's support?
m
0
l
a b V Motherboard
a c 215 $ Windows 7
February 14, 2010 7:03:55 AM

Is this a single disk? or have you connected a bunch of drives in a raid array over this esata port?
m
0
l
a b V Motherboard
a b $ Windows 7
February 14, 2010 7:14:18 AM

I don't think there are any single SATA disks larger than 2 TB, are there? Certainly none as large as 8 TB. So it must be some sort of array, which might well explain the issue.
m
0
l
a b V Motherboard
a c 215 $ Windows 7
February 14, 2010 7:24:04 AM

There are currently no single hard drives available to consumers larger than 2TB that I am aware of, however your comment did make me think of something ijack.

If the BIOS is telling the SATA controller to run in either legacy, or AHCI mode, then hooking up a RAID'ed array of drives to a single port would likely cause the BIOS to identify the drives (and thus their total combined capacity) incorrectly.
m
0
l
February 14, 2010 10:39:45 AM

Hi,

Just to clarify... I have a Drobo S which is effectively a case with hard drives in it. Drobo says that it should appear as a single external hard disk and I can format it to apprear as 2, 4, 8, or 16TB.

My BIOS setting is set to RAID (Intel SATA connections) as I have two internal WD EARS 1.5TB hard disks set up as a Striped array. On the other ports (there are 6 of them) I have a singel 1Tb hard disk (os), and two DVD ROMS.

I have also two Sata Gigabyte connections on the motherboard and I have set these to AHCI so I can plug and play my external esata hard disks. It works well.

My aim is to ALWAYS have my Drobo connected to the Intel sata port so it is found during boot up (POST?). Since this doesn't work as I described above, I have connected it to the Gigabyte AHCI port, but at bootup this is hit and miss. Sometimes it connects correctly and sometimes it says that there is an error with the external hard drive (Drobo). I think this is because the Drobo doesn't wake up in time and the Gigabyte port times out.

Therefore to summarise... I am really aiming to connect my Drobo to the Intel Sata port - but it won't recognise anything larger than 2.0TB. Any way to fix this?
m
0
l
a b V Motherboard
a b $ Windows 7
February 14, 2010 11:09:44 AM

As Data Robotics specifically say that you eSATA card must be set to non-raid mode, that might be the explanations of your problem.

Edit: Studying the documentation further, I see that it states that, if initially formatted as a 2 TB drive, Drobo will only every present 2TB volumes to the hardware as you add capacity. If your capacity exceeds 2 TB it will present it as multiple volumes. To see multiple volumes you need an eSata card that supports port multiplier function. Are you sure that your eSata connection meets this requirement (and that you are using a connector that supports port multiplier)? Or are you formatting to the largest size from scratch?

Edit again: (I keep looking!) This item from the Drobo Knowledge Base may be relevant.
m
0
l
February 14, 2010 12:04:44 PM

Thanks ijack:

(1) I realise Data Robotics says to set the eSata card to non-raid mode. As I see it, the port the Drobo is connected to is not set to RAID. The intel RAID controller is set for this port not to be RAID. But I may be mistaken.

(2) Yes this is correct if you set up the Drobo as a 2TB drive. With the Drobo you can keep adding drives and so if you exceed the original 2TB volume it will create another one. Therefore in this case you would need a port multiplier.

My aim is to have one 16TB drive (although I only have populated 3TB at the moment).

(3) Yes this is a good link. I was exctited when I saw it last week as it explained my problem perfectly. Alas I already have Microsoft drivers so this KB item doesn't apply to me. I suggest that the motherboard BIOS needs to recognise the drive as non 0.0GB before the operating system will see it.

I have put in a request to Gigabyte support asking whether the motherboard BIOS can recognise drives > 2.0TB as per my configurations. It's the Chinese new year so I don't expect to hear from them until the end of this month.

Keep looking... as I like the way you think.
m
0
l
February 25, 2010 3:51:09 AM

Anyone else have ideas?? I haven't heard back from Gigabyte as yet.
m
0
l
a b V Motherboard
a c 215 $ Windows 7
February 25, 2010 5:08:01 AM

If the SATA controller internally is set to Legacy or AHCI (i.e. non-RAID) mode, the controller will need to support port multiplication (which a lot of controllers out there right now do not) in order to see multiple hard drives connected via the eSATA interface though a single cable.

For example, I bought a Vantec Nexstar dual hard drive dock (seen here: http://www.ncix.com/products/?sku=36051&vpn=NST-D200SU&...). If I populate both hard drive slots with drives and connect it to my desktop or my laptop via eSATA, I cannot see the hard drive connected to the rear slot because the Intel SATA controller on my Gigabyte GA-EX58-UD5 motherboard does not support port multiplication, nor does my Asus G51J laptop. If it then switch cables on the dock from eSATA to USB and hook it up to both my laptop and my desktop, both hard drives are detected and function properly. I bet if you hooked that Drobo up to your computer over USB, every drive would be detected perfectly.
m
0
l
!