As you can see here:
The HDD is almost gone… you can check the smart values:
sudo smartctl -a /dev/sda
But I guess the HDD has a physical damage.
sudo smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.13-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: 27HIS90RS
LU WWN Device Id: 5 000039 795e82f53
Firmware Version: AX1P5J
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Sep 25 10:46:52 2021 EDT
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: ( 112) The previous self-test completed having
the read element of the test failed.
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: ( 237) 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 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 - 1855
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 39453
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 64
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 052 052 000 Old_age Always - 19230
10 Spin_Retry_Count 0x0033 253 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2360
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 111
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 254
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 129619
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 31 (Min/Max 20/46)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 7
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 6136
198 Offline_Uncorrectable 0x0030 001 001 000 Old_age Offline - 255
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 060 060 000 Old_age Always - 16342
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 - 189
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 6612 (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 6612 occurred at disk power-on lifetime: 19230 hours (801 days + 6 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 41 60 22 00 00 40 Error: UNC at LBA = 0x00000022 = 34
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 08 60 20 00 00 40 00 1d+19:33:12.777 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 1d+19:33:12.776 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 1d+19:33:12.776 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 1d+19:33:12.775 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 1d+19:33:12.775 SET FEATURES [Set transfer mode]
Error 6611 occurred at disk power-on lifetime: 19230 hours (801 days + 6 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 41 00 22 00 00 40 Error: UNC at LBA = 0x00000022 = 34
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 08 00 20 00 00 40 00 1d+19:33:12.630 READ FPDMA QUEUED
60 08 f8 a0 61 70 40 00 1d+19:33:12.626 READ FPDMA QUEUED
60 08 b8 f8 69 70 40 00 1d+19:33:12.626 READ FPDMA QUEUED
60 08 b0 d0 69 70 40 00 1d+19:33:12.626 READ FPDMA QUEUED
60 08 a8 e0 69 70 40 00 1d+19:33:12.626 READ FPDMA QUEUED
Error 6610 occurred at disk power-on lifetime: 19230 hours (801 days + 6 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 41 98 22 00 00 40 Error: UNC at LBA = 0x00000022 = 34
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 08 98 20 00 00 40 00 1d+19:33:12.358 READ FPDMA QUEUED
60 08 90 18 00 00 40 00 1d+19:33:12.358 READ FPDMA QUEUED
60 08 88 10 00 00 40 00 1d+19:33:12.358 READ FPDMA QUEUED
60 08 80 08 00 00 40 00 1d+19:33:12.358 READ FPDMA QUEUED
60 08 78 00 00 00 40 00 1d+19:33:12.329 READ FPDMA QUEUED
Error 6609 occurred at disk power-on lifetime: 19230 hours (801 days + 6 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 41 a0 22 00 00 40 Error: UNC at LBA = 0x00000022 = 34
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 08 a0 20 00 00 40 00 1d+19:27:23.584 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 1d+19:27:23.583 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 1d+19:27:23.583 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 1d+19:27:23.582 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 1d+19:27:23.582 SET FEATURES [Set transfer mode]
Error 6608 occurred at disk power-on lifetime: 19230 hours (801 days + 6 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 41 10 22 00 00 40 Error: UNC at LBA = 0x00000022 = 34
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 08 10 20 00 00 40 00 1d+19:27:23.437 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 1d+19:27:23.437 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 1d+19:27:23.436 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 00 1d+19:27:23.435 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 1d+19:27:23.435 SET FEATURES [Set transfer mode]
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 00% 19215 34
# 2 Extended offline Interrupted (host reset) 80% 19191 -
# 3 Extended offline Aborted by host 90% 19185 -
# 4 Short offline Completed: read failure 00% 19185 2049
# 5 Short offline Completed without error 00% 19073 -
# 6 Short offline Completed without error 00% 17855 -
# 7 Short offline Completed without error 00% 16829 -
# 8 Short offline Completed without error 00% 16396 -
# 9 Short offline Completed without error 00% 11177 -
#10 Short offline Completed without error 00% 2667 -
#11 Short offline Completed without error 00% 2643 -
#12 Short offline Completed without error 00% 2634 -
#13 Short offline Completed without error 00% 2560 -
#14 Short offline Completed without error 00% 2536 -
#15 Short offline Completed without error 00% 2512 -
#16 Short offline Completed without error 00% 2488 -
#17 Short offline Completed without error 00% 2464 -
#18 Short offline Completed without error 00% 2440 -
#19 Short offline Completed without error 00% 2416 -
#20 Extended offline Completed without error 00% 2393 -
#21 Short offline Completed without error 00% 2368 -
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.
That says everything:
- 64 reallocated sectors
- 255 uncorrectable errors
And now there are no spare sectors left for relocation of the bad sector:
So if you can and need the data on that disk, then create a backup image of it with dd, anything else makes no sense. The HDD is EOL.
2 Likes
Thanks for the help. thought that was the case just trying to make sure.
To follow up on that suggestion, you will have better luck with ddrescue.
It’s a two-part process, at minimum, but you can also do an additional third pass.
Pass 1: Run through the disk and skip any unreadable sectors / regions. (Sectors and regions that were not recovered are saved in a log file.)
Pass 2: Use the log file to attempt to recover the unreadable portions.
Pass 3: Try again, with the updated log file, but this time go in “reverse” order, from last to first sector backwards.
The resulting drive image is a best shot attempt to let you pull important data, if even possible. It depends on the state of the drive and how much damage has already been done, and where the unrecoverable portions are physically located.
WORST-CASE EMERGENCY: If you cannot mount a working filesystem from the recovery image (i.e, too much damage in the metadata), you can run photorec on the drive image and cross your fingers it will find the data. Photorec works by analyzing known signatures of different file types, and if they’re located in a sequential region, it can recover the file. It will not recover the timestamps, folder structure, nor file names.
None of the above should be relied on (or even hold relevance) if you have recent backups of your important stuff.
3 Likes