Seagate ST3000DM001-9YN166: A catastrophic disk

Written by - 4 comments

Published on - Listed in Hardware Linux Rant


In the past few months I've had a lot of failing hard drives to compensate... While I was writing a summary of all disk replace actions, I got aware that it's always the same model failing: ST3000DM001-9YN166.

November 3rd, 2012 - runtime 4391 hours (182 days + 23 hours):

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-9YN166
Serial Number:    XXXXXXXX
Firmware Version: CC4C
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sat Nov  3 11:51:24 2012 CET

February 28th, 2013 - runtime 2728 hours (113 days + 16 hours):

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-9YN166
Serial Number:    XXXXXXXX
Firmware Version: CC4B
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Thu Feb 28 01:20:07 2013 CET

May 27th, 2013 - runtime 2593 hours (108 days + 1 hours):

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-9YN166
Serial Number:    XXXXXXXX
Firmware Version: CC4H
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon May 27 11:59:17 2013 CEST

June 11th, 2013 - runtime 10528 hours (438 days + 16 hours):

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-9YN166
Serial Number:    XXXXXXXX
Firmware Version: CC4C
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Tue Jun 11 14:12:53 2013 CEST

So I'd say hands off this disk...

Update September 9th 2013: And another one failed yesterday after a runtime of ~13148 hours (547 days), which is actually not that bad:

=== START OF INFORMATION SECTION ===
Device Model:     ST3000DM001-9YN166
Serial Number:    XXXXXXXX
Firmware Version: CC4C
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Sep  9 11:57:55 2013 CEST


Add a comment

Show form to leave a comment

Comments (newest first)

Chad from Boston, USA wrote on Jan 9th, 2015:

Add another two on this list.
I have 6 HDDs, all Seagate, running in two NAS devices.
I purchased two ST3000DM001-9YN166 drives in August 2012. One died in June, 2014 - About 11,000 hours. I was sent a replacement in July under the warranty, another ST3000DM001-9YN166. After 6 months it too has died. The other drive has 17,000 hours and 1,584 bad sectors.
In comparison, I have a pair of ST32000641AS drives with 28,000 hours and no bad sectors. I'd avoid the ST3000DM001-9YN166 drives too.


Chris from wrote on Sep 25th, 2014:

Yep mine has been acting very weird lately...writing to the disk would hang in windows and eventually freeze.. Installed HD Sentinel and it showed the Seagate 3TB has 4% health left and in critical condition... model: ST3000DM001-9YN166

Never buying seagate again..

Here's my log:
-- Physical Disk Information - Disk: #0: ST3000DM001-9YN166 --

Hard Disk Summary
-------------------
Hard Disk Number . . . . . . . . . . . . . . . . : 0
Interface . . . . . . . . . . . . . . . . . . . : S-ATA Gen3, 6 Gbps
Disk Controller . . . . . . . . . . . . . . . . : Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller - 1E02 (AHCI)
Disk Location . . . . . . . . . . . . . . . . . : Channel 2, Target 0, Lun 0, Device: 0
Hard Disk Model ID . . . . . . . . . . . . . . . : ST3000DM001-9YN166
Firmware Revision . . . . . . . . . . . . . . . : CC4B
Hard Disk Serial Number . . . . . . . . . . . . : Z1F0XVJX
Total Size . . . . . . . . . . . . . . . . . . . : 2861585 MB
Power State . . . . . . . . . . . . . . . . . . : Active
Logical Drive(s) . . . . . . . . . . . . . . . . : E: [BACKUP]
Current Temperature . . . . . . . . . . . . . . : 45 °C (Overheat)
Maximum Temperature (Ever Measured) . . . . . . : 51 °C, 9/24/2014 8:47:43 PM
Minimum Temperature (Ever Measured) . . . . . . : 45 °C, 9/24/2014 11:35:14 PM
Maximum Temperature (During Entire Lifespan) . . : 53 °C
Power On Time . . . . . . . . . . . . . . . . . : 654 days, 17 hours
Estimated Remaining Lifetime . . . . . . . . . . : 4 days
Health . . . . . . . . . . . . . . . . . . . . . : -------------------- 4 % (Critical)
Performance . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)

There are 55264 bad sectors on the disk surface. The contents of these sectors were moved to the spare area.
The drive found 12440 bad sectors during its self test.
There are 12440 weak sectors f


Claudio from Switzerland wrote on Jan 17th, 2014:

I just took a look at the serial numbers of the failed disks. One started with S1F as you said. The others started with W1F.


Fabian from Switzerland wrote on Jan 17th, 2014:

I have two more to add to this list. I have updated them to CC4H as soon as I received them, both have a serial-nr. that begins with S1F05 (as yours I think) and ran about 500 days.


RSS feed

Blog Tags:

  AWS   Android   Ansible   Apache   Apple   Atlassian   BSD   Backup   Bash   Bluecoat   CMS   Chef   Cloud   Coding   Consul   Containers   CouchDB   DB   DNS   Database   Databases   Docker   ELK   Elasticsearch   Filebeat   FreeBSD   Galera   Git   GlusterFS   Grafana   Graphics   HAProxy   HTML   Hacks   Hardware   Icinga   Influx   Internet   Java   KVM   Kibana   Kodi   Kubernetes   LVM   LXC   Linux   Logstash   Mac   Macintosh   Mail   MariaDB   Minio   MongoDB   Monitoring   Multimedia   MySQL   NFS   Nagios   Network   Nginx   OSSEC   OTRS   Office   PGSQL   PHP   Perl   Personal   PostgreSQL   Postgres   PowerDNS   Proxmox   Proxy   Python   Rancher   Rant   Redis   Roundcube   SSL   Samba   Seafile   Security   Shell   SmartOS   Solaris   Surveillance   Systemd   TLS   Tomcat   Ubuntu   Unix   VMWare   VMware   Varnish   Virtualization   Windows   Wireless   Wordpress   Wyse   ZFS   Zoneminder