Data Recovery - SK Hynix HFS500G32TND - 3112A BC

[influx]

Hello,

suddenly the SSD does not work anymore. It is still recognized by Linux/Windows, but there is no partition anymore.

fdisk -l:

Code:

Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: HFS500G32TND-311
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

smartctl: (Serial Number removed)

Code:

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.0.10-1-default] (SUSE RPM)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HFS500G32TND-3112A
Serial Number: XXXXXXXXXXXXXXXXX
Firmware Version: 30060P00
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available
Device is: Not in smartctl database 7.3/5319
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Dec 10 17:01:04 2022 CET
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
No failed Attributes found.

General SMART Values:
Offline data collection status: (0x03) Offline data collection activity
is in progress.
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: ( 0) seconds.
Offline data collection
capabilities: (0x19) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save 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: ( 60) minutes.

SMART Attributes Data Structure revision number: 0
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 166 166 006 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 036 Old_age Always - 28
9 Power_On_Hours 0x0032 061 061 000 Old_age Always - 34681
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1858
100 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 16848174
171 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
172 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
174 Unknown_Attribute 0x0030 100 100 000 Old_age Offline - 135
175 Program_Fail_Count_Chip 0x0032 253 253 000 Old_age Always - 0
176 Erase_Fail_Count_Chip 0x0032 253 253 000 Old_age Always - 0
177 Wear_Leveling_Count 0x0032 097 097 000 Old_age Always - 20
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 000 Old_age Always - 34
179 Used_Rsvd_Blk_Cnt_Tot 0x0032 100 100 000 Old_age Always - 516
180 Unused_Rsvd_Blk_Cnt_Tot 0x0032 100 100 000 Old_age Always - 13372
181 Program_Fail_Cnt_Total 0x0032 253 253 000 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 253 253 000 Old_age Always - 0
183 Runtime_Bad_Block 0x0032 253 253 000 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 39
188 Command_Timeout 0x0032 253 253 000 Old_age Always - 0
191 Unknown_SSD_Attribute 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 023 000 000 Old_age Always - 23 (Min/Max 14/47)
195 Hardware_ECC_Recovered 0x0032 100 099 000 Old_age Always - 1017167385
201 Unknown_SSD_Attribute 0x000e 100 100 000 Old_age Always - 0
204 Soft_ECC_Correction 0x000e 100 001 000 Old_age Always - 0
231 Unknown_SSD_Attribute 0x0033 098 098 010 Pre-fail Always - 3
234 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 9823
235 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 16678
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 15803
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 18915
250 Read_Error_Retry_Rate 0x0032 100 100 000 Old_age Always - 8975325

SMART Error Log Version: 1
ATA Error Count: 14094 (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 14094 occurred at disk power-on lifetime: 34673 hours (1444 days + 17 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

04 41 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

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 10 88 16 00 40 40 00:08:10.100 WRITE FPDMA QUEUED
61 00 08 88 17 00 40 40 00:08:10.100 WRITE FPDMA QUEUED
ef 90 03 00 00 00 00 00 00:08:10.100 SET FEATURES [Disable SATA feature]
ef 02 00 00 00 00 00 00 00:08:10.100 SET FEATURES [Enable write cache]
61 00 10 88 16 00 40 40 00:08:10.070 WRITE FPDMA QUEUED

Error 14093 occurred at disk power-on lifetime: 34673 hours (1444 days + 17 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

04 41 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

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 10 88 16 00 40 40 00:08:10.070 WRITE FPDMA QUEUED
61 00 08 88 17 00 40 40 00:08:10.070 WRITE FPDMA QUEUED
ef 90 03 00 00 00 00 00 00:08:10.070 SET FEATURES [Disable SATA feature]
ef 02 00 00 00 00 00 00 00:08:10.070 SET FEATURES [Enable write cache]
61 00 10 88 16 00 40 40 00:08:10.040 WRITE FPDMA QUEUED

Error 14092 occurred at disk power-on lifetime: 34673 hours (1444 days + 17 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

04 41 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

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 10 88 16 00 40 40 00:08:10.040 WRITE FPDMA QUEUED
61 00 08 88 17 00 40 40 00:08:10.040 WRITE FPDMA QUEUED
ef 90 03 00 00 00 00 00 00:08:10.040 SET FEATURES [Disable SATA feature]
ef 02 00 00 00 00 00 00 00:08:10.040 SET FEATURES [Enable write cache]
61 00 10 88 16 00 40 40 00:08:10.010 WRITE FPDMA QUEUED

Error 14091 occurred at disk power-on lifetime: 34673 hours (1444 days + 17 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

04 41 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

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 10 88 16 00 40 40 00:08:10.010 WRITE FPDMA QUEUED
61 00 08 88 17 00 40 40 00:08:10.010 WRITE FPDMA QUEUED
ef 90 03 00 00 00 00 00 00:08:10.010 SET FEATURES [Disable SATA feature]
ef 02 00 00 00 00 00 00 00:08:10.010 SET FEATURES [Enable write cache]
61 00 10 88 16 00 40 40 00:08:09.980 WRITE FPDMA QUEUED

Error 14090 occurred at disk power-on lifetime: 34673 hours (1444 days + 17 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

04 41 00 00 00 00 00 Error: ABRT at LBA = 0x00000000 = 0

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 10 88 16 00 40 40 00:08:09.980 WRITE FPDMA QUEUED
61 00 08 88 17 00 40 40 00:08:09.980 WRITE FPDMA QUEUED
ef 90 03 00 00 00 00 00 00:08:09.980 SET FEATURES [Disable SATA feature]
ef 02 00 00 00 00 00 00 00:08:09.980 SET FEATURES [Enable write cache]
61 00 10 88 16 00 40 40 00:08:09.950 WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

Is there a way to get to recover the data?
Via UART? Safe Mode or similar?

Thank you!

[influx]

i was able to gain serial access (UART) and JTAG by shorting the two pins during power up:
I think the SSD is now in SAFE Mode (Size of 8GB) ?

dmesg output:

Code:

[  339.958759] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  339.959884] ata2.00: ATA-0: SKHMS PEARL BOOT, 0.19, max UDMA/133
[  339.959894] ata2.00: 16514064 sectors, multi 0: LBA
[  339.959906] ata2.00: applying bridge limits
[  339.960547] ata2.00: configured for UDMA/100
[  339.960730] scsi 1:0:0:0: Direct-Access     ATA      SKHMS PEARL BOOT 0.19 PQ: 0 ANSI: 5
[  339.961214] sd 1:0:0:0: Attached scsi generic sg0 type 0
[  339.961355] sd 1:0:0:0: [sda] 16514064 512-byte logical blocks: (8.46 GB/7.87 GiB)
[  339.961436] sd 1:0:0:0: [sda] Write Protect is off
[  339.961445] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[  339.961593] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  339.961776] sd 1:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[  339.983246] sd 1:0:0:0: [sda] Attached SCSI disk


fdisk:

Code:

Disk /dev/sda: 7.87 GiB, 8455200768 bytes, 16514064 sectors
Disk model: SKHMS PEARL BOOT
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


UART:

Code:

PC:1973, RBU:76ms

H=> E ATM
SERRI 0000001F
ASTP 00002000
SERR 00000000
E ATM

H=>
H=>help
help                 : show availiable commands.
n                    : switch UART to nand ARM.
dbg      <on/off>    : Switch to debug mode.
dsf                  : download serial flash.
esf                  : erase serial flash.
standby              : put the drive into standby mode.
dbgprt   : debug prints
smart                : Dump smart attribute ram

H=>n
N=>help
help     : show availiable commands.
h        : switch UART to host ARM.
dbg      : Switch to debug mode.
eraseall : erase entire drive
factory  : init drive
errlog   : error log
dftlst   : defect lists
wpmon    : Monitor Write Protect condition
dbgprt   : debug prints
N=>


The JTAG Output is a little bit confusing, because only consists of dots and asterisks:
JTAG:

Code:

..****..................................................................................................................................................

If i read from the disk, it displays an asterisk.

Any ideas?

[fzabkar]

If I understand correctly, your drive IDs correctly and reports valid SMART data, but you cannot access the user area. Is that it?

Does DMDE show anything in the Partitions window?

https://dmde.com/

[influx]

Hello fzabkar

If I understand correctly, your drive IDs correctly and reports valid SMART data, but you cannot access the user area. Is that it?
[...]

Correct. According to the customer, the hard drive was suddenly no longer recognized by Windows.

[...]
Does DMDE show anything in the Partitions window?

Reading the SSD via R-Studio, PC3000 Disk Analyzer or DMDE did not reveal any partitions or data... as if the SSD was suddenly brand new.
Also the HEX Viewer only displays zeros.

[PpetterL]

Hello influx,

did you find any fix for your problem?

I have exactly the same issue with the HFS500G32TND-3110A.
It worked perfectly fine and all of a sudden it did not anymore.

The partitions were still there but not accessible and trying to format partitions etc. threw I/O device errors.
I didn't really need the data on it since it was backed up, so I went to my BIOS and did a Secure Erase in hopes it would fix the problem.
Now it is completely empty and not initialized. Trying to initialize with either a MBR or GPT on Windows results in an I/O error.
Doing the same on Linux with fdisk just does not do anything either.

I did some testing with fio on Linux and reads as well as random reads work perfectly fine up to spec but writing immediately throws I/O errors.
S.M.A.R.T. Data looks okay to me, certainly not like it should stop working from 100% to 0%.
Hex data is just 0s as it is for you.

I suspect that the firmware is somehow bricked (although I know nothing about firmware) as this issue looks very similar to the Satafirm S11 issue with one of the Phison Controllers.

There is the Easy Kit SSD Toolkit from SK Hynix with which you can update the firmware on their drives including the SL301 but there is no available firmware file to do that with.


I hope you were successful in your attempt to revive that drive and can tell me how you did it.
Or alternatively we can maybe figure out a way together somehow!

[influx]

[...]
I suspect that the firmware is somehow bricked (although I know nothing about firmware) as this issue looks very similar to the Satafirm S11 issue with one of the Phison Controllers.

Yes, thats my guess as well. - Unfortunately i was unable to recovery any data.
My SSD had 34681 Power_On_Hours (3,9 years).
I suspect that the controller firmware has a bug so that it loses its data after about 4 years of service. (Flash Translation Layer gets corrupted or anything like that)

How many Power_On_Hours does your ssd have?

[PpetterL]

Oh okay, that is a long time compared to mine.
If I remember correctly (I don't have it handy right now), it had ~7600 hours.
But I think the event that bricked mine was probably an abrupt power loss or something.
The Windows on it was in hibernation mode as well.

Is there maybe a way to pull the current firmware on it without having to open it up and tinker with UART? Or maybe pull it from a working drive of the same model?

[labtech]

Old Intel SSD had the abrupt interruption problem.
It was a hardware flaw with the design.
SK Hynix SSD have other problems, like NAND flash degradation only, or if severe, turning into firmware issue (like the firmware translation layer).