Question GSmartControl HDD error

[PPorri]

I am having trouble with my main HDD. My current pending sector count is 1. Additionally, I am receiving continuous errors of similar type with "Uncorrectable error in data" and now for the first time "Media is write protected". All are at LBA = 0x 152ab4240 = 5681922624. Furthermore, the errors have come in a continuous interval.

Here is the log:


smartctl 7.3 2022-02-28 r5338 [x86_64-w64-mingw32-w10-21H2] (sf-7.3-1)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD30EFRX-68EUZN0
Serial Number:
LU WWN Device Id: 5 0014ee 2b7c437a1
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 7.3/5319
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: Tue Oct 25 22:15:15 2022 FLEST
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: Enabled
DSN feature is: Unavailable
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: (38400) 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: ( 385) 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 - 15
3 Spin_Up_Time POS--K 182 180 021 - 5891
4 Start_Stop_Count -O--CK 087 087 000 - 13870
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 072 072 000 - 20758
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 096 096 000 - 4820
192 Power-Off_Retract_Count -O--CK 200 200 000 - 264
193 Load_Cycle_Count -O--CK 182 182 000 - 56718
194 Temperature_Celsius -O---K 121 108 000 - 29
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 1
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-- 100 253 000 - 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 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: 15
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🇲🇲SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 15 [14] occurred at disk power-on lifetime: 20674 hours (861 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: WP at LBA = 0x152ab4240 = 5681922624

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 00 88 00 80 00 00 00 5e 26 68 40 00 05:04:14.078 WRITE FPDMA QUEUED
60 01 00 00 78 00 01 52 ab 43 08 40 00 05:04:14.078 READ FPDMA QUEUED
60 01 00 00 70 00 01 52 ab 42 08 40 00 05:04:14.078 READ FPDMA QUEUED
60 01 00 00 68 00 01 52 ab 41 08 40 00 05:04:14.077 READ FPDMA QUEUED
60 01 00 00 60 00 01 52 ab 40 08 40 00 05:04:14.077 READ FPDMA QUEUED

Error 14 [13] occurred at disk power-on lifetime: 20674 hours (861 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 60 00 01 52 ab 43 08 40 00 05:04:05.591 READ FPDMA QUEUED
60 01 00 00 58 00 01 52 ab 42 08 40 00 05:04:05.591 READ FPDMA QUEUED
60 01 00 00 50 00 01 52 ab 41 08 40 00 05:04:05.591 READ FPDMA QUEUED
60 01 00 00 48 00 01 52 ab 40 08 40 00 05:04:05.591 READ FPDMA QUEUED
60 01 00 00 40 00 01 52 ab 3f 08 40 00 05:04:05.591 READ FPDMA QUEUED

Error 13 [12] occurred at disk power-on lifetime: 20674 hours (861 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 a0 00 01 52 ab 43 08 40 00 05:03:28.642 READ FPDMA QUEUED
60 01 00 00 98 00 01 52 ab 42 08 40 00 05:03:28.642 READ FPDMA QUEUED
60 01 00 00 90 00 01 52 ab 41 08 40 00 05:03:28.642 READ FPDMA QUEUED
60 01 00 00 88 00 01 52 ab 40 08 40 00 05:03:28.642 READ FPDMA QUEUED
60 01 00 00 80 00 01 52 ab 3f 08 40 00 05:03:28.642 READ FPDMA QUEUED

Error 12 [11] occurred at disk power-on lifetime: 20674 hours (861 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 70 00 01 52 ab 43 08 40 00 04:52:01.501 READ FPDMA QUEUED
60 01 00 00 68 00 01 52 ab 42 08 40 00 04:52:01.501 READ FPDMA QUEUED
60 01 00 00 60 00 01 52 ab 41 08 40 00 04:52:01.501 READ FPDMA QUEUED
60 01 00 00 58 00 01 52 ab 40 08 40 00 04:52:01.501 READ FPDMA QUEUED
60 01 00 00 50 00 01 52 ab 3f 08 40 00 04:52:01.501 READ FPDMA QUEUED

Error 11 [10] occurred at disk power-on lifetime: 20674 hours (861 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 b8 00 01 52 ab 43 08 40 00 04:37:38.605 READ FPDMA QUEUED
60 01 00 00 b0 00 01 52 ab 42 08 40 00 04:37:38.605 READ FPDMA QUEUED
60 01 00 00 a8 00 01 52 ab 41 08 40 00 04:37:38.605 READ FPDMA QUEUED
60 01 00 00 a0 00 01 52 ab 40 08 40 00 04:37:38.605 READ FPDMA QUEUED
60 01 00 00 98 00 01 52 ab 3f 08 40 00 04:37:38.605 READ FPDMA QUEUED

Error 10 [9] occurred at disk power-on lifetime: 20673 hours (861 days + 9 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 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 08 00 01 52 ab 43 08 40 00 04:20:28.622 READ FPDMA QUEUED
60 01 00 00 f8 00 01 52 ab 42 08 40 00 04:20:28.622 READ FPDMA QUEUED
60 01 00 00 f0 00 01 52 ab 41 08 40 00 04:20:28.622 READ FPDMA QUEUED
60 01 00 00 e8 00 01 52 ab 40 08 40 00 04:20:28.622 READ FPDMA QUEUED
60 01 00 00 e0 00 01 52 ab 3f 08 40 00 04:20:28.622 READ FPDMA QUEUED

Error 9 [8] occurred at disk power-on lifetime: 20673 hours (861 days + 9 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 01 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 58 00 01 52 ab 43 08 40 00 04:14:20.658 READ FPDMA QUEUED
60 01 00 00 50 00 01 52 ab 42 08 40 00 04:14:20.658 READ FPDMA QUEUED
60 01 00 00 48 00 01 52 ab 41 08 40 00 04:14:20.658 READ FPDMA QUEUED
60 01 00 00 40 00 01 52 ab 40 08 40 00 04:14:20.658 READ FPDMA QUEUED
60 01 00 00 38 00 01 52 ab 3f 08 40 00 04:14:20.658 READ FPDMA QUEUED

Error 8 [7] occurred at disk power-on lifetime: 20595 hours (858 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 40 00 01 52 ab 43 08 40 00 04:10:48.448 READ FPDMA QUEUED
60 01 00 00 38 00 01 52 ab 42 08 40 00 04:10:48.448 READ FPDMA QUEUED
60 01 00 00 30 00 01 52 ab 41 08 40 00 04:10:48.448 READ FPDMA QUEUED
60 01 00 00 28 00 01 52 ab 40 08 40 00 04:10:48.448 READ FPDMA QUEUED
60 01 00 00 20 00 01 52 ab 3f 08 40 00 04:10:48.448 READ FPDMA QUEUED

Error 7 [6] occurred at disk power-on lifetime: 20595 hours (858 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 38 00 01 52 ab 43 08 40 00 04:10:40.923 READ FPDMA QUEUED
60 01 00 00 30 00 01 52 ab 42 08 40 00 04:10:40.923 READ FPDMA QUEUED
60 01 00 00 28 00 01 52 ab 41 08 40 00 04:10:40.923 READ FPDMA QUEUED
60 01 00 00 20 00 01 52 ab 40 08 40 00 04:10:40.923 READ FPDMA QUEUED
60 01 00 00 18 00 01 52 ab 3f 08 40 00 04:10:40.923 READ FPDMA QUEUED

Error 6 [5] occurred at disk power-on lifetime: 20595 hours (858 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 -- 51 00 00 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 a0 00 01 52 ab 43 08 40 00 04:04:30.216 READ FPDMA QUEUED
60 01 00 00 98 00 01 52 ab 42 08 40 00 04:04:30.216 READ FPDMA QUEUED
60 01 00 00 90 00 01 52 ab 41 08 40 00 04:04:30.216 READ FPDMA QUEUED
60 01 00 00 88 00 01 52 ab 40 08 40 00 04:04:30.216 READ FPDMA QUEUED
60 01 00 00 80 00 01 52 ab 3f 08 40 00 04:04:30.216 READ FPDMA QUEUED

Error 5 [4] occurred at disk power-on lifetime: 20595 hours (858 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 -- 51 00 01 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 60 00 01 52 ab 43 08 40 00 04:03:22.789 READ FPDMA QUEUED
60 01 00 00 58 00 01 52 ab 42 08 40 00 04:03:22.789 READ FPDMA QUEUED
60 01 00 00 50 00 01 52 ab 41 08 40 00 04:03:22.789 READ FPDMA QUEUED
60 01 00 00 48 00 01 52 ab 40 08 40 00 04:03:22.789 READ FPDMA QUEUED
60 01 00 00 40 00 01 52 ab 3f 08 40 00 04:03:22.789 READ FPDMA QUEUED

Error 4 [3] occurred at disk power-on lifetime: 20585 hours (857 days + 17 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 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 30 00 01 52 ab 43 08 40 00 07:01:59.863 READ FPDMA QUEUED
60 01 00 00 28 00 01 52 ab 42 08 40 00 07:01:59.863 READ FPDMA QUEUED
60 01 00 00 20 00 01 52 ab 41 08 40 00 07:01:59.863 READ FPDMA QUEUED
60 01 00 00 18 00 01 52 ab 40 08 40 00 07:01:59.863 READ FPDMA QUEUED
60 01 00 00 10 00 01 52 ab 3f 08 40 00 07:01:59.862 READ FPDMA QUEUED

Error 3 [2] occurred at disk power-on lifetime: 20585 hours (857 days + 17 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 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 d0 00 01 52 ab 43 08 40 00 07:01:52.660 READ FPDMA QUEUED
60 01 00 00 c8 00 01 52 ab 42 08 40 00 07:01:52.660 READ FPDMA QUEUED
60 01 00 00 c0 00 01 52 ab 41 08 40 00 07:01:52.660 READ FPDMA QUEUED
60 01 00 00 b8 00 01 52 ab 40 08 40 00 07:01:52.659 READ FPDMA QUEUED
60 01 00 00 b0 00 01 52 ab 3f 08 40 00 07:01:52.659 READ FPDMA QUEUED

Error 2 [1] occurred at disk power-on lifetime: 20585 hours (857 days + 17 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 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 38 00 01 52 ab 43 08 40 00 06:51:10.698 READ FPDMA QUEUED
60 01 00 00 30 00 01 52 ab 42 08 40 00 06:51:10.698 READ FPDMA QUEUED
60 01 00 00 28 00 01 52 ab 41 08 40 00 06:51:10.698 READ FPDMA QUEUED
60 01 00 00 20 00 01 52 ab 40 08 40 00 06:51:10.698 READ FPDMA QUEUED
60 01 00 00 18 00 01 52 ab 3f 08 40 00 06:51:10.698 READ FPDMA QUEUED

Error 1 [0] occurred at disk power-on lifetime: 20585 hours (857 days + 17 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 01 00 01 52 ab 42 40 40 00 Error: UNC at LBA = 0x152ab4240 = 5681922624

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 80 00 60 00 01 52 ab 43 08 40 00 06:35:25.520 READ FPDMA QUEUED
60 01 00 00 58 00 01 52 ab 42 08 40 00 06:35:25.520 READ FPDMA QUEUED
60 01 00 00 50 00 01 52 ab 41 08 40 00 06:35:25.520 READ FPDMA QUEUED
60 01 00 00 48 00 01 52 ab 40 08 40 00 06:35:25.520 READ FPDMA QUEUED
60 01 00 00 40 00 01 52 ab 3f 08 40 00 06:35:25.519 READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]

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: 29 Celsius
Power Cycle Min/Max Temperature: 28/29 Celsius
Lifetime Min/Max Temperature: 2/42 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 (12)

Index Estimated Time Temperature Celsius
13 2022-10-25 14:18 26 ***
... ..( 2 skipped). .. ***
16 2022-10-25 14:21 26 ***
17 2022-10-25 14:22 27 ****
... ..( 20 skipped). .. ****
38 2022-10-25 14:43 27 ****
39 2022-10-25 14:44 28 *
... ..( 81 skipped). .. *
121 2022-10-25 16:06 28 *
122 2022-10-25 16:07 29 **
... ..( 17 skipped). .. **
140 2022-10-25 16:25 29 **
141 2022-10-25 16:26 ? -
142 2022-10-25 16:27 22 ***
143 2022-10-25 16:28 23 ****
144 2022-10-25 16:29 23 ****
145 2022-10-25 16:30 24 *
... ..( 4 skipped). .. *
150 2022-10-25 16:35 24 *
151 2022-10-25 16:36 25 **
152 2022-10-25 16:37 25 **
153 2022-10-25 16:38 25 **
154 2022-10-25 16:39 26 ***
... ..( 3 skipped). .. ***
158 2022-10-25 16:43 26 ***
159 2022-10-25 16:44 27 ****
... ..( 5 skipped). .. ****
165 2022-10-25 16:50 27 ****
166 2022-10-25 16:51 28 *
... ..( 15 skipped). .. *
182 2022-10-25 17:07 28 *
183 2022-10-25 17:08 29 **
... ..( 15 skipped). .. **
199 2022-10-25 17:24 29 **
200 2022-10-25 17:25 30 ***
... ..( 45 skipped). .. ***
246 2022-10-25 18:11 30 ***
247 2022-10-25 18:12 ? -
248 2022-10-25 18:13 23 ****
249 2022-10-25 18:14 ? -
250 2022-10-25 18:15 23 ****
251 2022-10-25 18:16 23 ****
252 2022-10-25 18:17 24 *
... ..( 2 skipped). .. *
255 2022-10-25 18:20 24 *
256 2022-10-25 18:21 25 **
257 2022-10-25 18:22 25 **
258 2022-10-25 18:23 25 **
259 2022-10-25 18:24 26 ***
260 2022-10-25 18:25 26 ***
261 2022-10-25 18:26 26 ***
262 2022-10-25 18:27 27 ****
... ..( 5 skipped). .. ****
268 2022-10-25 18:33 27 ****
269 2022-10-25 18:34 28 *
... ..( 23 skipped). .. *
293 2022-10-25 18:58 28 *
294 2022-10-25 18:59 29 **
... ..( 11 skipped). .. **
306 2022-10-25 19:11 29 **
307 2022-10-25 19:12 ? -
308 2022-10-25 19:13 23 ****
309 2022-10-25 19:14 24 *
... ..( 2 skipped). .. *
312 2022-10-25 19:17 24 *
313 2022-10-25 19:18 25 **
... ..( 2 skipped). .. **
316 2022-10-25 19:21 25 **
317 2022-10-25 19:22 26 ***
... ..( 3 skipped). .. ***
321 2022-10-25 19:26 26 ***
322 2022-10-25 19:27 27 ****
... ..( 32 skipped). .. ****
355 2022-10-25 20:00 27 ****
356 2022-10-25 20:01 28 *
... ..( 70 skipped). .. *
427 2022-10-25 21:12 28 *
428 2022-10-25 21:13 ? -
429 2022-10-25 21:14 28 *
... ..( 34 skipped). .. *
464 2022-10-25 21:49 28 *
465 2022-10-25 21:50 29 **
... ..( 18 skipped). .. **
6 2022-10-25 22:09 29 **
7 2022-10-25 22:10 24 *
8 2022-10-25 22:11 25 **
... ..( 2 skipped). .. **
11 2022-10-25 22:14 25 **
12 2022-10-25 22:15 26 ***

SCT Error Recovery Control:
Read: 70 (7,0 seconds)
Write: 70 (7,0 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 132 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 2 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 3328 Vendor specific

 

[Aeacus]

What WD Dashboard says?
Link: https://support.wdc.com/downloads.aspx?p=279

The WD drive you have, isn't meant as OS drive, instead it is meant as NAS drive. Due to that, it may have shorter lifespan, when used outside of the designed scope. Still, hardware fails on a daily basis and by the looks of it, your WD HDD is on it's way out. Time to look towards new drive, preferably SSD, since SSDs are far more reliable and faster as well.

 

[PPorri]

What WD Dashboard says?
Link: https://support.wdc.com/downloads.aspx?p=279

The WD drive you have, isn't meant as OS drive, instead it is meant as NAS drive. Due to that, it may have shorter lifespan, when used outside of the designed scope. Still, hardware fails on a daily basis and by the looks of it, your WD HDD is on it's way out. Time to look towards new drive, preferably SSD, since SSDs are far more reliable and faster as well.

WD Dashboard shows it to be healthy based on S.M.A.R.T stats. What setting should I look into? I am not using the drive as an OS drive. OS is stored on my SSD and this drive functions as a storage drive for music, movies etc. Though, it is not in an NAS, but in my desktop.

 

[Aeacus]

There is a tool, named Data Lifeguard Diagnostic, that WD developed to monitor and check the health of their HDDs,
link: https://support.wdc.com/downloads.aspx?p=3&lang=en

Which i also used when i had WD HDDs in use. Since then, i've phased out all HDDs in my PCs and i'm only running SSDs (both SATA and NVMe).
At 1st, i was going to suggest Data Lifeguard Diagnostic for you, but as you can see from the link included, WD has abandoned this software and replaced it with WD Dashboard instead.

As of what to check from WD Dashboard, HDD health and if you can, run benchmark test on HDD. Data Lifeguard Diagnostic had HDD test suite built-in. I don't know if WD Dashboard also has HDD test suite in it nor i can not check it, since i don't have any WD HDDs in my systems anymore.

To keep your HDD healthy, always keep at least 20% of HDDs total capacity free. E.g for 1TB drive, that translates into 186GB (since 1TB drive actually has space for 931GB in total).

Also, use disk defragmentation tool about once a month to keep your files on a HDD in nice and proper order. Disk defrag also boosts the HDD read/write speeds at some extent if you have a lot of fragmented files on a HDD.

I'm was using MyDefrag to keep my WD Blue 1TB HDDs healthy,
link: http://www.mydefrag.net/

MyDefrag description

MyDefrag is a disk defragmenter and optimizer, that is a maintenance utility to make your hard disk faster. It is freeware, no time limit, fully functional, no advertisements. Fast, low overhead, with many optimization strategies, can handle floppies, USB disks, memory sticks, and anything else that looks like a disk to Windows. Included are a set of easy to use scripts for end-users, a scripting engine for demanding users, a screensaver, and a combined Windows plus command line version that can be scheduled by the Windows task scheduler or for use from administrator scripts.

MyDefrag is extremely solid because it is based on the standard defragmentation API by Microsoft, a system library that is included in Windows 2000, 2003, XP, Vista, 2008, and Win7. Most defragmenters are based on this API, including the free defragmenter that comes with Windows and many commercial defragmenters. Basically all MyDefrag does is send "move this file to that location" commands to the API. The API is part of the operating system and can safely move almost any file on the disk, without risk and while the computer is in full use.

What is "disk fragmentation"?
Imagine a book split into several parts, some pages are over here, other pages in another room on another floor altogether. You will have to walk a lot when you need to read the book. It may sound silly, but this is exactly what happens to files on your harddisk. Defragmentation will put all the parts (fragments) back together, making your computer a lot faster.

What is "disk optimization"?
Imagine a big library with lot's of books, spread out all over the building and not sorted whatsoever. There is an index telling you exactly where every book is, but you will have to walk a lot when you need several books. This is exactly what happens on your harddisk, the files that belong to an application can be all over the place, anywhere on the harddisk. Optimization will bring all the files together in one place, leaving the rest of the harddisk empty, and will sort the files, for example alphabetically.

So, doing HDD defrag often helps to keep the drive in working order and it can mitigate file corruption to some extent. Or the very least, shows you how many bad sectors you have on your drive.

 

[fzabkar]

You could use DMDE to determine which file, if any, owns that particular sector. Your next step would depend on what type of file it is.

https://dmde.com/

 

[PPorri]

You could use DMDE to determine which file, if any, owns that particular sector. Your next step would depend on what type of file it is.

https://dmde.com/

I downloaded DMDE but am little puzzled on how to input the value into the program.

 

[PPorri]

There is a tool, named Data Lifeguard Diagnostic, that WD developed to monitor and check the health of their HDDs,
link: https://support.wdc.com/downloads.aspx?p=3&lang=en

Which i also used when i had WD HDDs in use. Since then, i've phased out all HDDs in my PCs and i'm only running SSDs (both SATA and NVMe).
At 1st, i was going to suggest Data Lifeguard Diagnostic for you, but as you can see from the link included, WD has abandoned this software and replaced it with WD Dashboard instead.

As of what to check from WD Dashboard, HDD health and if you can, run benchmark test on HDD. Data Lifeguard Diagnostic had HDD test suite built-in. I don't know if WD Dashboard also has HDD test suite in it nor i can not check it, since i don't have any WD HDDs in my systems anymore.

To keep your HDD healthy, always keep at least 20% of HDDs total capacity free. E.g for 1TB drive, that translates into 186GB (since 1TB drive actually has space for 931GB in total).

Also, use disk defragmentation tool about once a month to keep your files on a HDD in nice and proper order. Disk defrag also boosts the HDD read/write speeds at some extent if you have a lot of fragmented files on a HDD.

I'm was using MyDefrag to keep my WD Blue 1TB HDDs healthy,
link: http://www.mydefrag.net/



So, doing HDD defrag often helps to keep the drive in working order and it can mitigate file corruption to some extent. Or the very least, shows you how many bad sectors you have on your drive.

WD Dashboard seems to have short and extended SMART tests. I could try to run the extended one.

 

[fzabkar]

DMDE is probably the least user friendly of all data recovery software. :-(

This is how I got there:

Launch DMDE and select your physical disc.

D-click your desired NTFS volume. You should now see your file/folder tree.

Select Editor -> Physical Sectors and specify your desired sector.

Focus Sector = 5681922624​

First Sector = 5681922624​

Number of Sectors = 1​

Offset (Bytes) = 0​

OK​

​

You should now see the hexadecimal content of this sector in the bottom RH pane.

Click the Up Arrow to bring the pane into focus.

Select Editor -> File Data

You should now see a dialogue box which is scanning the MFT records and looking for the file which corresponds to your sector. When it finishes, you will see the file name at the top of your tab.

If DMDE is unable to read this sector, choose the sector immediately before it (5681922623) or the next physical sector (5681922632).

 

[PPorri]

DMDE is probably the least user friendly of all data recovery software. :-(

This is how I got there:

Launch DMDE and select your physical disc.

D-click your desired NTFS volume. You should now see your file/folder tree.

Select Editor -> Physical Sectors and specify your desired sector.

Focus Sector = 5681922624​

First Sector = 5681922624​

Number of Sectors = 1​

Offset (Bytes) = 0​

OK​

​

You should now see the hexadecimal content of this sector in the bottom RH pane.

Click the Up Arrow to bring the pane into focus.

Select Editor -> File Data

You should now see a dialogue box which is scanning the MFT records and looking for the file which corresponds to your sector. When it finishes, you will see the file name at the top of your tab.

If DMDE is unable to read this sector, choose the sector immediately before it (5681922623) or the next physical sector (5681922632).

Thank you very much for a detailed guide! I got to the physical sectors and pressed ok. After a short while, I received "WinError 23. Data error (cyclic redundancy check", with an alert of informing the risks of further working.

 

[fzabkar]

Some additional suggestions ...

https://superuser.com/questions/1266135/how-do-i-find-if-there-are-files-at-a-specific-bad-sector

Extract "nfi.exe" from http://www.jumpjet.info/Application-Software/Windows/tools/oem_support_tools/oem3sr2.zip

Convert your absolute sector number (5681922624) to a relative (logical or volume) sector number. For example, if your partition's drive letter is C:, then determine the starting LBA for C: from DMDE's Partitions window. Let's assume this is LBA 2048.

Therefore, the sector number relative to the start of the volume is 5681922624 - 2048 = 5681920576.

In a CMD window, type ..

nfi.exe C: 5681920576​

​

Here is an example for relative sector 400000:

C:\Software\Microsoft\Win2000_OEM_Support_Tools\nfi C: 400000

NTFS File Sector Information Utility.
Copyright (C) Microsoft Corporation 1999. All rights reserved.


***Logical sector 400000 (0x61a80) on drive C is in file number 220559.
\Windows\Fonts\EmojiOneColor-SVGinOT.ttf
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
        logical sectors 393624-405727 (0x60198-0x630df)