8TB internal not responding (mostly) ... how to t-shoot?

WiiGame

n00b
Joined
Mar 19, 2012
Messages
24
So, I did try to resolve this without help, but you'll see why this one is a [H]ard one to simply Google.
I'll try to make this short & sweet, but also informative enough to minimize unnecessary back & forth ...

Old(er) Desktop:
Just got a internal 8TB Seagate NAS (ST8000VN0002) with the latest firmware (SC61).

This drive is actually going to a mirror in a home Unix server with somewhat more modern parts, but that system so full I'd have to break an existing mirror prematurely just to test this 8TB in that box (and if "the new guy" here doesn't work completely inside, that mirror is at more risk). So I'd much rather test it in (around, attached to) this older desktop first.

However:
  1. This 8TB HDD came very poorly shipped (Newegg "Business"): absolutely nothing between the anti-static bag and the barely-together cardboard box on the bottom and sides (just some bubble wrap on top), inches to slide side-to-side, the HDD green board on the bottom, and the box bottom design depresses easily, opening holes where only packing tape stood between the anti-static bag and the elements of shippers and a Mid-Atlantic winter.

  2. I've only got some USB3 enclosures from some old 3TB drives -- trying the 8TB in one of those enclosures in both Older Desktop and the final destination via USB3 only yielded some rhythmic whining/buzzing sounds from the drive (so it's getting power) but no recognition from FreeBSD 10 or Windows 7 Enterprise (even nothing new under Disk Management so, no, this is not a typical "oh, just partition & format it" answer).

  3. Installed it into Older Desktop connected with a SATA2 P55 header and got the same rhythmic buzzing/whining at first (it does go away)

  4. I was just going to DOA RMA this and then I tried Seatools for Windows (1.2.0.10) b/c I'm pretty sure that's the first thing Seagate would try or have me do:
    1. This tool finds my 2x SSDs and my 2x WDC HDDs
    2. But it also finds something else: a completely unnamed and unidentified, under a USB--1394 header, even though there's nothing on that type of connector
    3. In fact, there's nothing else connected except an APC Battery Backup, an internal 3-port USB3 card, 3 optical drives and an internal photo-stick-media type of device (SD, MMC, etc.)
    4. Seatools literally only gives me "-------" as the SN, a pic like for the WDC drives (an open HDD), and Drive Status = "Ready"to Test"
    5. All Basic Tests come out positive for this phantom drive, which might/should(?) be the 8TB
    6. However, this drive just won't show up in Disk Management to allow progress
So the questions (that I can compose while falling asleep here) are:
Q1: Where do I begin to troubleshoot this? i.e., What could it be?
Q2: Did I already reveal something that prevents a (or this) 8TB NAS drive from working and I don't realize it (b/c I'm not all *that* experienced at this)?
Q3: How would one go from here to find out if the drive is really dead or if it can be brought up if only you had ____?
Q4: What would you do in this situation (besides upgrade all your [H]ardware)?

I considered BIOS: but Gigabyte hasn't updated anything relevant for this board since mid-2011 (but it does have a ACHI mode I'm now running in, and potentially a new ACHI driver).

I considered HDD firmware, but that seems to be up-to-date on-delivery (these 8TBs had a noise problem before that FW).

I considered that this drive just may not work at SATA2 or that this desktop mobo was never designed to address 8TB. (This is where we get out of my current depth.)

I considered calling the 8Tb "DOA," but it does power up, spin, and make a little noise which seemed to change/reduce when the successful testing started on the "phantom drive."

I'm considering that I might try to replace this via Newegg, if only for the poor packing, but I'd rather confirm the actual condition of the drive. And I don't want to have Seagate come back and say "it works for us" b/c I have some [H]W, FW, or driver deficiency.

I'd greatly appreciate any help to push me in the right direction to resolve my conundrum. Thanks!
 
Last edited:
So, no love for the baffled? Or are you all just as lacking of ideas as I am?

Or maybe you just prefer the TL;DR version where we go back & forth to help you help me? Should I just make it simpler and edit this down to 100 words and then we can go forward from there?

I guess I just figured this would be an easy one for someone vastly more experienced than me, whom I imagine is out here.
 
OK, great, thanks folks. I take from this that there are no obvious reasons a recent 8TB drive shouldn't work in this older setup. I just wanted to make sure this didn't repeat on the replacement and I'm back to square 1 but holding a working drive. Thanks again!
 
Just a note. If you have no way of troubleshooting it because of old ports/BIOS/motherboard then getting a new one wont solve your problem. Just be certain you really can use that size of drive on your setup via the Manual.
 
Which port on the motherboard did you try connecting the drive to? The picture seem to have 6 blue SATA 2 ports and 2 white SATA 3 ports (Marvell). One last ditch would be to try the Marvell ports?
 
Similar issue with same drive. Try unplugging your other drives and see if it spools up. I had to install an 800 watt power supply to get the juice to get it spinning. Wouldn't work in any of my external enclosures. Otherwise, it's been a good drive for the 6 months I've had it.
 
Just a note. If you have no way of troubleshooting it because of old ports/BIOS/motherboard then getting a new one wont solve your problem. Just be certain you really can use that size of drive on your setup via the Manual.
That's what I was actually looking for. So there *is* a possibility a mobo or SATA2 may not support this drive. But the only things I can find in this manual are # of ports and how to configure in mobo-based RAID, but nothing at all about TB limits or the like. So I'm at a loss as to where to find that info.

But this is kind of answering my core question of: Could it be because of the old h/w? Or is this h/w expected to work with SATA drives in nearly all circumstances?
 
Which port on the motherboard did you try connecting the drive to? The picture seem to have 6 blue SATA 2 ports and 2 white SATA 3 ports (Marvell). One last ditch would be to try the Marvell ports?

I have it on 1 of the 6 blue ones. Yes, I could try the ports the manual refers to as "GIGABYTE" but are apparently "Marvell"?

BTW, the most recent BIOS and driver updates for this board are 2010-11, so there's not much hope of those updates helping me.
 
Similar issue with same drive. Try unplugging your other drives and see if it spools up. I had to install an 800 watt power supply to get the juice to get it spinning. Wouldn't work in any of my external enclosures. Otherwise, it's been a good drive for the 6 months I've had it.

I certainly hope it's not that. I've got a 650W in the old desktop and a 750W in the Unix server.
 
I've been remiss in updating you all / future readers on what's happened with this.

does the bios see something on the attached hdd page?
I believe the answer to that one was "no."

But to expand, here's the answer I got back from Gigabyte (the mobo mfg):
"This drive has not been validated to work, please use 2TB or smaller on this board ... since this is a non UEFI based board it cannot support larger drives."
That's fine. Remember, it was just my test, not the final destination for this drive. And having thought about it, it turns out, while I had plenty of 3TB drives external on this box over time, I'd never tried to install one internally.

I kind of corroborated that UEFI/2TB limit with info from other places, but I also saw a trend that implies UEFI is only important if you want to boot from >2TB. So nothing 100% clear and definitive to me.

So then I bit the bullet and tried the drive on what will be the destination box anyway. This also didn't go so well. Same every-5-second humming upon power-up, which disappears after many minutes. These BIOS definitely didn't see it at first ... at least until it has been up for quite a while. Then I restarted (not powered off), THEN it would show in the BIOS, but then continue to not be recognized by the FreeBSD OS (and a post to FreeBSD returned that it "should" work with it).

I pressed on and tried to get it to work on my HTPC board, which is older than the destination board, but it still refers to UEFI somewhere. The drive was not recognized there either, but I never bothered with the overnight test here.

Upshot: I had plenty of evidence to RMA it, but I'm still worried, and trying to be hopeful, that when I get the replacement:
1) Newegg will have someone with common sense packing the replacement (esp. since I made a big deal at every turn/opportunity about their piss-poor shipping of the original)
2) It will ultimately be recognized immediately by the destination BIOS and by the Unix OS.

Thanks again, everyone! I'll try to return with any final updates (or questions if any new ones arise in this regard).
 
I've been remiss in updating you all / future readers on what's happened with this.


I believe the answer to that one was "no."

But to expand, here's the answer I got back from Gigabyte (the mobo mfg):
"This drive has not been validated to work, please use 2TB or smaller on this board ... since this is a non UEFI based board it cannot support larger drives."
That's fine. Remember, it was just my test, not the final destination for this drive. And having thought about it, it turns out, while I had plenty of 3TB drives external on this box over time, I'd never tried to install one internally.

Wuh? I've got 4TB drives in a Gigabyte p965 MB from 2007! I also have the same MB as yours in a more recent (though currently unused) build that had no problem with 4TB (though I believe you have to use GPart with drives over 2TB). I have no idea if it'd work with 5TB plus drives.
 

Attachments

  • hdd 3tb.jpg
    hdd 3tb.jpg
    63.4 KB · Views: 46
Wuh? I've got 4TB drives in a Gigabyte p965 MB from 2007! I also have the same MB as yours in a more recent (though currently unused) build that had no problem with 4TB (though I believe you have to use GPart with drives over 2TB). I have no idea if it'd work with 5TB plus drives.

Yes, I totally get the GPT requirement. But I was getting suspicious of the supposed non-booting HDD requirement when I can across other mobo's settings that only indicated it mattered if they were to be booted from.

Additional data, a WD 8TB works 100% well (so far) in the same target box the Seagate NAS failed in. So, it looks right now like the Seagate NAS HDD really was bad, though they don't receive the bad one until tomorrow, so haven't sent the replacement, so I cannot confirm yet. (No, I didn't bother trying the WD 8TB directly on the non-UEFI mobo I asked about, simply because it came in its own enclosure so I could Windows-based-test it externally.)
 
Yes, I totally get the GPT requirement. But I was getting suspicious of the supposed non-booting HDD requirement when I can across other mobo's settings that only indicated it mattered if they were to be booted from.

Additional data, a WD 8TB works 100% well (so far) in the same target box the Seagate NAS failed in. So, it looks right now like the Seagate NAS HDD really was bad, though they don't receive the bad one until tomorrow, so haven't sent the replacement, so I cannot confirm yet. (No, I didn't bother trying the WD 8TB directly on the non-UEFI mobo I asked about, simply because it came in its own enclosure so I could Windows-based-test it externally.)
Well that explains it, I guess. I've never tried to boot from one of these drives. They're all slow spinners, so not much point.
 
Back
Top