Steven Roberts

Thanks for your time. One 3TB WD Red in the bin!

Thank you for your time and spotting that line in amongst everything. So I guess that is basically saying 10% of the 3TB drive is already trash? Steve.

Hi, I recently moved 2.4TB of files off a 3TB drive, then ran pre clear ready to add it to my array. Pre clear through up a few issues that I have never had before and then I ran an extended test. Here are the results, please advise is this savable or should it be binned? ================================================================== 1.20 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 64 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 16:06:59 ========================================================================1.20 == WDCWD30EFRX-68EUZN0 WD-WCC4N2REK1X7 == Disk /dev/sde has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 114 116 0 ok 36 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 60 sectors are pending re-allocation at the end of the preclear, a change of 60 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N2REK1X7 LU WWN Device Id: 5 0014ee 26258e985 Firmware Version: 82.00A82 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Oct 18 08:41:45 2021 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Disabled 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 113) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (38940) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 391) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) 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 POSR-K 200 200 051 - 1179 3 Spin_Up_Time POS--K 188 178 021 - 5600 4 Start_Stop_Count -O--CK 099 099 000 - 1519 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 072 072 000 - 20841 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 30 192 Power-Off_Retract_Count -O--CK 200 200 000 - 6 193 Load_Cycle_Count -O--CK 197 197 000 - 9323 194 Temperature_Celsius -O---K 115 110 000 - 35 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 60 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 11 ||||||_ 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 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb7 GPL,SL VS 1 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: 167 (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 167 [22] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 53 de 2c a0 40 00 Error: UNC at LBA = 0x153de2ca0 = 5702036640 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 18 00 01 53 de 2c a0 40 08 5d+22:02:27.635 READ FPDMA QUEUED 60 00 08 00 10 00 01 53 de 2c 98 40 08 5d+22:02:27.513 READ FPDMA QUEUED 60 00 08 00 c8 00 01 53 de 2c 90 40 08 5d+22:02:27.480 READ FPDMA QUEUED 60 00 08 00 c0 00 01 53 de 2c 88 40 08 5d+22:02:26.769 READ FPDMA QUEUED 60 00 08 00 b8 00 01 53 de 2c 80 40 08 5d+22:02:26.758 READ FPDMA QUEUED Error 166 [21] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 53 de 2e 98 40 00 Error: UNC at LBA = 0x153de2e98 = 5702037144 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 02 68 00 38 00 01 53 de 2e 88 40 08 5d+22:02:10.062 READ FPDMA QUEUED 60 05 40 00 30 00 01 56 db 7f 70 40 08 5d+22:02:10.062 READ FPDMA QUEUED 60 04 c0 00 28 00 01 56 db 84 b0 40 08 5d+22:02:10.062 READ FPDMA QUEUED 60 05 40 00 20 00 01 56 db 89 70 40 08 5d+22:02:10.062 READ FPDMA QUEUED 60 04 c0 00 18 00 01 56 db 8e b0 40 08 5d+22:02:10.062 READ FPDMA QUEUED Error 165 [20] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 53 de 2c 58 40 00 Error: UNC at LBA = 0x153de2c58 = 5702036568 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 c0 00 88 00 01 56 db 84 b0 40 08 5d+22:02:03.050 READ FPDMA QUEUED 60 05 40 00 80 00 01 56 db 7f 70 40 08 5d+22:02:03.050 READ FPDMA QUEUED 60 04 c0 00 78 00 01 56 db 7a b0 40 08 5d+22:02:03.043 READ FPDMA QUEUED 60 05 40 00 70 00 01 56 db 75 70 40 08 5d+22:02:03.043 READ FPDMA QUEUED 60 04 c0 00 68 00 01 56 db 70 b0 40 08 5d+22:02:03.043 READ FPDMA QUEUED Error 164 [19] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 55 cc 42 78 40 00 Error: UNC at LBA = 0x155cc4278 = 5734417016 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 a8 00 01 55 cc 42 78 40 08 5d+21:59:45.937 READ FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 a0 08 5d+21:59:45.919 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 00 00 00 00 00 e0 08 5d+21:59:45.919 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 5d+21:59:45.918 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 5d+21:59:45.918 SET FEATURES [Set transfer mode] Error 163 [18] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 55 cc 42 78 40 00 Error: UNC at LBA = 0x155cc4278 = 5734417016 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 80 00 01 55 cc 42 78 40 08 5d+21:59:42.391 READ FPDMA QUEUED 60 00 08 00 78 00 01 55 cc 42 70 40 08 5d+21:59:42.358 READ FPDMA QUEUED 60 00 08 00 70 00 01 55 cc 42 68 40 08 5d+21:59:42.280 READ FPDMA QUEUED 60 00 08 00 68 00 01 55 cc 42 60 40 08 5d+21:59:42.247 READ FPDMA QUEUED 60 00 08 00 60 00 01 55 cc 42 58 40 08 5d+21:59:42.247 READ FPDMA QUEUED Error 162 [17] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 55 cc 42 78 40 00 Error: UNC at LBA = 0x155cc4278 = 5734417016 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 0a 00 00 d8 00 01 55 cc 40 f8 40 08 5d+21:59:35.231 READ FPDMA QUEUED 60 0a 00 00 d0 00 01 55 cc 36 f8 40 08 5d+21:59:35.171 READ FPDMA QUEUED 60 0a 00 00 c8 00 01 55 cc 2c f8 40 08 5d+21:59:33.578 READ FPDMA QUEUED 60 0a 00 00 b8 00 01 55 cc 22 f8 40 08 5d+21:59:33.518 READ FPDMA QUEUED 60 06 c0 00 b0 00 01 55 cc 1c 38 40 08 5d+21:59:27.591 READ FPDMA QUEUED Error 161 [16] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 55 b5 be 08 40 00 Error: UNC at LBA = 0x155b5be08 = 5732941320 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 08 00 01 55 b5 be 08 40 08 5d+21:58:47.025 READ FPDMA QUEUED 60 00 08 00 00 00 01 55 b5 be 00 40 08 5d+21:58:46.914 READ FPDMA QUEUED 60 00 08 00 f8 00 01 55 b5 bd f8 40 08 5d+21:58:46.814 READ FPDMA QUEUED 60 00 08 00 b8 00 01 55 b5 bd f0 40 08 5d+21:58:46.770 READ FPDMA QUEUED 60 00 08 00 b0 00 01 55 b5 bd e8 40 08 5d+21:58:46.725 READ FPDMA QUEUED Error 160 [15] occurred at disk power-on lifetime: 20833 hours (868 days + 1 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 -- 51 00 00 00 01 55 b5 be 08 40 00 Error: UNC at LBA = 0x155b5be08 = 5732941320 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 06 20 00 00 00 01 55 b5 bf 50 40 08 5d+21:58:39.499 READ FPDMA QUEUED 60 03 10 00 f0 00 01 55 b5 bc 40 40 08 5d+21:58:39.498 READ FPDMA QUEUED 60 01 88 00 e8 00 01 55 b5 ba b8 40 08 5d+21:58:39.480 READ FPDMA QUEUED 60 0a 00 00 e0 00 01 55 b5 b0 b8 40 08 5d+21:58:39.464 READ FPDMA QUEUED 60 0a 00 00 d8 00 01 55 b5 a6 b8 40 08 5d+21:58:39.447 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 10% 20841 5701892488 # 2 Short offline Completed without error 00% 20552 - 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) Device State: Active (0) Current Temperature: 35 Celsius Power Cycle Min/Max Temperature: 29/38 Celsius Lifetime Min/Max Temperature: 13/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): 478 (41) Index Estimated Time Temperature Celsius 42 2021-10-18 00:44 33 ************** ... ..( 8 skipped). .. ************** 51 2021-10-18 00:53 33 ************** 52 2021-10-18 00:54 34 *************** ... ..( 2 skipped). .. *************** 55 2021-10-18 00:57 34 *************** 56 2021-10-18 00:58 35 **************** ... ..( 6 skipped). .. **************** 63 2021-10-18 01:05 35 **************** 64 2021-10-18 01:06 36 ***************** ... ..(277 skipped). .. ***************** 342 2021-10-18 05:44 36 ***************** 343 2021-10-18 05:45 37 ****************** ... ..(106 skipped). .. ****************** 450 2021-10-18 07:32 37 ****************** 451 2021-10-18 07:33 36 ***************** ... ..( 4 skipped). .. ***************** 456 2021-10-18 07:38 36 ***************** 457 2021-10-18 07:39 35 **************** 458 2021-10-18 07:40 36 ***************** ... ..( 10 skipped). .. ***************** 469 2021-10-18 07:51 36 ***************** 470 2021-10-18 07:52 35 **************** ... ..( 6 skipped). .. **************** 477 2021-10-18 07:59 35 **************** 0 2021-10-18 08:00 36 ***************** ... ..( 15 skipped). .. ***************** 16 2021-10-18 08:16 36 ***************** 17 2021-10-18 08:17 35 **************** ... ..( 4 skipped). .. **************** 22 2021-10-18 08:22 35 **************** 23 2021-10-18 08:23 34 *************** ... ..( 8 skipped). .. *************** 32 2021-10-18 08:32 34 *************** 33 2021-10-18 08:33 33 ************** ... ..( 7 skipped). .. ************** 41 2021-10-18 08:41 33 ************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) 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 11 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 11 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 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 538929 Vendor specific