• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Large SMART values in error rows for Seagate Constellation ES.3

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
N

nstgc

Registered
​
Joined
Dec 21, 2013
I just recieved a Seagate Constellation ES.3 today and as soon as I started it the first thing I did was run smartctl to check the SMART data. Was I in for a shocker.

Code: 
  1 Raw_Read_Error_Rate     0x000f   100   100   044    Pre-fail  Always       -       7535
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       56442
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       0
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   075   075   045    Old_age   Always       -       25 (Min/Max 19/25)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0022   025   040   000    Old_age   Always       -       25 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       7535
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   253   000    Old_age   Always       -       0

I don't know about Seagate, but if one of my WD RE's gave me errors like that I'd be submitting and RMA request instantly. I sent out an email to Seagate, but I thought I should post on these boards as well.

[edit] After running a basic benchmark with Gnome Disks the errors jumped. Also, the speeds I got were quite different from what I've seem in other benchmarks. I didn't buy this thing for its speed, but when hardware preforms this far from spec I suspect something is wrong.

Code: 
  1 Raw_Read_Error_Rate     0x000f   067   067   044    Pre-fail  Always       -       6053358
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       158255
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       0
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   073   073   045    Old_age   Always       -       27 (Min/Max 19/27)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1
194 Temperature_Celsius     0x0022   027   040   000    Old_age   Always       -       27 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   016   016   000    Old_age   Always       -       6053358
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

[edit2] By the way, to contrast, here is the same sort of data from my Western Digital RE4

Code: 
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   175   172   021    Pre-fail  Always       -       4250
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       -       2430
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       8876
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       2072
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       190
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2239
194 Temperature_Celsius     0x0022   119   101   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       1
 
Last edited:
Ok.

When you say revived, that seems to me that the thing wasn't new (which then makes me question the point)? How old is the drive? I mean, its hard to be on the same thought process as you not knowing if the drive is new or...............? It says one power cycle so I am assuming its new?

If so, yeah, likely RMA. It happens. :(


EDIT: Ohhhhhhhhhhhh, maybe you meant "received"??? THAT would make more sense!! LOL, gotcha.

Yeah, likely an RMA. :(
 
I'm sorry. Typo. I meant "recieved". The drive has been on for less than an hour. Its new.

[edit] I'm talking to Amazon now. This is ****ing rediculous. I used Seagate drives in the past. They were good, then very bad, then I waited 8 years to see if they improved. Nope.
 
EarthDog said:
It happens. Spilled milk. RMA and move on. :)
Click to expand...

My real issue is the lost time. I have several things I tend to do to drives once I get them. First, I run clairvoyance smart test which is intended to detect damage done in transit. Second, extended SMART self test just to be safe. I skip this with the WD's enterprise drives since they are all individually burn tested (saves a lot of head ache). Third, I run badblocks. Lastly, and I'm just starting this one since a friend of mine (and system admin) suggested using encryption, is to write random blocks to the drive to make free space indistinguishable from encrypted data. Writing urandom takes days, as does the bad block test.

[edit] Also, while I've learned to expect bad drives from Seagate, I didn't expect non-zero seek errors right out of the box. That's insane.
 
Last edited:
Sounds like a lot of effort...just not sure if it's worth it in the return on time department. I've had dozens of drives in my time and never once did any of those things and managed only to lose files by my own negligence. Not sure I would be labeled lucky. ;)

Sorry you got a doa a drive, it sucks. Hopefully the RMA process is quick for ya. Report back! :)
 
I'm in the "better safe than sorry" club. Aside from Seagate drives, I've never had a problem. After Seagate I moved to Samsung Spinmasters. When Samsung's HDD business got bought by Seagate I bailed to Western Digital and have been quite happy there. Lots of good drives from them. i just was looking for a feature they don't offer.

[edit] Okay, so I decided to check with a different program. I've been using smartctl, but I tried HD Sentinel instead. I don't know if its giving me better info or not. I'll have to check on the Arch forums (which isn't as scaring as many likely think).

Code: 
No.  Attribute                Thre.. Value  Worst  Data                Status                   Flags                                                  
1    Raw Read Error Rate      44     69     67     0000007EE736        OK                       Error-Rate, Performance, Statistical, Critical
3    Spin Up Time             0      99     99     000000000000        OK (Always passing)      Statistical, Critical
4    Start/Stop Count         20     100    100    000000000001        OK                       Self Preserving, Event Count, Statistical
5    Reallocated Sectors Co.. 10     100    100    000000000000        OK                       Self Preserving, Event Count, Statistical, Critical
7    Seek Error Rate          30     60     60     0000001360CF        OK                       Error-Rate, Performance, Statistical, Critical
9    Power On Time Count      0      100    100    000000000003        OK (Always passing)      Self Preserving, Event Count, Statistical
10   Spin Retry Count         97     100    100    000000000000        OK                       Event Count, Statistical, Critical
12   Drive Power Cycle Count  20     100    100    000000000001        OK                       Self Preserving, Event Count, Statistical
184  End-to-End Error Count   99     100    100    000000000000        OK                       Self Preserving, Event Count, Statistical
187  Reported Uncorrectable.. 0      100    100    000000000000        OK (Always passing)      Self Preserving, Event Count, Statistical
188  Command Timeout          0      100    100    000000000000        OK (Always passing)      Self Preserving, Event Count, Statistical
189  High Fly Writes          0      100    100    000000000000        OK (Always passing)      Self Preserving, Event Count, Error-Rate, Statistical
190  Airflow Temperature      45     73     72     00001C13001B        OK                       Self Preserving, Statistical
191  G-Sense Error Rate       0      100    100    000000000000        OK (Always passing)      Self Preserving, Event Count, Statistical
192  Power off Retract Cycl.. 0      100    100    000000000000        OK (Always passing)      Self Preserving, Event Count, Statistical
193  Load/Unload Cycle Count  0      100    100    000000000001        OK (Always passing)      Self Preserving, Event Count, Statistical
194  Disk Temperature         0      27     40     00130000001B        OK (Always passing)      Self Preserving, Statistical
195  Hardware ECC Recovered   0      9      9      0000007EE736        OK (Always passing)      Event Count, Error-Rate, Statistical
197  Current Pending Sector.. 0      100    100    000000000000        OK (Always passing)      Event Count, Statistical
198  Off-Line Uncorrectable.. 0      100    100    000000000000        OK (Always passing)      Event Count
199  Ultra ATA CRC Error Co.. 0      200    200    000000000000        OK (Always passing)      Self Preserving, Event Count, Error-Rate, Performanc..

It seems as if smartctl isn't properly displaying the correct code resulting in the confusion. Everything is okay I guess.

[edit2] Looking at this it seems as if this new set of information actually indicates that there is absolutely nothing wrong.

[edit3] http://comments.gmane.org/gmane.linux.utilities.smartmontools/8404

Apparently you need to have drives added to smartctl's database. If it isn't added, you get garbage. From what I've been reading by googling "seagate smartctl" this is an issue on all of their drives. I'm just going to call them and ask what Linux software they would suggest for reading SMART data.
 
Last edited:
Very. I haven't confirmed any of this, of course, but I'm as close to 100% certain as I can be.

Also, I think if I converted the output of smartctl to HEX and then read it as it was meant to be read, it would all come out the same.
 
I don't think you can compare those statistics between brands and perhaps even between drive models from the same manufacturer. There seems to be a lot of variability between how recoverable errors get reported. For example read errors are no problem if they can be recovered via CRC. As density of bits on the media goes up, read errors become more common and the drive is designed to accommodate them. Of all the numbers, the one that concerns me the most is remapped sectors because that indicates a sector that has had so many problems it could no longer be used. If that number continues to grown the drive is failing.

Nevertheless, it would be nice if drive manufacturers provided the information to get their drives in the smartctl database. (I'm assuming it's not there because it is not readily available.) Seagate has a Linux diagnostic program but I don't think they have maintained it for years.

I've gone off Seagate drives since I had one - a 2TB model - fail (and I found out my experience was all too common.) No problems with any WD drives so far.
 
Seagate's consumer drives, from what I've read, have an AFR of about 10%. I'm assuming that sort of thing doesn't fly in an enterprise setting. [edit] They list 0.63% AFR for the drive I just got, and I'm planning on populating my RAID with V.4's which have a 0.44% AFR.[/edit]

My first thought was to get a WD Re with SED, but they just don't sell them. I've had great luck with WD, but they simply don't have want I'm looking for.

[edit2] I've heard back from Seagate. They explicitly said that they don't support Linux. If Hitachi drivers weren't significantly louder I would give Seagate the finger return this seemingly functional drive and get one of Hitachi's. They are, after all, owned by WD.

[edit3] Seriously though. How can you say you support server infrastructure and not support the #1 server operating system?!
 
Last edited:
"Since we don't support a Linux environment..." -- SG Tech Rep

Nope. None. If you search Google you come up with a program that hasn't been updated in over 10 years. I tried to use it and it doesn't properly recognize my drive.

[edit] I myself am shocked. I couldn't make this **** up if I wanted to, its just unreal. I can understand a ATi/AMD that has nothing to do with servers or work stations pulling this, but anyone who wants to work in the enterprise section, I figured, would need this. Thank God for the internet, or I would never figure out how to use any of my drive's features.
 
Last edited:
What's odd to me is that we have an EMC based DASD that sports Seagate drives. I believe that DASD runs RHEL underneath...?

I've seen a few Linuxless shops in my day though...
 
EarthDog said:
What's odd to me is that we have an EMC based DASD that sports Seagate drives. I believe that DASD runs RHEL underneath...?

I've seen a few Linuxless shops in my day though...
Click to expand...

Is support coming from Seagate, or someone in house? They have pretty decent documentation so maybe it is.

petteyg359 said:
That is absolutely ridiculous. Glad I've been buying nothing but Hitachi for years.
Click to expand...

I'm seriously reconsidering my switch to Seagate.

This is like if Steam didn't sell Windows games or if Angry Birds didn't run on smart phones.
 
Its through EMC. I'm not going to tell you how many drives we have replaced over the last 3 years. :shock:
 
Confirmation:

Seagate said:
Thank you for getting back to us. I'm happy to see that the drive is working properly. I understand that you wish to know if you need to use the first four numbers of read and seak errors to determine the raw SMART status. I will gladly assist you with that.

The numbers resulting from getting the first four digits from the left of the hexadecimal value are the number of errors, the rest of the hexadecimal value (eight hex digits from the right) is the number of good operations.

For additional assistance, feel free to reply to this email.
Click to expand...

So yeah, the drive is fine. Still no Linux support, but they do offer a DOS untility so I guess that's good enough.
 
I also recently purchased a constellation and SMART parameters are not too good.
Code: 
                                               Value   Worst   Thre.                            raw value
           1 Raw_Read_Error_Rate     0x000f     066     066     044     Pre-fail  Always   -    70342312
           191 G-Sense_Error_Rate    0x0032     100     100     000     Old_age   Always   -    960

Value and Worst of Raw_Read_Error (66) are quite close to the threshold (44)
Also G-Sense_Error_Rate (but I use HDD Removable Frames) displays an enough high value (960)
 
You must log in or register to reply here.

Similar threads

O
New drive with 100gb used?!
Replies
7
Views
1K
HankB
HankB
HankB
Resurrecting a failed SSD
Replies
4
Views
1K
HankB
HankB
HankB
Another one (SSD) bites the dust.
Replies
10
Views
2K
Woomack
W
HankB
Current_Pending_Sector woe (WD30EFRX)
Replies
5
Views
590
HankB
HankB
Z
SSD Crucial M4 I/O error
Replies
4
Views
1K
zook
Z
Back