One more WD SMR HDD WD40EZAZ-00SF3B0 was recovered by DFL-WD hdd repair tool and DFL-DDP data recovery equipment.
Before repairing the second-translator module 190, the hdd had only 0.2GB data remained, the engineer got the following report:
2022/11/02 09:12:43 —T2 analysis—
2022/11/02 09:12:43 —————————-
2022/11/02 09:12:43 Check SIT:
2022/11/02 09:12:43 SIT Check…OK!
2022/11/02 09:12:43 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:43 Traversal completes
2022/11/02 09:12:43 ***Tree root node no. error(Tree=7507,File=7942)
2022/11/02 09:12:43 —Param—
2022/11/02 09:12:43 T2 Format:LBA64V2
2022/11/02 09:12:44 Capacity 512:7814037168
2022/11/02 09:12:44 Capacity 4K:976754646
2022/11/02 09:12:44 Root:7942
2022/11/02 09:12:44 Entry pre node:29
2022/11/02 09:12:44 Max entry sects:65535
2022/11/02 09:12:44 Node size:256
2022/11/02 09:12:44 —Summary—
2022/11/02 09:12:44 Node count:198850
2022/11/02 09:12:44 Used count:13005
2022/11/02 09:12:44 Free count:185845
2022/11/02 09:12:44 —T2 modules—
2022/11/02 09:12:44 T2 size:50905696
2022/11/02 09:12:44 Data pos:13C6800
2022/11/02 09:12:44 Block size:4096
2022/11/02 09:12:44 Free Node ID:24183
2022/11/02 09:12:44 Entry Count:14967
2022/11/02 09:12:44 Used Entry:46
2022/11/02 09:12:44 Total node count = 198850 Used:13005
2022/11/02 09:12:50 Sort LBA
2022/11/02 09:12:51 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:51 Valid data = 0.20(GB) Unallocated = 3725.83(GB)
2022/11/02 09:12:51 Vacant Nodes:>=0
After repairing the module 190, the report change to repaired status as below:
2022/11/02 09:12:43 —T2 analysis—
2022/11/02 09:12:43 —————————-
2022/11/02 09:12:43 Check SIT:
2022/11/02 09:12:43 SIT Check…OK!
2022/11/02 09:12:43 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:43 Traversal completes
2022/11/02 09:12:43 ***Tree root node no. error(Tree=7507,File=7942)
2022/11/02 09:12:43 —Param—
2022/11/02 09:12:43 T2 Format:LBA64V2
2022/11/02 09:12:44 Capacity 512:7814037168
2022/11/02 09:12:44 Capacity 4K:976754646
2022/11/02 09:12:44 Root:7942
2022/11/02 09:12:44 Entry pre node:29
2022/11/02 09:12:44 Max entry sects:65535
2022/11/02 09:12:44 Node size:256
2022/11/02 09:12:44 —Summary—
2022/11/02 09:12:44 Node count:198850
2022/11/02 09:12:44 Used count:13005
2022/11/02 09:12:44 Free count:185845
2022/11/02 09:12:44 —T2 modules—
2022/11/02 09:12:44 T2 size:50905696
2022/11/02 09:12:44 Data pos:13C6800
2022/11/02 09:12:44 Block size:4096
2022/11/02 09:12:44 Free Node ID:24183
2022/11/02 09:12:44 Entry Count:14967
2022/11/02 09:12:44 Used Entry:46
2022/11/02 09:12:44 Total node count = 198850 Used:13005
2022/11/02 09:12:50 Sort LBA
2022/11/02 09:12:51 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:12:51 Valid data = 0.20(GB) Unallocated = 3725.83(GB)
2022/11/02 09:12:51 Vacant Nodes:>=0
2022/11/02 09:13:20 —T2 analysis—
2022/11/02 09:13:20 —————————-
2022/11/02 09:13:20 Check SIT:
2022/11/02 09:13:20 SIT Check…OK!
2022/11/02 09:13:20 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:13:20 Traversal completes
2022/11/02 09:13:20 —Param—
2022/11/02 09:13:20 T2 Format:LBA64V2
2022/11/02 09:13:20 Capacity 512:7814037168
2022/11/02 09:13:20 Capacity 4K:976754646
2022/11/02 09:13:20 Root:8192
2022/11/02 09:13:20 Entry pre node:29
2022/11/02 09:13:20 Max entry sects:65535
2022/11/02 09:13:20 Node size:256
2022/11/02 09:13:20 —Summary—
2022/11/02 09:13:20 Node count:198850
2022/11/02 09:13:20 Used count:22503
2022/11/02 09:13:20 Free count:176347
2022/11/02 09:13:20 —T2 modules—
2022/11/02 09:13:20 T2 size:50905696
2022/11/02 09:13:20 Data pos:13C6800
2022/11/02 09:13:20 Block size:4096
2022/11/02 09:13:20 Free Node ID:22504
2022/11/02 09:13:20 Entry Count:476879
2022/11/02 09:13:20 Used Entry:475696
2022/11/02 09:13:20 Total node count = 198850 Used:22503
2022/11/02 09:13:22 Sort LBA
2022/11/02 09:13:22 **********Vacant node count = 0 Overlapped node count = 0
2022/11/02 09:13:22 Valid data = 3708.95(GB) Unallocated = 17.07(GB)
2022/11/02 09:13:22 Vacant Nodes:>=0
After repairing module 190, the user wrote the new module 190 to patient HDD and then users get 3708.95(GB) data back by DFL-DDP data recovery equipment.
Any question is welcome to [email protected] or add Dolphin Skype iD: dolphin.data.lab
This is one successful WD hdd firmware repair and data recovery case study for one DFL user from Bangladesh and all lost data was recovered by DFL-PCIe data recovery hardware tool.
HDD Model ID: WD20NMVW-11W68S0
PCB number: 2060-771801
Failure symptoms:
External hdd was not detected by pc
Data was not accessed
The user converted the USB PCB to SATA PCB(771823) and then connected to DFL PCIe data recovery hardware for diagnosis.
DFL-WD hdd firmware repair tool was firstly used to diagnose the firmware corruption issue and the common slow firmware issue was detected and this issue was fixed by one click.
Next DFL-DDP data recovery equipment was used to set up one disk image project and auto decryption function was used to decrypt the data. Finally all lost partitions and files were recovered.
Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab
This is one WD SMR HDD WDC WD40EDAZ-11SLVB0 data recovery case by one client who was using other data recovery tools but failed and finally bought Dolphin data recovery tools to fix the SMR HDD format case and get most data back.
The engineer helped the user to backup the second level translator-module 190 by DFL WD HDD repair tool and then go to DFL DDP data recovery equipment, repair 190.
Before repairing 190, all the data nodes records remained in module 190 indicates the valid data is only 15.01GB after format and the user couldn’t get lost data back at all，the user tried all methods and tools he had.
After repairing the 190 by DFL-DDP data recovery equipment, the engineer got the following result:
2022/10/25 09:41:14 —T2 analysis—
2022/10/25 09:41:14 —————————-
2022/10/25 09:41:14 Checking SIT:
2022/10/25 09:41:14 SIT Checking…OK!
2022/10/25 09:41:15 **********Vacant nodes count = 0 Overlapped nodes count = 0
2022/10/25 09:41:15 Traversal completes
2022/10/25 09:41:15 —Param—
2022/10/25 09:41:15 T2 Format:LBA64V2
2022/10/25 09:41:15 Capacity 512:7814037168
2022/10/25 09:41:15 Capacity 4K:976754646
2022/10/25 09:41:15 Root:8192
2022/10/25 09:41:15 Entry pre node:29
2022/10/25 09:41:15 Max entry sects:65535
2022/10/25 09:41:15 Node size:256
2022/10/25 09:41:15 —Summary—
2022/10/25 09:41:15 Node count:198850
2022/10/25 09:41:15 Uesd count:38690
2022/10/25 09:41:15 Free count:160160
2022/10/25 09:41:15 —T2 modules—
2022/10/25 09:41:15 T2 size in sectors:455808
2022/10/25 09:41:15 Data pos:13C6800
2022/10/25 09:41:15 Block size:4096
2022/10/25 09:41:15 Free Node ID:38691
2022/10/25 09:41:15 Entry Count:781243
2022/10/25 09:41:15 Used Entry:620135
2022/10/25 09:41:15 Total node count = 198850 Used:38690
2022/10/25 09:41:48 Sort LBA
2022/10/25 09:41:51 **********Vacant nodes = 0 Overlapped nodes = 0
2022/10/25 09:41:51 Valid data = 3544.93(GB) Unallocated = 181.09(GB)
2022/10/25 09:41:51 Vacant nodes count:>=0
Finally about 3.5T data was recovered from the WD SMR hard drives.
Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab
T2Data auto loading to RAM is one featured data recovery solution within DFL-DDP data recovery equipment for WD SMR hard drives. Users can find this data recovery solution within the common WD hdd repair column or disk image settings.
Dolphin DFL users can backup T2data by DFL-WD hdd repair tool or users can extract the T2data from the module 190 within DFL-DDP data recovery equipment.
When the WD SMR hard drives are all sectors 0000 or data area is not accessed, users can try to load the T2data auto to RAM for access to the data.
Here is the video on how to load T2data auto to RAM for WD SMR HDD data recovery
Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab
Most WD SMR HDD data recovery cases are concerned with the second-level dynamic translator-module 190.
For example, the WD SMR HDDs are formatted, all sectors 0000, wrongly detected, no data access, etc. Users can try to backup the module 190, repair 190, load module 190 to ram to fix the issue.
For all Dolphin DFL users, it is much easier and more successful to recover WD SMR HDDs. In the video below, users can learn how to use DFL-WD firmware repair tool to backup the module 190 in different ways.
01: Double click module 190, select all hex data and then save as 190.rpm;
02: FW Operations>Read Modules>Read Module 190 by ID mode;
03: FW Operations>Read Modules>Read Module 190 by ABA mode, read copy 0 or copy 1, sometimes copy 0 fails, then try to read copy 1, sometimes if both copies fail, try read valid data only;
04: Read SA regions and users can try to extract module 190 from the SA region.
Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab
For data recovery from all WD SMR HDDs, it’s necessary to learn how to read the original rom, how to generate unlock rom, how to write unlock rom and unlock firmware area, how to backup firmware resources.
Tools used for WD SMR HDD Firmware Unlock and Backup:
DFL-WD HDD firmware repair tool
HDD ROM chip pin reader
Users can learn from the video here on how to do all above
Any question is welcome to [email protected] or add Dolphin Skype ID: dolphin.data.lab
