Smartctl HDD errors

Node Operators
,
1

Good afternoon,

Finally got some errors on my refurbished HDD which I bought less then two years ago. Any suggestions what I should do? If I ask the AI they say I should replace

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.0-124-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST16000NM000J-2TW103
Serial Number:    ZR5DGKVR
LU WWN Device Id: 5 000c50 074450bbe
Firmware Version: SN04
User Capacity:    16,000,900,661,248 bytes [16.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database 7.3/5528
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jun 21 10:41:35 2026 UTC
SMART support is: Available - device has SMART capability.
SMART support is: 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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (  575) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        (1439) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x70bd) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   074   064   044    Pre-fail  Always       -       25743360
  3 Spin_Up_Time            0x0003   089   089   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       34
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   086   060   045    Pre-fail  Always       -       373237144
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14809
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       34
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   053   000    Old_age   Always       -       38 (Min/Max 33/43)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       18
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       767
194 Temperature_Celsius     0x0022   038   047   000    Old_age   Always       -       38 (0 20 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       2
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0023   100   100   001    Pre-fail  Always       -       0
240 Head_Flying_Hours       0x0000   100   100   000    Old_age   Offline      -       14801 (96 10 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       77111919176
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       96254862021

SMART Error Log Version: 1
ATA Error Count: 135 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
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 135 occurred at disk power-on lifetime: 14792 hours (616 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  43d+07:19:04.933  READ FPDMA QUEUED
  61 00 08 ff ff ff 4f 00  43d+07:19:04.933  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:19:04.933  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:19:04.933  READ FPDMA QUEUED
  60 00 10 ff ff ff 4f 00  43d+07:19:04.933  READ FPDMA QUEUED

Error 134 occurred at disk power-on lifetime: 14792 hours (616 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 28 ff ff ff 4f 00  43d+07:19:02.373  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:19:02.373  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00  43d+07:19:02.373  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:19:02.373  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:19:02.373  READ FPDMA QUEUED

Error 133 occurred at disk power-on lifetime: 14792 hours (616 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 90 50 8c 41 00  43d+07:18:59.823  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:59.823  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:59.823  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:59.823  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:59.823  READ FPDMA QUEUED

Error 132 occurred at disk power-on lifetime: 14792 hours (616 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: WP at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 ff ff ff 4f 00  43d+07:18:57.347  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:57.347  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:57.347  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:57.347  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:57.347  READ FPDMA QUEUED

Error 131 occurred at disk power-on lifetime: 14792 hours (616 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  43d+07:18:56.972  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:55.853  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:55.706  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:55.617  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  43d+07:18:54.856  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      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.

The above only provides legacy SMART information - try 'smartctl -x' for more
2

If you’re only using it for Storj… just keep running it until it fails. Fsck/scrub as needed.

If you have important data on it… then as long as you already have automated backups… you can do the same thing.

Often damaged drives can still work for years: and a good backup system keeps you safe.

3

Based on just the data you’ve posted, this seems to be just a bad sector. Observe Reallocated_Sector_Ct. With some luck, the drive will reallocate it somewhere else (you’ll see Reallocated_Sector_Ct change) and forget about it. But yeah, don’t trust this drive with important data at this point.

If this drive is only used for Storj, I wouldn’t even bother trying to clear this error.

4

Did you mess with the cables recently or have a power cut?

5

Had some thermal issues one hdd was above 50 Degree maybe it got a hit when I changed the layout for better airflow. Now I have a smartctl exporter installed and trying to track issues. The drive is only for Storj just hope it will last some years to pay out.

6

to expand on this idea, look at the raw values.

Current_Pending_Sector shows a “2”. A pending sector is one that had a failed read, but it can only be confirmed if new data is attempted to be written to it. it could actually 'clear up".

If this was a drive you were storing important data on, I would recommend attempting to write to every sector (normally I just do a slow format on a new drive… maybe badblocks can do it non destrictively). After the pending sector is written to, it will either “clear up” or it will be confirmed as a reallocated_sector.

If you’re just using it for storj I would leave the drive as is. if it starts racking up more sectors maybe prepare to migrate off the drive.