December 16, 20223 yr Hi Guys, I have been doing some research because my drive has 8 pending sectors. In previous topics I read that this is a serious problem. In the topics I read before this was confirmed by a failing smart test. In my case the test passed so I am a bit unsure what to do and would love to hear your input. I have attached the full smart log after the test. Some of the highlights: Disk stats ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance P-S--- 132 132 054 - 96 3 Spin_Up_Time POS--- 157 157 024 - 421 (Average 419) 4 Start_Stop_Count -O--C- 098 098 000 - 9519 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate PO-R-- 100 100 067 - 0 8 Seek_Time_Performance P-S--- 128 128 020 - 18 9 Power_On_Hours -O--C- 095 095 000 - 41444 10 Spin_Retry_Count PO--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 172 22 Helium_Level PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 076 076 000 - 28890 193 Load_Cycle_Count -O--C- 076 076 000 - 28890 194 Temperature_Celsius -O---- 200 200 000 - 30 (Min/Max 19/53) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 8 198 Offline_Uncorrectable ---R-- 100 100 000 - 4 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 91 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 172 --- Lifetime Power-On Resets 0x01 0x010 4 41444 --- Power-on Hours 0x01 0x018 6 1287713147715 --- Logical Sectors Written 0x01 0x020 6 5986104774 --- Number of Write Commands 0x01 0x028 6 836681078544 --- Logical Sectors Read 0x01 0x030 6 2049151681 --- Number of Read Commands 0x01 0x038 6 149198993100 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 26672 --- Spindle Motor Power-on Hours 0x03 0x010 4 26672 --- Head Flying Hours 0x03 0x018 4 28890 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 5 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 2 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 93 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 30 --- Current Temperature 0x05 0x010 1 31 N-- Average Short Term Temperature 0x05 0x018 1 30 N-- Average Long Term Temperature 0x05 0x020 1 53 --- Highest Temperature 0x05 0x028 1 19 --- Lowest Temperature 0x05 0x030 1 49 N-- Highest Average Short Term Temperature 0x05 0x038 1 22 N-- Lowest Average Short Term Temperature 0x05 0x040 1 45 N-- Highest Average Long Term Temperature 0x05 0x048 1 25 N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 1 --- Number of Hardware Resets 0x06 0x010 4 557 --- Number of ASR Events 0x06 0x018 4 91 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == |||_ C monitored condition met ||__ D supports DSN |___ N normalized value SMART result SMART overall-health self-assessment test result: PASSED 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% 41443 - # 2 Short offline Completed without error 00% 41422 - Previously logged errors (not during SMART test reported) Error 93 [0] occurred at disk power-on lifetime: 40714 hours (1696 days + 10 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 00 00 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0 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 01 00 00 00 00 00 05 89 76 28 40 00 41d+13:33:54.527 READ FPDMA QUEUED 60 01 00 00 08 00 00 05 89 77 28 40 00 41d+13:33:52.077 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 75 28 40 00 41d+13:33:52.076 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 74 28 40 00 41d+13:33:52.076 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 73 28 40 00 41d+13:33:52.075 READ FPDMA QUEUED Error 92 [3] occurred at disk power-on lifetime: 40714 hours (1696 days + 10 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 00 00 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0 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 01 00 00 00 00 00 05 89 67 28 40 00 41d+13:33:51.852 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 66 28 40 00 41d+13:33:49.445 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 65 28 40 00 41d+13:33:49.444 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 64 28 40 00 41d+13:33:49.444 READ FPDMA QUEUED 60 01 00 00 00 00 00 05 89 63 28 40 00 41d+13:33:49.443 READ FPDMA QUEUED Error 91 [2] occurred at disk power-on lifetime: 26542 hours (1105 days + 22 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 -- -- -- == -- == == == -- -- -- -- -- 84 -- 41 00 00 00 00 00 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 03 f8 00 00 00 02 80 02 8d 20 40 00 00:06:31.627 WRITE FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 00 00 00:06:31.381 SET FEATURES [Enable SATA feature] ef 00 02 00 00 00 00 00 00 00 00 00 00 00:06:31.378 SET FEATURES [Enable write cache] ef 00 aa 00 00 00 00 00 00 00 00 00 00 00:06:31.375 SET FEATURES [Enable read look-ahead] ef 00 03 00 46 00 00 00 00 00 00 00 00 00:06:31.372 SET FEATURES [Set transfer mode] Error 90 [1] occurred at disk power-on lifetime: 26542 hours (1105 days + 22 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 -- -- -- == -- == == == -- -- -- -- -- 84 -- 41 00 00 00 00 00 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 03 f8 00 00 00 02 80 02 8d 20 40 00 00:06:31.128 WRITE FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 00 00 00:06:30.881 SET FEATURES [Enable SATA feature] ef 00 02 00 00 00 00 00 00 00 00 00 00 00:06:30.878 SET FEATURES [Enable write cache] ef 00 aa 00 00 00 00 00 00 00 00 00 00 00:06:30.876 SET FEATURES [Enable read look-ahead] ef 00 03 00 46 00 00 00 00 00 00 00 00 00:06:30.873 SET FEATURES [Set transfer mode] WDC_WD121KRYZ-01W0RB0-20221215-1933.txt Edited December 16, 20223 yr by imthesandman typo in title
December 16, 20223 yr Community Expert Solution This sometimes happens, specially with WD drives, they are "false positives", a full disk write should get rid of them if you want.
December 16, 20223 yr Author 5 minutes ago, JorgeB said: This sometimes happens, specially with WD drives, they are "false positives", a full disk write should get rid of them if you want. Thanks I will do exactly that!
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.