Files
bobbie-pkm/_Inbox/2026-05-15 0538 failing drive testing.md

12 KiB

category, type, title, created, date, tags
category type title created date tags
Journal
Log
failing drive testing 2026-05-15T05:38:44 2026-05-15

the Toshiba High-Performance P300 3TB HDD seems to be failing, want to see what's really wrong with it. Ran the following command (used -d sat as the drive is connected via usb)

smartctl -d sat -T permissive -a /dev/sdx

output

smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.2-2-pve] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba P300 (CMR)
Device Model:     TOSHIBA HDWD130
Serial Number:    3713VPPAS
LU WWN Device Id: 5 000039 fe6cfd8d8
Firmware Version: MX6OACF0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.5/5706
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri May 15 05:36:59 2026 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                (21504) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 359) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   140   140   054    Pre-fail  Offline      -       68
  3 Spin_Up_Time            0x0007   140   140   024    Pre-fail  Always       -       402 (Average 416)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1641
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       5
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   124   124   020    Pre-fail  Offline      -       33
  9 Power_On_Hours          0x0012   093   093   000    Old_age   Always       -       53349
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       231
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       1693
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       1693
194 Temperature_Celsius     0x0002   157   157   000    Old_age   Always       -       38 (Min/Max 4/58)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       5
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       56
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 4
        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 4 occurred at disk power-on lifetime: 53349 hours (2222 days + 21 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 51 68 50 5e 26 0c  Error: UNC 104 sectors at LBA = 0x0c265e50 = 203841104

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 b8 59 26 40 00      07:48:10.253  READ DMA EXT
  25 00 b0 08 52 26 40 00      07:48:10.242  READ DMA EXT
  25 00 00 08 4a 26 40 00      07:48:10.232  READ DMA EXT
  25 00 f0 18 42 26 40 00      07:48:10.220  READ DMA EXT
  25 00 00 18 3a 26 40 00      07:48:10.209  READ DMA EXT

Error 3 occurred at disk power-on lifetime: 53320 hours (2221 days + 16 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 51 48 10 77 92 0c  Error: UNC at LBA = 0x0c927710 = 210925328

  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 68 88 30 79 92 40 00   4d+18:00:26.852  READ FPDMA QUEUED
  60 90 e8 58 78 92 40 00   4d+18:00:26.852  READ FPDMA QUEUED
  60 e0 80 78 73 92 40 00   4d+18:00:26.852  READ FPDMA QUEUED
  60 70 70 98 72 92 40 00   4d+18:00:26.852  READ FPDMA QUEUED
  60 a8 e0 a8 71 92 40 00   4d+18:00:26.852  READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 53281 hours (2220 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 60 b8 57 7c 0c  Error: UNC at LBA = 0x0c7c57b8 = 209475512

  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 80 e0 b8 9d cf 40 00   3d+03:07:44.065  READ FPDMA QUEUED
  60 80 78 98 55 7c 40 00   3d+03:07:44.056  READ FPDMA QUEUED
  60 80 70 98 57 7c 40 00   3d+03:07:44.056  READ FPDMA QUEUED
  60 80 a0 18 57 7c 40 00   3d+03:07:44.056  READ FPDMA QUEUED
  60 80 98 18 55 7c 40 00   3d+03:07:44.056  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 53281 hours (2220 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 60 88 47 3c 0c  Error: UNC at LBA = 0x0c3c4788 = 205277064

  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 80 b0 68 47 3c 40 00   3d+02:59:20.357  READ FPDMA QUEUED
  60 80 78 e8 47 3c 40 00   3d+02:59:20.357  READ FPDMA QUEUED
  60 80 70 e8 46 3c 40 00   3d+02:59:20.357  READ FPDMA QUEUED
  60 80 68 68 48 3c 40 00   3d+02:59:20.342  READ FPDMA QUEUED
  60 80 60 e8 44 3c 40 00   3d+02:59:20.342  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    Completed: read failure       10%     53334         -
# 2  Extended offline    Aborted by host               90%     53328         -

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

[!NOTE] AI summary The Diagnosis: Physical Surface Failure

The drive is physically failing due to bad sectors, and it is hitting the end of its natural lifespan.

  1. Critical Lifespan Data (ID 9)
  • Power_On_Hours: 53,349 hours.
  • This drive has been running continuously for over 6 years (2,222 days). Consumer-grade mechanical hard drives typically show high failure rates after 3 to 5 years of continuous use.
  1. Sector Degradation Flags (ID 5 & ID 197)
  • Reallocated_Sector_Ct (5): The raw value is 5. The drive has already found 5 physically dead sectors and permanently swapped them out for clean backup sectors.
  • Current_Pending_Sector (197): The raw value is 56. This is the critical warning flag. The drive currently has 56 unstable sectors waiting to be reallocated. It cannot reliably read or write to these locations right now, which is causing your system slowdowns or software freezes.
  1. Active Read Errors (UNC Errors)

The log shows 4 major hardware error events at the very end of its runtime (at 53,349 hours).

  • Error Code UNC: This stands for Uncorrectable Error.
  • The internal Error Correction Code (ECC) inside the drive can no longer fix the corrupted bits coming off the platter surface.
  • The failures occurred while processing standard read requests (READ DMA EXT and READ FPDMA QUEUED), meaning any system or file trying to scan those areas will immediately hang or experience an I/O drop.

What is Wrong With It?

The magnetic substrate coating on the internal physical platters is physically degrading. The drive's actuator head is passing over these spots and encountering corrupted data it can no longer parse or repair.

Because the Current_Pending_Sector count is high (56) alongside active UNC errors, the damage is actively spreading. The drive will continue to drop off the system or fail reads whenever those specific sectors are accessed. It cannot be repaired or reliably used anymore.

further destructive testing, to force device to reallocate the bad sectors

badblocks -wsv /dev/sdx

check beck in in many hours time...