My dying 2TB HDD finally gave up the ghost
Hello, I'm incompetent.
My 3TB HDD died the other day and I recovered it, but now my 2TB HDD has died.
This is a memo about that.
By the way, if you're asking if I'm depressed because it broke, I'm a little sad, but I didn't put any important data on it in the first place. It was just for file sharing among my many PCs, so the original files are elsewhere. So, I'm not that depressed.
It's sad, but I bought it for about 500 yen with bad sectors already present, so in a way, I bought it to break it.
I never know what to do until something breaks, so I'm always the guinea pig.
By the way, there's already a clearly strange noise, so it would be a miracle if I could retrieve any data.
Last time, I successfully recovered it and it's back to being overworked on my home server.
As they say, masochists have the potential to be sadists; it's something like that.
Checking the Superblock
$ sudo mkfs.ext4 -n /dev/sdb
mke2fs 1.47.1 (20-May-2024)
Creating filesystem with 122094657 4k blocks and 30531584 inodes
Filesystem UUID: 81d0a0ba-490a-4ea0-bb08-ee84f122b21e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000
You can check the backups of metadata-like information held by the file system.
Superblock Restoration
If you want to restore:
sudo e2fsck -b 71663616 /dev/sdb1
Enter the value of Superblock backups stored on blocks as the argument for -b.
smartctl
Checking disk status
sudo smartctl -a /dev/sdb
Execution result
$ sudo smartctl -a /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.1-artix1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda Green (AF)
Device Model: ST2000DL003-9VT166
Serial Number: 5YD3ZLT5
LU WWN Device Id: 5 000c50 038d5b835
Firmware Version: CC32
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5900 rpm
Device is: In smartctl database 7.3/5528
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Thu Oct 17 00:58:11 2024 JST
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.
See vendor-specific Attribute list for marginal Attributes.
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: ( 612) 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: ( 334) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x30b7) SCT Status 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 098 079 006 Pre-fail Always - 50824899
3 Spin_Up_Time 0x0003 096 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 554
5 Reallocated_Sector_Ct 0x0033 047 047 036 Pre-fail Always - 35272
7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always - 434289978
9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 11048
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 554
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 098 098 099 Old_age Always FAILING_NOW 2
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 9017
188 Command_Timeout 0x0032 099 098 000 Old_age Always - 47245361169
189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 342
190 Airflow_Temperature_Cel 0x0022 061 055 045 Old_age Always - 39 (Min/Max 39/39)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 511
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 576
194 Temperature_Celsius 0x0022 039 045 000 Old_age Always - 39 (0 22 0 0 0)
195 Hardware_ECC_Recovered 0x001a 036 005 000 Old_age Always - 50824899
197 Current_Pending_Sector 0x0012 001 001 000 Old_age Always - 13032
198 Offline_Uncorrectable 0x0010 001 001 000 Old_age Offline - 13032
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 11007 (95 12 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4111343507
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2489096598
SMART Error Log Version: 1
ATA Error Count: 4459 (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 4459 occurred at disk power-on lifetime: 11048 hours (460 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 51 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
-- -- -- -- -- -- -- -- ---------------- --------------------
25 d5 b8 ff ff ff ef 00 00:01:07.241 READ DMA EXT
25 d5 b8 ff ff ff ef 00 00:00:57.948 READ DMA EXT
25 d5 98 ff ff ff ef 00 00:00:57.934 READ DMA EXT
25 d5 a0 ff ff ff ef 00 00:00:57.919 READ DMA EXT
25 d5 a0 ff ff ff ef 00 00:00:57.914 READ DMA EXT
Error 4458 occurred at disk power-on lifetime: 11048 hours (460 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 51 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
-- -- -- -- -- -- -- -- ---------------- --------------------
25 d5 b8 ff ff ff ef 00 00:00:57.948 READ DMA EXT
25 d5 98 ff ff ff ef 00 00:00:57.934 READ DMA EXT
25 d5 a0 ff ff ff ef 00 00:00:57.919 READ DMA EXT
25 d5 a0 ff ff ff ef 00 00:00:57.914 READ DMA EXT
25 d5 a0 ff ff ff ef 00 00:00:57.899 READ DMA EXT
Error 4457 occurred at disk power-on lifetime: 11048 hours (460 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 51 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
-- -- -- -- -- -- -- -- ---------------- --------------------
25 d5 c0 ff ff ff ef 00 00:00:30.313 READ DMA EXT
25 d5 08 ff ff ff ef 00 00:00:30.312 READ DMA EXT
25 d5 50 ff ff ff ef 00 00:00:30.296 READ DMA EXT
25 d5 58 ff ff ff ef 00 00:00:30.294 READ DMA EXT
25 d5 58 ff ff ff ef 00 00:00:30.292 READ DMA EXT
Error 4456 occurred at disk power-on lifetime: 11048 hours (460 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 51 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
-- -- -- -- -- -- -- -- ---------------- --------------------
25 d5 f0 ff ff ff ef 00 00:00:25.557 READ DMA EXT
25 d5 f0 ff ff ff ef 00 00:00:25.551 READ DMA EXT
25 d5 10 ff ff ff ef 00 00:00:25.551 READ DMA EXT
25 d5 20 ff ff ff ef 00 00:00:25.549 READ DMA EXT
25 d5 38 ff ff ff ef 00 00:00:25.548 READ DMA EXT
Error 4455 occurred at disk power-on lifetime: 11048 hours (460 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 51 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
-- -- -- -- -- -- -- -- ---------------- --------------------
25 d5 08 ff ff ff ef 00 00:00:56.960 READ DMA EXT
25 d5 10 ff ff ff ef 00 00:00:56.958 READ DMA EXT
25 d5 f0 ff ff ff ef 00 00:00:56.953 READ DMA EXT
25 d5 08 ff ff ff ef 00 00:00:56.947 READ DMA EXT
25 d5 10 ff ff ff ef 00 00:00:56.945 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 70% 11048 436275968
# 2 Short offline Completed: read failure 70% 11048 436209928
# 3 Short offline Interrupted (host reset) 00% 11048 -
# 4 Short offline Completed: read failure 70% 11048 436209928
# 5 Short offline Completed: read failure 90% 11047 436209928
# 6 Short offline Completed: read failure 90% 11047 436209928
# 7 Short offline Completed: read failure 90% 11047 436209928
# 8 Short offline Interrupted (host reset) 00% 11047 -
# 9 Short offline Completed: read failure 90% 11047 436209928
#10 Short offline Interrupted (host reset) 00% 11046 -
#11 Short offline Completed: read failure 90% 11046 1438650248
#12 Short offline Interrupted (host reset) 00% 11045 -
#13 Short offline Completed: read failure 10% 10835 266787488
#14 Short offline Completed: read failure 10% 10667 266787488
#15 Short offline Completed: read failure 60% 10499 266787488
#16 Short offline Completed: read failure 10% 10331 266787488
#17 Short offline Completed: read failure 10% 10163 266787488
#18 Short offline Completed: read failure 10% 9995 266765001
#19 Short offline Completed: read failure 10% 9982 266765001
#20 Short offline Aborted by host 10% 9981 -
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
Quick Test
Actually, I think the correct way to check is to first confirm with -a, then run the test, and then run it again.
sudo smartctl -t short /dev/sdb1
Specifying 'long' seems to take about 60 minutes.
How to pass bad sectors to fsck when even badblocks command doesn't work
There's a convenient badblocks command just for detecting bad blocks.
This only checks for their existence, it doesn't repair them. There's also an option for the fsck command to run badblocks and repair them.
In the end, SATA connection might be fine, but if there are bad blocks that even a USB-HDD can't read, the connection will be automatically reset like this, and you won't be able to continue.
[ 2606.101954] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 1a 00 09 18 00 00 e8 00
[ 2606.101960] blk_print_req_error: 9 callbacks suppressed
[ 2606.101965] I/O error, dev sdb, sector 436209944 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 2636.680192] usb 3-2: reset high-speed USB device number 25 using xhci_hcd
[ 2640.153840] usb 3-2: USB disconnect, device number 25
If the disk itself is too severely damaged, like mine, attempting to boot a PC with a SATA connection will cause the BIOS to stack before booting, possibly because it can't find the disk.
The same phenomenon occurs with SSDs.
Passing bad sector information from file reading
In the end, based on the information output from the kernel, I'll write it into a text file in a format that can be read line by line.
dmesg
[ 3140.292122] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 1a 00 09 48 00 00 b8 00
[ 3140.292130] I/O error, dev sdb, sector 436209992 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
File to pass as badblock information
$ cat badblock
436209984
436275968
436209992
Then pass this to fsck
sudo e2fsck -f -y -l ./badblock /dev/sdb1
I'm writing this in a lighthearted tone, but it's undoubtedly very dangerous, so it's better not to do it.
Conclusion
There's also the ddrescue command for recovery, and I think data rescue is possible if it's a SATA connection and not a complete physical damage to the HDD. Clearly abnormal disks like mine are very rare, so this probably won't be much help. This is for those who want to play with disks as an experiment.