Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[relax_nl]

Mine stopped working after 7 months! Part of a 5 HDDs RAID6 volume in a Synology DS1511+.

Symptoms exactly as others describe them. No hints of any problem whatsoever, suddenly the drive just died off and isn't talking to the controller.

ST2000DL003

P/N: 9VT166-301

F/W: CC32

DATE: 12082

SITE: SU

Bought in the Netherlands.

[VeganFanatic]

The ST2000DL003 and other green series disks are not suited for RAID.

Better to use the corporate enterprise disks which are designed for the purpose.

[relax_nl]

This model is present in the compatibility list of Synology with no remark!!!

http://www.synology.com/support/hd.php?lang=us&bays_id=4&product_id=67#3.5 SATA Hard Drives

Another user has reported them to work fine:

http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/ST2000DL003-fails-in-raid-array/m-p/90...

---

zasy99 wrote:

I have 5 of these drives in a Synology NAS, they work fine for me.

My NAS has a power saving feature that powers down the drives after 20mins of inactivity ( I can enable or disable this feature, I have it on as I don't need the drives to spin all night when I am sleeping).

When they are inactive and I access the NAS it takes approx. 10 seconds for them to spinup and the NAS can then react to file or folder access requests.

These are 'green' drives and green drives are generally never certified for RAID useage because they have many power saving features that make them 'slower' to react than desktop or enterprise (RAID) drives.

Depending on your RAID controller card the card may think a drive is no longer functioning because it is taking too long to react to a command whereby in reality the drive is just coming out of power saving mode.  Users have reported these issues on several forums, not only with Seagate drives but also other manufacturers.  Unfortunately the users do not get much help from the manufacturer because they bought the 'wrong' drive for the job.

That being said, Seagate does state the drive for use in:

• Direct Attached Storage devices–USB/FireWire/eSATA
• Network Attached Storage devices and Windows storage servers
• Eco friendly PCs
• High-capacity desktop storage

Do you have some kind of power saving configuration in your NAS, if so you you may want to try disabling it and see if that helps.  That should prevent your drives from idling and hopefully prevent timeout issues and your RAID card from thinking the drive has dropped out of the array when in reality it was just in standby so to speak.

---

And moreover

The implementation of RAID on the DiskStations is done in software (mdadm), there is no hardware RAID. As far as I am aware the CPUs used in a majority of Synology NASes will have hardware assisted RAID. Meaning that the CPU's have instruction sets specifically for RAID calculations.

The advantages of software RAID is the ability to add new RAID algorithms or RAID levels. The advantage of hardware RAID is the ability to fully off load any RAID calculations to a dedicated processor and not take up CPU time.

Considering the flexibility of using a software based RAID, I think the performance penalty is worth it.

[zarillo]

Hi,

well i add my disk to the thread:

ST2000DL003

CC32

Date: 11285

Today i power up and its all good. I power down...drink some coffee...power up...drive is gone. Win7 takes ages to load and then no HDD anymore (of course my system is on a differnet SSD, otherwise Win7 wouldnt load anyway..)

Bios : No HDD...takes ages to get into bios.

I have around 900 GB on that disk. Mostly movies and stuff that i can replace..but also the few docs that my wife saved in the last years. Sooo...its kind of a matter to live or get killed by her if i have to tell her that his is all gone (of course i never did a backup of that stuff...). Thats when i read about this guy who was able to get his hdd back in action after shortening the pins on the back of the HDD. 

Beeing no computer profi i just wanted to ask you guys if i understand everything correct before i try his method ( i mean it cant get worse if it fails anyway ;-) ) .

 Step by Step:

1): I removed the HDD from my PC (looks good..silver...however, still dead)

2) I organised a old wire (a isolated electric cable, dont know how the real name of that thing is)  to shorten the contacts that i can see marked in blue in the picture psoted on page 23 in this thread.

3) What now?

My Plan is to either a ) plug in my SATA PC power cable again and the SATA data cable (just as i had it before it crashed or b) add a SATA to USB connector so i can connect it as a external usb drive later.

Lets say i go with b)

1. Connector connected with HDD but not PC

2. SATA Power plug connected (the drive has power from my PC)

3. Turn on PC

4. Drive spins up...pc boots (of course the  HDD is not found) to win7

5. I shorten the pins (and hope that it wont explode) for a minute

6. I connect the usb with the PC (still shortening the drive??)

7. I see the drive?

Do i need this terminal thing? I just want to copy the few word docs and then send it to heck (= RMA).

Any help is appreciated!!

Thanks!

[Lahcen]

My first drive shows the below log and the dialog stops on [SR] 0003. when i send ctrl-z at the beginning i cna have the F3 T> prompt my first question is how to get ride of this issue [SR] 0003 ................................................................... MCMainPOR: Start: Check MCMT Version: Current MCMainPOR: Non-Init Case MC Seg Disc and Cache Nodes: 4011A58C 4011869C Seg Write Preamble VBM start: 000010A7 end: 000010CE Footer - start: 000010D0 end: 000010F7 Seg Read Preamble VBM - start: 000010F9 end: 00001120 Footer - start: 00001122 end: 00001149 Reconstruction: MCMT Reconstruction Start Max number of MC segments 22E0 Nonvolatile MCMT sequence number 00007724 [RSRS] 1658 Reconstruction: Completed 1: Reconstruction occurred [MCMTWS] MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00005141 MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A MCMainPOR: MCStateFlags = 00005141 MCMainPOR: Feature Enabled... [SR] 0003 [SR] 0003 [SR] 0003 [SR] 0003 ..................................................................... for the second drive regarding some forum, my drive has the lba 0 issue (0mb) I need to send m0,2,2,0,0,0,0,22 command my question: can m0,2,2,0,0,0,0,22 command lose data or damage my drive. Please help, I am very upset about my collected data since long time.

[pich39]

Hello to everyone. My almost brand new HDD has stopped being detected by BIOS suddenly too after only 3 months of normal working and without any signs of disk damage: sounds of spinning ok, but red light of disk activity keeps lighted and the message "Disk boot failure" appears, because there is no detection in BIOS. Formerly I managed to mend a HDD 7200.11 with the firmware solution from SEAGATE, but for this case it´s impossible the firmware approach for the hdd remains undetected (or am I wrong?). I have lost all 3 months of work, documents, projects, family photos, etc, so I pray SEAGATE or any guru of this forum to post the step by step solution for as far as I can get from previous posts, it can be solved by shorting some pins of the printed circuit board (PCB). There´s no point in interchanging PCB´s for the problem is not there (I´ve checked that myself with a PCB from another older hdd ST2000DL003 2TB with matching Part Number and matching number of the PCB: 100617465 REV B). As for which pins to short, I have a PCB 100617465 REV B, and in the posts the pic shown is for PCB 100617465 REV A, which is similar as far as I can see to REV B, are the pins to short shown for REV A PCB valid for REV B PCB too?. How do I enter hyperterminal if I can´t access the disk nor Windows? From another HDD and an external USB or from some live CD? Well, I hope SEAGATE support admit it´s a common failure with 7200.12 Green Barracuda disks and don´t let us in the ditch when we are so many and for years faithful clients. Please reply with full detail and with the pics of the procedure (manual for dumbs) -even of how the pin-shorting- if you´ve been successful in recovering the hdd for use or at least to clone it and retrieving the valuable data. Thanks so much in advance.

[pich39]

Just to stir the post:

As 267 messages are not enough for anyone at SEAGATE to care for this post, at least to say they are working on the solution if that is the case, I just put my disc specs again:

ST2000DL003 Barracuda Green 2 TB

Part Number: 9VT166-301

Firmware: CC32

Date: 11455

I think it would be much cheaper for SEAGATE to develop a fix for this than the discredit of not even attempting to solve it. The damage is already done, but at least a firmware fix for the hdd´s that are still alive (the one I´m posting from, for instance) and a solution (I´m sure there will be one) to retrieve the data for the ones that have bricked (although it requires buying some cables to do the hyperterminal thing) will help mend the situation, and make us trust again in the company.

Have a good day and post solutions.

[AskTheLeaf]

It would be best to establish live contact with our technical support to get this issue resolved:

http://www.seagate.com/support/contact-support/

[pich39]

Just to let you know, I´ve found this recent page (posted ending July-2012) http://blog.pcbfordatarecovery.com/?p=8 where the tech guy there talks of the issue relative to the ST2000DL003 being inaccessible to hyperterminal commands (perhaps he had to have shorted the pins and didn´t??), although there´s a dim scope for hope for he makes a final statement in the sense that SEAGATE Manufacture Engineers would "reveal" a solution at the end of August 2012, so by now if any of you engineers have a hint on that, it would be nice of you to share it publicly here the sooner the better. Also, from reading the post of Yannick on page 25, he seems to have succeeded in accessing the hdd, so please do post the procedure you followed in detail. As for the live contact with SEAGATE tech support, I wonder if any of you, AskTheLeaf and the rest of the SEAGATE guys, already have this longed-for working solution, because there is no point in sending the hdd to the headquarters otherwise without knowing if data is due to come back or be lost for good by some possible human error in the manipulation, and besides I imagine you must have a lot of bricked ST2000DL003 by now to experiment with. Please answer with what you know for sure and thanx for your interest and time.

[TowerPower]

Just to add my drives to the list...

I have two Seagate Baracuda Green 2000GB drives that died after about a year of using it without warning after a reboot. Drive data is: ST2000DL003 P/N: 9VT166-301 F/W: CC32 Date: 11453

One is now still recognized by Bios and Windows XP, but does not show. In device manager this appears without any partition and a yellow exclamation mark. The other one is not even recognized by BIOS.

I need the data at least from the "healthier" drive. Is there a solution now as mentioned in the previous post?

I cannot believe that Seagate leaves us with shortening drives...