Seagate 1TB ST31000340AS anyone?

Browser

Expert Member
Joined
Aug 9, 2007
Messages
1,018
Reaction score
26
Does anyone have a Seagate 1TB ST31000340AS? I've been thinking of getting one but have been reading about quite a few people having problems with them.

Anyone having any problems with one of these?
 
Last edited:
Does anyone have a Seagate 1TB ST31000340AS? I've been thinking of getting one but have been reading about quite a few people having problems with them.

Anyone having any problems with one of these?

Got 2 Seagate Freeagent drives 750G and 500G, work fine.
 
Lawsuit for Seagate

I wish I read this thread before buying a ST31000340AS 1TB Barracudda.

Bought it in February 2009 and it failed 25th July 2010.

I am not impressed with Seagate and would like to know if anyone is or is oi the process of suing them because it seems I will go that route and it would make sense to join forces.

Please reply to this post so that we can get into contact with each other.
 
The ST31000340AS is part of the 7200.11 generation. I would advise not to take one unless you are confident enough to update the firmware (if the drive has SD01 to SD17. The CCxx firmwares apparently don't have the same issues). The ST31000340AS is replaced by ST31000528AS, which is a 7200.12 generation drive, which seems a lot more reliable.

Unfortunately for Seagate, after years of good drives, they had a bad generation of drives, much like the fujitsu MPG drives of many years ago. How both companies handled the situation was not really in the best interest of the consumer and caused a bad reputation. In the same breath, however, I have heard some bad reports about other manufacturers' drives having high failure rates in recent periods.
 
in my expereince seagate has the most unreliable externals, iv had two die on me in infancy and another one lasted about two years before it decided to break...... stay far away
 
I can say the same about Samsung 1TB drives (infantile death): A friend went through 3 of them, days/weeks apart. However, I have the same drives in external bays, running 24/7 without issues.
Same goes for the specific Seagate drive this topic is about: I have an array system (12 drives) running the specific drive without too many headaches (made sure firmware was corrected), yet some customers have lost entire RAID systems due to the drives (BSY / 0GB errors).

One thing all manufacturers are certain about, is that something will break at some stage (MTBF). Unfortunately, some people just have bad luck and get all the duds in a go, while others are blissfully unaware for the longest time. A few years ago, Google (ye who have uber QTY hdd) wrote a paper about harddrives and their longevity. The crux is hdd's will generally last for a long time (a few years) or for a very short period (first few months) before behaving badly.

Is one brand/model better than the other? Only to a certain extent. Quality (read: design & production flaws) varies greatly between generations, factories and firmwares. Unless you research a lot, it's pretty much like being a kid sticking money into a candy machine and hoping for something nice.
 
Last edited:
I wish I read this thread before buying a ST31000340AS 1TB Barracudda.

Bought it in February 2009 and it failed 25th July 2010.

I am not impressed with Seagate and would like to know if anyone is or is oi the process of suing them because it seems I will go that route and it would make sense to join forces.

Please reply to this post so that we can get into contact with each other.

You want to sue because ur HDD failed? I take it you don't believe in backups and u lost something. Hope it wasn't critical data, and that you recover what was lost. Never nice loosing data.

Not sure about ur particular model, but i've got 3 Seagate 1TB drives in a RAID5 array, and they've been fine for the last 2 years. No problems yet, with some pretty heavy load.
 
@shogun:
check the generation and firmware. Problem was the drives returning BSY, particularly in RAID config as the drives would lock (BSY) when the machine is rebooted, I.E the drive would disappear, and the issue was usually a function of time. Often more than 1 drive would lock.... byebye RAID.
 
@shogun:
check the generation and firmware. Problem was the drives returning BSY, particularly in RAID config as the drives would lock (BSY) when the machine is rebooted, I.E the drive would disappear, and the issue was usually a function of time. Often more than 1 drive would lock.... byebye RAID.

Good thing I backup the RAID array as well then:P

How do you check the generation and firmware? Device Manager giving me info for the RAID array only, not the individual drives.
 
@shogun : Use the RAID utility inside the OS. Should get the HDD model number (ST3xxxxyS) and maybe the firmware. Reference the model number on Google/Seagate and check if you've got a 7200.11 / ES2.
While you're at it, check if your RAID utility has an email reporting feature and configure it. So often this is ignored, but has saved my bacon a few times (give me the opportunity to schedule downtime instead of having a toasted array during business hours and many many upset users).

@UnUnOctium: Probably would agree with you there. Haven't heard too many sob stories regarding them, but don't have many sources either to be statistical for me. That said, things change quickly in the IT hardware industry, and world + dog is left with the aftermath.
 
Last edited:
I'm giving Samsung a go - no problems so far. Also have 2 seven year old Maxtor drives (some of the first sata drives) that still work. Also have a three year old Seagate which is also still fine. I guess its just unlucky if you get a bad drive.
 
Top
Sign up to the MyBroadband newsletter
X