[SOLVED] The dreaded Seek Error Rate bad issue

[EdBakersfield]

I have reviewed comments regarding hard disk (not SSD) bad seek error rates and I suspect there is more to this issue than meets the eye...or disk. I have a new Toshiba X300 8TB that shows as "bad" a seek error rate of 27 17 50 (50=threshold). However I am thinking that this may have more to do with the size of the drive than a true mechanical issue. After having backed up critical data, I find myself in the position of curiosity rather than despair. The thing does have a three year warranty. In the absence of other symptoms, is planning a funeral premature?

 

[SkyNetRising]

Can you show screenshot from HDtune health?
(upload to imgur.com and post link)

 

[fzabkar]

Your drive does appear to be sick. Is the Read Error Rate also reporting non-zero raw values?

 

[EdBakersfield]

Please, What are non-zero raw values?

 

[EdBakersfield]

data:
(02) TOSHIBA HDWR180
----------------------------------------------------------------------------
Model : TOSHIBA HDWR180
Firmware : 0603
Serial Number : 6130A07UFBLG
Disk Size : 8001.5 GB (8.4/137.4/8001.5/8001.5)
Buffer Size : Unknown
Queue Depth : 32
# of Sectors : 15628053168
Rotation Rate : 7200 RPM
Interface : Serial ATA
Major Version : ACS-3
Minor Version : ACS-3 Revision 5
Transfer Mode : SATA/600 | SATA/600
Power On Hours : 161 hours
Power On Count : 27 count
Temperature : 48 C (118 F)
Health Status : Bad
Features : S.M.A.R.T., APM, NCQ
APM Level : 0080h [ON]
AAM Level : ----
Drive Letter : G:

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 100 100 _50 000000000000 Read Error Rate
02 100 100 _50 000000000000 Throughput Performance
03 100 100 __1 000000001E4B Spin-Up Time
04 100 100 __0 000000000055 Start/Stop Count
05 100 100 _50 000000000000 Reallocated Sectors Count
07 _29 _17 _50 000000000000 Seek Error Rate
08 100 100 _50 000000000000 Seek Time Performance
09 100 100 __0 0000000000A1 Power-On Hours
0A 100 100 _30 000000000000 Spin Retry Count
0C 100 100 __0 00000000001B Power Cycle Count
BF 100 100 __0 000000000000 G-Sense Error Rate
C0 100 100 __0 000000000005 Power-off Retract Count
C1 100 100 __0 0000000000D3 Load/Unload Cycle Count
C2 100 100 __0 003200130030 Temperature
C4 100 100 __0 000000000000 Reallocation Event Count
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 200 __0 000000000000 UltraDMA CRC Error Count
DC 100 __1 __0 00000B0E0058 Disk Shift
DE 100 100 __0 000000000088 Loaded Hours
DF 100 100 __0 000000000000 Load/Unload Retry Count
E0 100 100 __0 000000000000 Load Friction
E2 100 100 __0 000000000219 Load 'In'-time
F0 100 100 __1 000000000000 Head Flying Hours

 

[USAFRet]

Why is this "dreaded"?

Drives die. All of them, eventually. Some earlier than others.
Replace and recover your data from the backup you made before this happened.

If still under warranty, free replacement.
If not under warranty, well, it had a good life.

 

[EdBakersfield]

Well I took out the 8TB drive and placed it in a separate location. As there were three drives in a rack, disk heat was uncomfortably high for my sensibilities. The vacant middle slot allowed drive temperatures to plummet by 10C. However SMART remains the same. I am teetering on a return as it is still within the30 day window.

 

[fzabkar]

Seek Error Rate and Read Error Rate values are rates rather than counts. This suggests that they are rolling averages rather than lifetime counts. That is, the raw value does not accumulate over the life of the drive, but is periodically recalculated. I don't understand why the Current normalised value (27) is below the threshold (50), but the raw value is zero. That seems contradictory. :-?

I confess I don't understand what is happening, but I notice that the Worst value of Disk Shift is 1. This attribute measures the eccentricity of the tracks on the disc. That is, if the drive has been severely bumped, then the platters may have shifted slightly off-centre. This could explain the seek error problem, but I can't understand how a Disk Shift could correct itself (Current value = 100). :-?

Also, I notice that G-Sense Error Rate is 0, so this would suggest that the drive has never been bumped while it was running.

 

[USAFRet]

Well I took out the 8TB drive and placed it in a separate location. As there were three drives in a rack, disk heat was uncomfortably high for my sensibilities. The vacant middle slot allowed drive temperatures to plummet by 10C. However SMART remains the same. I am teetering on a return as it is still within the30 day window.

I have an 8TB X300 in a 4 bay QNAP.
Current temp is 37C.
Power On = 990 days


But I also had a 16TB Tosh Enterprise start throwing errors at 7 months out of the box.
RMA, replaced.