ReadyNAS Duo RND2110 v2 died recently. Help with recovering data from the drives

Hello,

My ReadyNAS Duo v2 (2110 model) died recently. It powers up but is not responsive at all. It shows briefly as connected in my router config but then dissapears. It won't power off unless I unplug it and the drives do not appear to spin up.

I am attempting to recover the data from drive #1 but struggling with how best to do this. The ReadyNAS was using x-raid. I bought a powered hard drive enclosure and have that connected via usb3 to my Ubuntu 16.04 server. My server sees the drive and it is visible under /media/. Runniung fdisk -l produces:

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 32 4096031 4096000 2G 83 Linux
/dev/sdb2 4096032 4608031 512000 250M 82 Linux swap / Solaris
/dev/sdb3 4608032 3907008687 3902400656 1.8T 5 Extended
/dev/sdb5 4608040 1953092263 1948484224 929.1G 8e Linux LVM
/dev/sdb6 1953092272 3906992311 1953900040 931.7G 8e Linux LVM

I did some googling and saw an old post from 2010 saying to use R-Tools recovery software but I'm not confident this is the best way at this time. I'm hoping someone out there has done this before and can help guide me in the right direction. Any help is greatly appreciated. Thanks!

StephenB
Jul 09, 2019
robotron3000 wrote:

Thank you for this!

If you meant my response - then that was for the x64 4.2 NAS, not the duo v1.

Here's the procedure for the 4.1 systems (like your Duo)

https://web.archive.org/web/20171003190159/http://home.bott.ca/webserver/?p=306 wrote:

Mounting Sparc-based ReadyNAS Drives in x86-based Linux

(1) sudo su
(2) apt-get install fuseext2
(3) apt-get install lvm2
(4) modprobe fuse
(5) vgscan
(6) vgchange -ay c
(7) fuseext2 -o ro -o sync_read /dev/c/c /mnt

That’s it!!!
You can now see the mounted files in the /mnt directory

Alternative Method

If you are trying to recover data from a Duo (or from a disk with only 1 or 2 disks in the array), then you may be able to recover the data using the following method:

Connect your faulty disk to a Windows PC using a SATA to USB cable

Download, install & run the free software R-linux ( https://www.r-studio.com/free-linux-recovery/ )

Copy the recovered data from the faulty disk

The alternative method only works with the main disk (usually disk 1), not the parity disk. There is a linux version of R-Linux, which you could also try.

Note I did make some edits to the original blog post.

9 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Jul 08, 2019
robotron3000 wrote:
My ReadyNAS Duo v2 (2110 model) died recently.

A lot of v1 users think they have a v2 (as the labeling is confusing). So we should start by confirming the platform.

A Duo v2

runs 5.3.x firmware

was introduced in 2011

says Duo v2 on the front chassis

A Duo v1

runs 4.1.x firmware

was introduced in 2008

says Duo on the front chassis

Which one do you have? There are instructions out there for mounting the Duo v1 disks in x86 linux systems, but I don't think those instructions will work with a Duo v2.
- Sandshark
  Sensei - Experienced User
  Jul 08, 2019
  Given the partition sizes show you have a 4TB drive, you definately have a V2. I believe the instructions you can find for mounting an OS4.2.x drive in a Linux system will work for OS5.x, but I've never tried it.
  - StephenB
    Guru - Experienced User
    Jul 09, 2019
    Sandshark wrote:
    
    I believe the instructions you can find for mounting an OS4.2.x drive in a Linux system will work for OS5.x, but I've never tried it.
    
    The procedure for OS 4.2 should be
    
    # vgscan # vgchange -a y # mount /dev/c/c /c
    
    Though it would be safer to mount read-only using the -o ro option
- robotron3000
  Aspirant
  Jul 09, 2019
  Thanks for the info. I have the v1 (despite the sticker on the bottom saying v2, maybe it is the v2 of the v1?).