I was asked to replace a malfunctioning hard drive, which was used as recording device in a TV setup.
(2.5" HDD, simple USB interface, in a two part plastic casing)
As it has a USB type A cable out, it was simple to just plug it in on the Ubuntu laptop.
Added Note: The USB connection seemingly worked perfectly, the device appears to have problems with the storage media only. Therefore it was possible to see...
The largest files present appears to be 200MB chunks of encrypted stream data. The remainder of the files are most likely metadata of various kind; I won't even try to decipher any of it, the recordings are a random set of TV-programs and covers 7.5% of the space.
"Disks" says:
- Model: TOSHIBA MQ01ABD050V -63 (AX0N1Q)
- Partitioning: 500 GB, Master Boot Record, 17MB Free, then a 500GB ext4 v1.0 partition.
- Assessment: Disk is OK, 16376 bad sectors (29° C / 84° F)
Is there more to interpret out from this, than just "multiple escalating read error"?
I suspect the "driving factor" for the breakage is the small (even TINY) fully enclosed casing with no venting; causing heat problems.
It might also have been exposed to shock, as the device was standing beside a TV for two(?) years. When cleaning dust, ooops! Dropped it.
$ sudo smartctl -a /dev/sdb
[sudo] password for hannu:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.13.0-37-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA MQ01ABD050V -63
Serial Number: 885YC2J1TF6G
LU WWN Device Id: 5 000039 8b43822ba
Firmware Version: AX0N1Q
User Capacity: 500 107 862 016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Wed Mar 30 19:53:04 2022 CEST
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: (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: ( 120) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 115) 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 084 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1125
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 200
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 10288
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 033 033 000 Old_age Always - 26898
10 Spin_Retry_Count 0x0033 103 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 200
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 185
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 200
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 27 (Min/Max 22/58)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 854
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 6088
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 033 033 000 Old_age Always - 26898
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 178
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 467 (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 467 occurred at disk power-on lifetime: 26805 hours (1116 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 b8 f0 73 13 4d Error: UNC 184 sectors at LBA = 0x0d1373f0 = 219378672
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 d5 08 a0 73 13 40 00 06:40:51.442 READ DMA EXT
25 d5 c0 e8 72 13 40 00 06:40:51.333 READ DMA EXT
25 d5 98 58 71 13 40 00 06:40:51.137 READ DMA EXT
25 d5 88 d8 6f 13 40 00 06:40:50.928 READ DMA EXT
25 d5 d0 10 6e 13 40 00 06:40:50.728 READ DMA EXT
Error 466 occurred at disk power-on lifetime: 26805 hours (1116 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 18 e0 74 13 4d Error: UNC 24 sectors at LBA = 0x0d1374e0 = 219378912
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 d5 18 e0 74 13 40 00 06:38:34.673 READ DMA EXT
25 d5 48 a0 73 13 40 00 06:38:31.303 READ DMA EXT
25 d5 c0 e8 72 13 40 00 06:38:31.292 READ DMA EXT
25 d5 40 b0 71 13 40 00 06:38:31.083 READ DMA EXT
25 d5 30 88 6f 13 40 00 06:38:30.890 READ DMA EXT
Error 465 occurred at disk power-on lifetime: 26805 hours (1116 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 f8 f0 73 13 4d Error: UNC 248 sectors at LBA = 0x0d1373f0 = 219378672
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 d5 48 a0 73 13 40 00 06:38:31.303 READ DMA EXT
25 d5 c0 e8 72 13 40 00 06:38:31.292 READ DMA EXT
25 d5 40 b0 71 13 40 00 06:38:31.083 READ DMA EXT
25 d5 30 88 6f 13 40 00 06:38:30.890 READ DMA EXT
25 d5 b8 d8 6d 13 40 00 06:38:30.688 READ DMA EXT
Error 464 occurred at disk power-on lifetime: 26798 hours (1116 days + 14 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 06 c2 76 06 40 Error: UNC 6 sectors at LBA = 0x000676c2 = 423618
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 06 c2 76 06 40 00 00:00:20.982 READ DMA EXT
25 00 01 c1 76 06 40 00 00:00:17.605 READ DMA EXT
25 00 01 c0 76 06 40 00 00:00:14.221 READ DMA EXT
25 00 20 c0 76 06 40 00 00:00:10.840 READ DMA EXT
25 00 08 b8 76 06 40 00 00:00:10.839 READ DMA EXT
Error 463 occurred at disk power-on lifetime: 26798 hours (1116 days + 14 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 01 c1 76 06 40 Error: UNC 1 sectors at LBA = 0x000676c1 = 423617
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 01 c1 76 06 40 00 00:00:17.605 READ DMA EXT
25 00 01 c0 76 06 40 00 00:00:14.221 READ DMA EXT
25 00 20 c0 76 06 40 00 00:00:10.840 READ DMA EXT
25 00 08 b8 76 06 40 00 00:00:10.839 READ DMA EXT
25 00 20 90 76 06 40 00 00:00:10.838 READ DMA EXT
SMART Self-test log structure revision number 1
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.
$ smartctl -P showall /dev/sdb1
No presets are defined for this drive. Its identity strings:
MODEL: /dev/sdb1
FIRMWARE: (any)
do not match any of the known regular expressions.
26898
] and divide by 24, then subtract the error time from that value to determine how many days ago the error occurred) and a bunch of other information.Offline_Uncorrectable
sectors and self-test log results from a long test (reallocated sectors, seek errors, etc. can all be caused by non-HDD hardware).Offline_Uncorrectable
sectors don't increase, the drive should be fine. I've had multiple drives in one of my TrueNAS zpools for 7yrs that had hardware errors occur due to an impact a little over a year into their powered-on hours and have had no issues with the drives since