Seek_Error_Rate on 1[TB] HGST Drive

Hi. I'm new in this forum. I want to ask you about a disk that I have purchased. The disk was taken from a new notebook to which an SSD was placed.

It is a guy who is dedicated to selling notebooks, which changes the disk that comes by default by an SSD disk at the request of customers.

The disk is a 1[TB] HGST Z5K1 (HTS541010B7E610). Attached below the gSmartControl LOG that I did as soon as I received it:

Code:: smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-43-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HGST HTS541010B7E610 Serial Number: WXN1AA7K3JAR LU WWN Device Id: 5 0014ee 6083c2672 Firmware Version: 03.01A03 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Feb 1 01:06:46 2019 -03 SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 254 (maximum performance) Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [SEC2] === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 660) seconds. Offline data collection capabilities: (0x51) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 73) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 32 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 100 100 050 - 0 3 Spin_Up_Time POS--K 057 056 021 - 1266 4 Start_Stop_Count -O--CK 100 100 000 - 19 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-K 100 100 030 - 37404 9 Power_On_Hours -O--CK 100 100 000 - 12 10 Spin_Retry_Count PO--CK 100 100 050 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 17 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error PO-RCK 100 100 097 - 0 187 Reported_Uncorrect -O--CK 100 100 000 - 0 188 Command_Timeout -O--CK 100 100 000 - 0 189 High_Fly_Writes -O-RCK 100 100 000 - 0 191 G-Sense_Error_Rate -O--CK 072 072 000 - 28 192 Power-Off_Retract_Count -O--CK 100 100 000 - 25769803782 193 Load_Cycle_Count -O--CK 100 100 000 - 245 194 Temperature_Celsius -O---K 035 040 000 - 35 (Min/Max 28/37) 197 Current_Pending_Sector -O--CK 100 100 000 - 0 198 Offline_Uncorrectable ----CK 100 100 000 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 240 Head_Flying_Hours -O--CK 100 100 000 - 6726 243 Unknown_Attribute -O--CK 100 100 000 - 8238 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 SATA NCQ Queued Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x24 GPL R/O 277 Current Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 74 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 26 (device log contains only the most recent 24 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 26 [1] occurred at disk power-on lifetime: 7 hours (0 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:04:21.800 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:04:21.800 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:04:21.527 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:04:21.524 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:04:21.524 READ DMA EXT Error 25 [0] occurred at disk power-on lifetime: 7 hours (0 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:03.857 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:03.857 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:00:03.559 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 00:00:03.558 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 00:00:03.557 READ DMA EXT Error 24 [23] occurred at disk power-on lifetime: 7 hours (0 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 02:37:20.094 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 02:37:20.094 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 02:37:15.998 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 02:37:15.995 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 02:37:15.995 READ DMA EXT Error 23 [22] occurred at disk power-on lifetime: 7 hours (0 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 02:31:01.363 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 02:31:01.363 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 02:31:01.075 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 02:31:01.072 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 02:31:01.072 READ DMA EXT Error 22 [21] occurred at disk power-on lifetime: 7 hours (0 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 02:19:43.665 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 02:19:43.665 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 02:19:43.376 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 02:19:43.374 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 02:19:43.374 READ DMA EXT Error 21 [20] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 01:58:37.213 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 01:58:37.212 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 01:58:36.921 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 01:58:36.920 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 01:58:36.920 READ DMA EXT Error 20 [19] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:50:13.500 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:50:13.500 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:50:13.207 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 00:50:13.206 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 00:50:13.205 READ DMA EXT Error 19 [18] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:43:42.870 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:43:42.870 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:43:42.578 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 00:43:42.577 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 00:43:42.576 READ DMA EXT Error 18 [17] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:32:45.985 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:32:45.984 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:32:45.698 READ DMA EXT 25 00 00 00 20 00 00 74 70 6d 8f e0 00 00:32:45.695 READ DMA EXT 25 00 00 00 20 00 00 00 00 00 02 e0 00 00:32:45.695 READ DMA EXT Error 17 [16] occurred at disk power-on lifetime: 4 hours (0 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:06.994 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:06.994 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:00:06.704 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:06.702 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:06.702 READ DMA EXT Error 16 [15] occurred at disk power-on lifetime: 4 hours (0 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:47:16.446 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:47:16.446 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:47:16.169 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:47:16.168 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:47:16.168 READ DMA EXT Error 15 [14] occurred at disk power-on lifetime: 4 hours (0 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:04:28.211 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:04:28.211 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:04:24.179 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:04:24.179 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:04:24.179 READ DMA EXT Error 14 [13] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:02.752 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:02.752 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:02.471 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:02.471 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:00:02.471 READ DMA EXT Error 13 [12] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:03.100 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:03.097 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:02.813 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:02.813 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:00:02.813 READ DMA EXT Error 12 [11] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 03:12:53.555 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 03:12:53.555 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 03:12:53.272 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 03:12:53.272 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 03:12:53.272 READ DMA EXT Error 11 [10] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 03:08:52.203 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 03:08:52.203 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 03:08:51.915 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 03:08:51.915 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 03:08:51.915 READ DMA EXT Error 10 [9] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 02:50:56.456 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 02:50:56.456 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 02:50:56.170 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 02:50:56.170 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 02:50:56.169 READ DMA EXT Error 9 [8] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 01:28:05.396 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 01:28:05.395 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 01:28:05.112 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 01:28:05.112 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 01:28:05.111 READ DMA EXT Error 8 [7] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:05:01.974 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:05:01.974 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:05:01.688 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:05:01.688 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:05:01.687 READ DMA EXT Error 7 [6] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:06.332 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:06.332 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:06.048 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:06.047 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 1f e0 00 00:00:06.047 READ DMA EXT Error 6 [5] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:03.482 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:03.482 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:00:03.187 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:03.184 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:03.184 READ DMA EXT Error 5 [4] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:03.375 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:03.374 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:00:03.085 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:03.083 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:03.082 READ DMA EXT Error 4 [3] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:00:26.493 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:00:26.493 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:00:26.218 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:00:26.216 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:00:26.216 READ DMA EXT Error 3 [2] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 04 -- 51 00 00 00 00 00 00 00 02 e0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- b4 00 20 00 00 00 00 00 72 4c 6b e0 00 00:03:00.968 SANITIZE DEVICE f5 00 00 00 00 00 00 00 00 00 00 e0 00 00:03:00.968 SECURITY FREEZE LOCK 25 00 00 00 01 00 00 00 00 00 00 e0 00 00:03:00.695 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 21 e0 00 00:03:00.693 READ DMA EXT 25 00 00 00 01 00 00 00 00 00 20 e0 00 00:03:00.693 READ DMA EXT SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 10 - # 2 Short offline Completed without error 00% 9 - # 3 Short offline Completed without error 00% 4 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Active (0) Current Temperature: 35 Celsius Power Cycle Min/Max Temperature: 28/37 Celsius Lifetime Min/Max Temperature: 22/40 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 128 (116) Index Estimated Time Temperature Celsius 117 2019-01-31 22:59 36 ***************** ... ..( 2 skipped). .. ***************** 120 2019-01-31 23:02 36 ***************** 121 2019-01-31 23:03 35 **************** ... ..( 36 skipped). .. **************** 30 2019-01-31 23:40 35 **************** 31 2019-01-31 23:41 34 *************** ... ..( 5 skipped). .. *************** 37 2019-01-31 23:47 34 *************** 38 2019-01-31 23:48 ? - 39 2019-01-31 23:49 34 *************** ... ..( 17 skipped). .. *************** 57 2019-02-01 00:07 34 *************** 58 2019-02-01 00:08 35 **************** 59 2019-02-01 00:09 34 *************** ... ..( 6 skipped). .. *************** 66 2019-02-01 00:16 34 *************** 67 2019-02-01 00:17 35 **************** 68 2019-02-01 00:18 34 *************** 69 2019-02-01 00:19 34 *************** 70 2019-02-01 00:20 34 *************** 71 2019-02-01 00:21 35 **************** 72 2019-02-01 00:22 35 **************** 73 2019-02-01 00:23 34 *************** 74 2019-02-01 00:24 35 **************** 75 2019-02-01 00:25 34 *************** ... ..( 15 skipped). .. *************** 91 2019-02-01 00:41 34 *************** 92 2019-02-01 00:42 ? - 93 2019-02-01 00:43 34 *************** ... ..( 4 skipped). .. *************** 98 2019-02-01 00:48 34 *************** 99 2019-02-01 00:49 35 **************** ... ..( 16 skipped). .. **************** 116 2019-02-01 01:06 35 **************** SCT Error Recovery Control: Read: 85 (8.5 seconds) Write: 85 (8.5 seconds) Device Statistics (GP/SMART Log 0x04) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 29 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 32 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 12718 Vendor specific

I have also made performance measurements with the Ubuntu Disks tool (Some screeshots are in Spanish, sorry

),

It also passes correctly to SMART tests.

I could not find detailed information about SMART data for HGST disks.

There are ATA errors (26) on the disk but all correspond, according to the LOG, to the first 7 hours of disk life. I suppose they correspond to the period in which the disc was in the factory. What worries me are two values. On the one hand G-Sense_Error_Rate, which originally was 28, and has increased to 33.

On the other hand, the RAW value of the variable Seek_Error_Rate, which changes all the time when operations are performed on the disk. The value changes increasing until it reaches a value between 65000 and 66000 (I assume that it must be 65535, for a 16 bit register), after which it restarts to zero and starts growing again. I attached a video conformed with screenshots of the moment it is restarted. The mentioned thing is observed while updating the SMART values in gSmartControl (I was making copies of files on the disk at the same time). Screenshots were taken approximately every two seconds. Can you assume that the RAW value is actually an error counter? Since the normalized values have not changed after copying approximately 500GB of junk files to disk.

Seek_Error_Rate_Restart.zip: [VIDEO] Seek_Error_Rate Reboot moment; (282.37 KiB) Downloaded 305 times

When there is no operation on the disk the value of Seek_Error_Rate increases very slowly (this was what worried me originally). As mentioned before, when performing operations on the disk, the value is triggered and begins to rise rapidly until reaching the mentioned threshold in which it is restarted, but the normalized value has not changed after 500 Gb of file copy.

I use Ubuntu 18.04 as my main system, but I have a partition with Windows 10, on which I have run CrystalDiskInfo.This is a capture of the SMART data represented on a hexadecimal basis.

I still have seven days to return the disk without costs, and I try to determine if the disk has problems. Is it possible that this behavior is normal?

Thank you very much for your answers.

Apologies for my bad English! Greetings.

ISTM that your drive is a rebadged WD model. I haven't noticed that WD's new Seek Error Rate attributes have changed in the way that you have discovered, but you seem to have interpreted them correctly. FWIW, Seagate's drives count up to 250 million seeks before rolling over. ISTM that there is nothing to be concerned about.

Seek_Error_Rate on 1[TB] HGST Drive

Seek_Error_Rate on 1[TB] HGST Drive

Re: Seek_Error_Rate on 1[TB] HGST Drive