Unable to mount data volume 0004

Hallo,

Yesterday I encountered a critical error in My Cloud 4TB stating that the data volume is not mounted. 

4 second/40 seconds reset/ system only recovery did no avail. 

I tried to access SSH and followed some guides in this forum but it could not solve my problem. I do not have a back up and I need to perserve the data.

WDMyCloud:~# mke2fs -n /dev/sda4
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
243900416 inodes, 975575808 blocks
48778790 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
29773 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848, 512000000, 550731776, 644972544

WDMyCloud:~# parted -l
Model:
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number Start End Size File system Name Flags
 3 15.7MB 528MB 513MB linux-swap(v1) primary
 1 528MB 2576MB 2048MB ext3 primary raid
 2 2576MB 4624MB 2048MB ext3 primary raid
 5 4624MB 4724MB 99.6MB primary
 6 4724MB 4824MB 101MB primary
 7 4824MB 4826MB 1049kB primary
 8 4826MB 4828MB 2097kB primary
 4 4828MB 4001GB 3996GB primary


Model: Linux Software RAID Array (md)
Disk /dev/md0: 2048MB
Sector size (logical/physical): 512B/4096B
Partition Table: loop

Number Start End Size File system Flags
 1 0.00B 2048MB 2048MB ext3

WDMyCloud:~# fsck /dev/sda4
fsck from util-linux 2.20.1
^[[Be2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda4
Could this be a zero-length partition?
WDMyCloud:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/md0: 2047 MB, 2047803392 bytes
2 heads, 4 sectors/track, 499952 cylinders, total 3999616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Doing command 
e2fsck -b blocknumber /dev/sda4 resulted in 
Error writing block 1(Attempt to write block from filesystem resulted in short write). Ignore error? y
Error writing block 2(Attempt to write block from filesystem resulted in short write). Ignore error? y
Error writing block 3(Attempt to write block from filesystem resulted in short write). Ignore error? y
Error writing block 4(Attempt to write block from filesystem resulted in short write). Ignore error? y
Error writing block 5(Attempt to write block from filesystem resulted in short write). Ignore error? y

And it kept going…

Can anyone help me to fix this or is it possible for me to rescue my data by connecting another drive in the USB slot?

Many thanks.

Hello tedwald, welcome to the WD Community. Sorry to hear you cannot access your files, since you want to recover them I recommend you to contact support first before trying anything else, they can assist you with good advice on how to recover your files. You can also contact any of the data recovery partners on the WD support page, some of them offer a free evaluation. 

http://support.wdc.com/country/index.asp

http://support.wdc.com/recovery/index.asp?wdc_lang=en

I suppose badblocks is also reporting some issues, check dmesg once you got write failure , you’ll get more log … warning this is operation is destructive …

Thank you,

I contacted cs. They found my drive had some sustained physical damages and thought data is not retrievable through computer commands. 

To anyone unfortunately encountered the same problem:

I cannot retrive my data after they inspected the system report. I decided to dispose those data comparing them with the data recovery cost.  

I went for RMA and am waiting for a replacement.