joeshmoe1 Posted March 24, 2018 Share Posted March 24, 2018 Hi folks, My Toshiba 4TB drive started showing a few errors in the dashboard after about two years. First 8, then two hundred and some. It seemed to stabilize there, but of course that didn't inspire confidence. I replaced the drive, and after a successful rebuild, precleared the Toshiba. The following SMART report is from after the preclear. Is the drive toast? Has my data been corrupted? Thanks smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.26-unRAID] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" MD04ACA... Enterprise HDD Device Model: TOSHIBA MD04ACA400 Serial Number: Y583KQ2MFSAA LU WWN Device Id: 5 000039 6ab80138c Firmware Version: FP2A User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Mar 24 16:28:07 2018 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 128 (minimum power consumption without standby) Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 112) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 120) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 477) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 050 - 0 2 Throughput_Performance P-S--- 100 100 050 - 0 3 Spin_Up_Time POS--K 100 100 001 - 6764 4 Start_Stop_Count -O--CK 100 100 000 - 3132 5 Reallocated_Sector_Ct PO--CK 100 100 050 - 0 7 Seek_Error_Rate PO-R-- 100 100 050 - 0 8 Seek_Time_Performance P-S--- 100 100 050 - 0 9 Power_On_Hours -O--CK 058 058 000 - 17168 10 Spin_Retry_Count PO--CK 162 100 030 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 40 191 G-Sense_Error_Rate -O--CK 100 100 000 - 125 192 Power-Off_Retract_Count -O--CK 100 100 000 - 35 193 Load_Cycle_Count -O--CK 099 099 000 - 12390 194 Temperature_Celsius -O---K 100 100 000 - 29 (Min/Max 10/53) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O--CK 100 100 000 - 24 198 Offline_Uncorrectable ----CK 100 100 000 - 3 199 UDMA_CRC_Error_Count -O--CK 200 253 000 - 0 220 Disk_Shift -O---- 100 100 000 - 0 222 Loaded_Hours -O--CK 073 073 000 - 10909 223 Load_Retry_Count -O--CK 100 100 000 - 0 224 Load_Friction -O---K 100 100 000 - 0 226 Load-in_Time -OS--K 100 100 000 - 294 240 Head_Flying_Hours P----- 100 100 001 - 0 ||||||_ 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 51 Comprehensive SMART error log 0x03 GPL R/O 64 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x24 GPL R/O 12288 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 0xa7 GPL VS 8 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 (64 sectors) Device Error Count: 8 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 8 [7] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:54.083 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+15:07:54.080 READ LOG EXT 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:51.218 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c8 40 00 4d+15:07:51.218 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c0 40 00 4d+15:07:51.218 READ FPDMA QUEUED Error 7 [6] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:51.218 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c8 40 00 4d+15:07:51.218 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c0 40 00 4d+15:07:51.218 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 b8 40 00 4d+15:07:51.073 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 b0 40 00 4d+15:07:49.894 READ FPDMA QUEUED Error 6 [5] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 03 a0 00 00 00 01 ac 49 e2 f8 40 00 4d+15:07:47.292 READ FPDMA QUEUED 60 02 00 00 00 00 01 ac 49 e0 f8 40 00 4d+15:07:47.292 READ FPDMA QUEUED 60 01 00 00 00 00 01 ac 49 df f8 40 00 4d+15:07:47.289 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 db f8 40 00 4d+15:07:47.283 READ FPDMA QUEUED 60 03 00 00 00 00 01 ac 49 d8 f8 40 00 4d+15:07:47.282 READ FPDMA QUEUED Error 5 [4] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:42.614 READ FPDMA QUEUED 2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+15:07:42.613 READ LOG EXT 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:39.751 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c8 40 00 4d+15:07:39.751 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c0 40 00 4d+15:07:39.473 READ FPDMA QUEUED Error 4 [3] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 08 00 00 00 01 ac 49 e3 d0 40 00 4d+15:07:39.751 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c8 40 00 4d+15:07:39.751 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 c0 40 00 4d+15:07:39.473 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 b8 40 00 4d+15:07:37.667 READ FPDMA QUEUED 60 00 08 00 00 00 01 ac 49 e3 b0 40 00 4d+15:07:37.525 READ FPDMA QUEUED Error 3 [2] occurred at disk power-on lifetime: 17156 hours (714 days + 20 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d0 40 00 Error: UNC at LBA = 0x1ac49e3d0 = 7185490896 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 03 a0 00 00 00 01 ac 49 e2 f8 40 00 4d+15:07:32.316 READ FPDMA QUEUED 60 02 00 00 00 00 01 ac 49 e0 f8 40 00 4d+15:07:32.314 READ FPDMA QUEUED 60 01 00 00 00 00 01 ac 49 df f8 40 00 4d+15:07:32.313 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 db f8 40 00 4d+15:07:32.308 READ FPDMA QUEUED 60 03 00 00 00 00 01 ac 49 d8 f8 40 00 4d+15:07:32.305 READ FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 16611 hours (692 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 d8 40 00 Error: UNC at LBA = 0x1ac49e3d8 = 7185490904 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 ac 49 e2 10 40 00 3d+00:42:36.524 READ FPDMA QUEUED 60 00 48 00 00 00 01 ac 49 e1 c8 40 00 3d+00:42:36.519 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 dd c8 40 00 3d+00:42:36.517 READ FPDMA QUEUED 60 00 58 00 00 00 01 ac 49 dd 70 40 00 3d+00:42:36.513 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 d9 70 40 00 3d+00:42:36.510 READ FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 15940 hours (664 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 -- -- -- == -- == == == -- -- -- -- -- 40 -- 41 00 00 00 01 ac 49 e3 c0 40 00 Error: UNC at LBA = 0x1ac49e3c0 = 7185490880 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 ac 49 e1 c0 40 00 24d+17:42:18.047 READ FPDMA QUEUED 60 00 a0 00 00 00 01 ac 49 e1 20 40 00 24d+17:42:18.042 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 dd 20 40 00 24d+17:42:18.039 READ FPDMA QUEUED 60 04 00 00 00 00 01 ac 49 d9 20 40 00 24d+17:42:18.031 READ FPDMA QUEUED 60 00 60 00 00 00 01 ac 49 d8 c0 40 00 24d+17:42:18.028 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 00% 17166 7185490896 # 2 Short offline Completed without error 00% 16042 - 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): 1 (0x0001) SCT Support Level: 1 Device State: Active (0) Current Temperature: 29 Celsius Power Cycle Min/Max Temperature: 27/38 Celsius Lifetime Min/Max Temperature: 10/53 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 5/55 Celsius Min/Max Temperature Limit: 5/55 Celsius Temperature History Size (Index): 478 (262) Index Estimated Time Temperature Celsius 263 2018-03-24 08:31 38 ******************* ... ..( 10 skipped). .. ******************* 274 2018-03-24 08:42 38 ******************* 275 2018-03-24 08:43 37 ****************** ... ..( 52 skipped). .. ****************** 328 2018-03-24 09:36 37 ****************** 329 2018-03-24 09:37 36 ***************** 330 2018-03-24 09:38 36 ***************** 331 2018-03-24 09:39 37 ****************** 332 2018-03-24 09:40 36 ***************** ... ..( 93 skipped). .. ***************** 426 2018-03-24 11:14 36 ***************** 427 2018-03-24 11:15 37 ****************** ... ..( 40 skipped). .. ****************** 468 2018-03-24 11:56 37 ****************** 469 2018-03-24 11:57 38 ******************* 470 2018-03-24 11:58 38 ******************* 471 2018-03-24 11:59 37 ****************** 472 2018-03-24 12:00 38 ******************* ... ..( 4 skipped). .. ******************* 477 2018-03-24 12:05 38 ******************* 0 2018-03-24 12:06 37 ****************** 1 2018-03-24 12:07 38 ******************* 2 2018-03-24 12:08 38 ******************* 3 2018-03-24 12:09 38 ******************* 4 2018-03-24 12:10 37 ****************** 5 2018-03-24 12:11 38 ******************* 6 2018-03-24 12:12 37 ****************** ... ..( 3 skipped). .. ****************** 10 2018-03-24 12:16 37 ****************** 11 2018-03-24 12:17 38 ******************* 12 2018-03-24 12:18 37 ****************** 13 2018-03-24 12:19 37 ****************** 14 2018-03-24 12:20 38 ******************* 15 2018-03-24 12:21 37 ****************** ... ..( 4 skipped). .. ****************** 20 2018-03-24 12:26 37 ****************** 21 2018-03-24 12:27 36 ***************** ... ..( 11 skipped). .. ***************** 33 2018-03-24 12:39 36 ***************** 34 2018-03-24 12:40 35 **************** ... ..( 3 skipped). .. **************** 38 2018-03-24 12:44 35 **************** 39 2018-03-24 12:45 34 *************** ... ..( 5 skipped). .. *************** 45 2018-03-24 12:51 34 *************** 46 2018-03-24 12:52 33 ************** 47 2018-03-24 12:53 33 ************** 48 2018-03-24 12:54 34 *************** ... ..( 2 skipped). .. *************** 51 2018-03-24 12:57 34 *************** 52 2018-03-24 12:58 35 **************** ... ..( 6 skipped). .. **************** 59 2018-03-24 13:05 35 **************** 60 2018-03-24 13:06 36 ***************** ... ..( 42 skipped). .. ***************** 103 2018-03-24 13:49 36 ***************** 104 2018-03-24 13:50 35 **************** 105 2018-03-24 13:51 35 **************** 106 2018-03-24 13:52 34 *************** 107 2018-03-24 13:53 35 **************** 108 2018-03-24 13:54 35 **************** 109 2018-03-24 13:55 35 **************** 110 2018-03-24 13:56 34 *************** ... ..( 31 skipped). .. *************** 142 2018-03-24 14:28 34 *************** 143 2018-03-24 14:29 33 ************** 144 2018-03-24 14:30 34 *************** 145 2018-03-24 14:31 33 ************** 146 2018-03-24 14:32 34 *************** 147 2018-03-24 14:33 33 ************** ... ..( 23 skipped). .. ************** 171 2018-03-24 14:57 33 ************** 172 2018-03-24 14:58 32 ************* 173 2018-03-24 14:59 32 ************* 174 2018-03-24 15:00 32 ************* 175 2018-03-24 15:01 31 ************ ... ..( 6 skipped). .. ************ 182 2018-03-24 15:08 31 ************ 183 2018-03-24 15:09 30 *********** ... ..( 6 skipped). .. *********** 190 2018-03-24 15:16 30 *********** 191 2018-03-24 15:17 29 ********** ... ..( 19 skipped). .. ********** 211 2018-03-24 15:37 29 ********** 212 2018-03-24 15:38 28 ********* 213 2018-03-24 15:39 28 ********* 214 2018-03-24 15:40 29 ********** 215 2018-03-24 15:41 28 ********* 216 2018-03-24 15:42 29 ********** 217 2018-03-24 15:43 28 ********* 218 2018-03-24 15:44 29 ********** ... ..( 3 skipped). .. ********** 222 2018-03-24 15:48 29 ********** 223 2018-03-24 15:49 28 ********* 224 2018-03-24 15:50 29 ********** ... ..( 2 skipped). .. ********** 227 2018-03-24 15:53 29 ********** 228 2018-03-24 15:54 28 ********* 229 2018-03-24 15:55 28 ********* 230 2018-03-24 15:56 29 ********** ... ..( 2 skipped). .. ********** 233 2018-03-24 15:59 29 ********** 234 2018-03-24 16:00 28 ********* 235 2018-03-24 16:01 29 ********** 236 2018-03-24 16:02 29 ********** 237 2018-03-24 16:03 28 ********* 238 2018-03-24 16:04 28 ********* 239 2018-03-24 16:05 29 ********** 240 2018-03-24 16:06 28 ********* 241 2018-03-24 16:07 29 ********** ... ..( 20 skipped). .. ********** 262 2018-03-24 16:28 29 ********** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 2) == 0x01 0x008 4 40 --- Lifetime Power-On Resets 0x01 0x010 4 17168 --- Power-on Hours 0x01 0x018 6 29367039616 --- Logical Sectors Written 0x01 0x020 6 37351446 --- Number of Write Commands 0x01 0x028 6 348686688970 --- Logical Sectors Read 0x01 0x030 6 607260610 --- Number of Read Commands 0x02 ===== = = === == Free-Fall Statistics (rev 1) == 0x02 0x010 4 125 --- Overlimit Shock Events 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 12321 --- Spindle Motor Power-on Hours 0x03 0x010 4 10909 --- Head Flying Hours 0x03 0x018 4 12390 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 9 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 8 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 29 --- Current Temperature 0x05 0x010 1 35 N-- Average Short Term Temperature 0x05 0x018 1 31 N-- Average Long Term Temperature 0x05 0x020 1 53 --- Highest Temperature 0x05 0x028 1 10 --- Lowest Temperature 0x05 0x030 1 46 N-- Highest Average Short Term Temperature 0x05 0x038 1 20 N-- Lowest Average Short Term Temperature 0x05 0x040 1 41 N-- Highest Average Long Term Temperature 0x05 0x048 1 24 N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 55 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 5 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 324 --- Number of Hardware Resets 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x0002 4 0 R_ERR response for data FIS 0x0003 4 0 R_ERR response for device-to-host data FIS 0x0004 4 0 R_ERR response for host-to-device data FIS 0x0005 4 0 R_ERR response for non-data FIS 0x0006 4 0 R_ERR response for device-to-host non-data FIS 0x0007 4 0 R_ERR response for host-to-device non-data FIS 0x0008 4 0 Device-to-host non-data FIS retries 0x0009 4 3 Transition from drive PhyRdy to drive PhyNRdy 0x000a 4 5 Device-to-host register FISes sent due to a COMRESET 0x000b 4 0 CRC errors within host-to-device FIS 0x000d 4 0 Non-CRC errors within host-to-device FIS 0x000f 4 0 R_ERR response for host-to-device data FIS, CRC 0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC 0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC 0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC Quote Link to comment
JorgeB Posted March 24, 2018 Share Posted March 24, 2018 4 minutes ago, joeshmoe1 said: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 00% 17166 7185490896 This is all you need to see, failed SMART test is a failed disk. Quote Link to comment
joeshmoe1 Posted March 24, 2018 Author Share Posted March 24, 2018 1 hour ago, johnnie.black said: This is all you need to see, failed SMART test is a failed disk. Thanks for the response Johnnie. How about question #2? Is the data OK? I have a backup of the important stuff, but eventually it will get overwritten with a new backup. Quote Link to comment
JorgeB Posted March 24, 2018 Share Posted March 24, 2018 Data on the rebuilt disk should be OK but only way to know for sure is if you have cheksums (or are using btrfs) 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.