Western Digital My Cloud Data Recovery

Western Digital's My Cloud series offers users the convenience of centralized storage and remote access to their data. However, even with advanced storage solutions like My Cloud, data loss can still occur due to various reasons, presenting users with significant challenges in recovering their valuable information.

Western Digital WD My Cloud Data Recovery Dissasembly

WD My Cloud has a 4TB WD Red hard drive inside designed for NAS with bad sectors needing data recovery

1. Hardware Failures

One of the most common reasons for data loss in Western Digital My Cloud devices is hardware failure. Despite being designed for reliability, hard drives can still experience mechanical issues, such as head crashes, motor failures, or electronic component failures. These hardware failures can render the data inaccessible and require specialized expertise to recover.

2. File System Corruption

File system corruption can occur due to sudden power outages, improper shutdowns, or software bugs. When the file system on a My Cloud device becomes corrupted, users may experience difficulties accessing their data or even encounter the dreaded "file system not recognized" error. Recovering data from a corrupted file system often requires advanced tools and techniques to reconstruct the file structures and retrieve the files intact.

3. Accidental Deletion or Formatting

Human error is another significant factor contributing to data loss on Western Digital My Cloud devices. Accidentally deleting important files or formatting the entire drive can lead to irreversible data loss if proper backup measures are not in place. While data recovery software can sometimes help recover accidentally deleted files, the success rate depends on various factors, including the extent of data fragmentation and overwrite.

4. Firmware Issues

Firmware issues in My Cloud devices can manifest in different ways, ranging from connectivity problems to complete system crashes. Firmware updates gone wrong or incompatible firmware versions can result in data loss or device instability. Recovering data from My Cloud devices affected by firmware issues may require specialized tools and expertise to bypass or repair the firmware and access the underlying data.

5. RAID Rebuild Failures

My Cloud devices configured with RAID (Redundant Array of Independent Disks) for data redundancy can still experience data loss if a RAID rebuild fails. RAID rebuild failures can occur due to various reasons, such as disk errors, power interruptions during the rebuild process, or mismatched drive configurations. Recovering data from a failed RAID rebuild often requires expert knowledge of RAID systems and data recovery techniques to reconstruct the data from the remaining disks.

Conclusion

While Western Digital My Cloud devices offer convenient storage solutions for home and business users alike, they are not immune to data loss. Hardware failures, file system corruption, accidental deletion, firmware issues, and RAID rebuild failures are just some of the common challenges users may encounter when attempting to recover data from My Cloud devices. In such situations, seeking professional data recovery services from experienced providers is often the best course of action to maximize the chances of successful data recovery without risking further damage to the valuable information stored on these devices.

Data Recovery WD My Cloud Case Log

14May24: This drive shows no problems in the smart but the customer said that it no longer detects over their network using Windows 11. Bad sectors were found by doing a read test. They use a linux EXT4 file system.

Model : WDC WD40EFRX-68WT0N0
Serial : WD-WCC4E7TEDV3B
Firmware : 82.00A82
Capacity : 4 TB (7 814 037 168)

Family:................................. : Giant
Techno mode key......................... : Ok

HDD Status sector....................... : Ok

RAM:
System controller (SoC)................. : 88i9446C0 0x(A5C0)
HDD Info reading........................ : Ok
Heads number............................ : 8
Cyl Count............................... : 256

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 402 725
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted

SA SPT.................................. : 6347

SA Translator loading................... : Ok
SA defects assigned..................... : 5

ROM Modules:
ROM version............................. : 02.7PC
Module 4F F/W version................... : 0002007P
Overlay F/W version..................... : 02.7QC
Servo F/W version....................... : 02.57

Heads configuration..................... : by map
Heads number............................ : 8
Heads number in use..................... : 8
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5,6,7

Relocations............................. : 0 (2 163)
Read ROM DCM............................ : Ok

Power up log reading.................... : Ok
Power up load dir data.................. : Yes
Power up load permovl................... : Yes
Power up load CFG data.................. : Yes

Service area:
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 510

SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
CFG tech mode lock...................... : No
Self encryption drive................... : No
Master Password......................... : has not been set
User Password........................... : has not been set

DCM in module 47........................ : WM
DCM in module 0A........................ : |F|GWMPXGC
DCM in module 02........................ : S|BFLNPGMWHMCPRXVGKMUG

S.M.A.R.T. Data reading................. : Ok

Data Recovery WD My Cloud Home Case Log

01July2024: Drive has dead heads. Cleanroom work needed.

The enclosure PCB (via UART) drops into a command interface with the following output when no drive is connected (115200 baud):

C1:80000000
C2
?
C3h
hwsetting size: 000005C0
C4
f
5-5
Goto FSBL: 0x10100000
<=============================================>
fsbl_main: sys_secure_type = 0x0000BEEE
fsbl_main: sys_boot_type = 0x00000001
fsbl_main: sys_boot_enc = 0x00000000
fsbl_main: sys_bisr_done = 0x00000000
sys_hwsetting_size:00000600
sys_bootcode_size:00067440
sys_secure_fsbl_size:00010B00
sys_secure_os_size:00000000
sys_bl31_size:00005040
sys_rsa_key_fw_size:00000000
sys_rsa_key_tee_size:00000000
sys_rescue_size:00026360

HwSetting:
hwsetting_blk_no:88120800
hwsetting_total_size:00000680
hwsetting_blk_count:00000680

Bootcode:
bootcode_blk_no:88120E80
bootcode_total_size:00067460
bootcode_blk_count:00067460

FSBL:
secure_fsbl_blk_no:881882E0
secure_fsbl_total_size:00010B20
secure_fsbl_blk_count:00010B20

TEE OS:
secure_os_blk_no:88198E00
secure_os_total_size:00000000
secure_os_blk_count:00000000

BL31:
bl31_blk_no:88198E00
bl31_total_size:00005060
bl31_blk_count:00005060

RSA Key Fw:
rsa_key_fw_blk_no:8819DE60
rsa_key_fw_total_size:00000000
rsa_key_fw_blk_count:00000000

RSA Key TEE:
rsa_key_tee_blk_no:8819DE60
rsa_key_tee_total_size:00000000
rsa_key_tee_blk_count:00000000

Rescue:
rescue_blk_no:8819DE60
rescue_total_size:00026380
rescue_blk_count:00026380
********** FW_TYPE_BOOTCODE **********
fwInfo->fwType: 00000001
fwInfo->isGolden: 00000001
fwInfo->ddrReadAddr: 00520000
fwInfo->ddrDestAddr: 00020000
fwInfo->flashType: 00000001
fwInfo->flashUnitSize: 00000001
fwInfo->flashOffset: 88120E80
fwInfo->dataSize: 00067460
body_size:00067440
flash_unit_no:88120E80
flash_unit_count:00067460
real_size:00067418
sha256 Fw
j bootcode jump address:00020000
64b

4.1.4

CPU : Cortex-A53 quad core - AARCH32
Board: Realtek QA Board
[ERR] get_accessible_ddr_size: hw setting error. (impossible value 0x0)
[ERR] get_accessible_ddr_size: hw setting error. (impossible value 0x0)
DRAM: 0 Bytes
Watchdog: Disabled
Cache: Enabled
Non-Cache Region: 1 MB@0x07900000
nor flash id [0x00ef4014]
sector 256k en: 0
sector 64k en: 1
sector 32k en: 1
sector 4k en: 1
page_program : 1
max capacity : 0x00100000
spi type name : WINBOND_W25Q80BV_8Mbit
[SATA] enable SATA interface
[SATA] spread-spectrum disable
Factory: NOR
Factory: pp:0, seq#:0x3c, size:0x2400
------------can't find tmp/factory/000BootParam.h
Set HDMI TX OFF
In: serial
Out: serial
Err: serial
Net: Realtek PCIe GBE Family Controller mcfg = 0024
dev->name=r8168#0
*** Reboot-Action invalid ***
Hit Esc or Tab key to enter console mode or rescue linux: 0
------------can't find tmp/factory/recovery
======== Checking into android recovery ====

AHCI 0001.0301 32 slots 2 ports ? Gbps 0x3 impl SATA mode
flags: ncq pm led clo only pmp pio slum part
No port device detected!
Error, SATA device initialization failed!
bootr - boot realtek platform

Usage:
bootr [u/uz]
u - boot from usb
uz - boot from usb (use lzma image)
m - read fw from flash but boot manually (go all)

Enter console mode, disable watchdog ...

Realtek> help
b2ndbc - load 2nd stage bootcode
bdinfo - print Board Info structure
bootm - boot application image from memory
bootr - boot realtek platform
dcache - enable or disable data cache
dhcp - boot image via network using DHCP/TFTP protocol
env - environment handling commands
factory - FACTORY sub system
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatwrite- write file into a dos filesystem
fdt - flattened device tree utility commands
gettime - get timer val elapsed
go - start application at address 'addr' or start running fw
goru - start rescue linux from usb
gpt - GUID Partition Table
help - print command description/usage
i2c - I2C sub-system
icache - enable or disable instruction cache
keyset - keyset - write keyset file into factory area
loady - load binary file over serial line (ymodem mode)
md - memory display
mtest - simple RAM read/write test
mtest2 - simple RAM read/write test
mw - memory write (fill)
ping - send ICMP ECHO_REQUEST to network host
reset - Perform RESET of the CPU
rtkfat - Realtek FAT32 format utility v1.0
rtkfdt - RTK fdt utility
rtkgpt - rtkgpt utility
rtkrng - rng utility
rtkspi - spi flash utility
sata - SATA sub system
saveenv - save environment variables to persistent storage
source - run script from memory
tftp - download image from TFTP server
tftpput - TFTP put command, for uploading files to a server
uart_write- for uart mp tool burn mac and sn keyunzip - unzip a memory region
usb - USB sub-system
version - print monitor, compiler and linker version
wdpp - Western Digital Boot Patition Tool
Realtek> bdinfo
arch_number = 0x0000138A
boot_params = 0x00100100
DRAM bank = 0x00000000
-> start = 0x00000000
-> size = 0x00000000
ethaddr = 00:14:EE:02:D8:13
ip_addr = 192.168.100.1
baudrate = 115200 bps
TLB addr = 0x000E0000
*** bdinfo pll ***
SCPU PLL = 1201 MHz
SCPU = 600 MHz
ACPU PLL = 549 MHz
ACPU = 549 MHz
VCPU1 PLL = 594 MHz
VCPU2 PLL = 675 MHz
DDSA PLL = 432 MHz
DDSB PLL = 432 MHz
BUS PLL = 255 MHz
BUS_H PLL = 459 MHz
GPU PLL = 449 MHz
VODMA PLL = 405 MHz
*** bdinfo ddr ***
DDR = 1600 MHz (0x1a)
[ERR] get_ddr_size: hw setting error. (impossible value 0xf)
[ERR] get_accessible_ddr_size: hw setting error. (impossible value 0x0)
[ERR] get_ddr_size: hw setting error. (impossible value 0xf)
[ERR] get_accessible_ddr_size: hw setting error. (impossible value 0x0)
DDR SIZE = 0*2 = 0 MB (Evaluated from DC1 0xb8008004/0x18008740)
Realtek> version
4.1.4
arm-linux-gnueabi-xgcc (Realtek ASDK-4.9.3 Build 2180) 4.9.3 20150413 (prerelease)
GNU ld (Realtek ASDK-4.9.3 Build 2180) 2.24.0.20141017
Realtek>