ReadyNas 2120v2 No Longer Network Accessible

Question

I'm in the process of taking our ReadyNas 2120v2 out of service due to age. Yesterday, I was moving data off the unit when network accessibility was abruptly lost.. I lost assess to the SMB shares and the web UI. It is set to a static IP, which is no longer responding to pings, IP scanners, etc. RAIDar will also not locate the unit. Most of the IP addresses on our network are taken up by statics, so it's obvious that DHCP has not tried to give it a different address.

Here's what I have tried:

1, Power cycling the unit.

2. Tried different ethernet cords and ports.

3. OS reinstall.

4. Reflashing the OS by USB drive, which it will not accept.

I am not willing to perform a factory reset since I want the data off the unit. I only need to get it running properly long enough to get the rest of the data off.

Thoughts and suggestions?

I did consider popping the CMOS battery, but I am unsure of any potential consequences with data protection

StephenB · Answer

I suggest powering down and removing the disks (labeling by slot, so you can restore them later).
&nbsp;
Then power up, and see if RAIDar detects the NAS.&nbsp; Normally it will, and give you a no-disks status.

StephenB · Answer

mtkoc&nbsp;wrote:
The web UI still isn't accessible though.
&nbsp;
&nbsp;

That is normal.&nbsp; The linux os and the readynas application software is on the disks.
&nbsp;
This test shows that your NAS chassis is ok.&nbsp; There is could be a problem with the disk the NAS is booting from (normally disk 1), or something could have gone seriously wrong with the OS partition (which is RAID-1 and mirrored on all disks).
&nbsp;
You could try putting all the disks back except for disk 1, and then see if you can boot the NAS read-only.&nbsp; Read-only would ensure nothing is written to the data volume (making sure the volume remains in sync).&nbsp; Instructions for a read-only boot are on page 17 of the hardware manual:

https://www.downloads.netgear.com/files/GDC/RN2120/ReadyNAS_OS6_Rackmount_HWM_EN.pdf

If this works, I suggest continuing your backup.
&nbsp;
If it fails, then the problem is not a failure of disk 1. The next steps depend on how important the data is.&nbsp;
&nbsp;
The safest option is to move to data recovery - either contracting with a data recovery service, or doing it yourself.&nbsp; Doing this yourself would require connecting the disks to a windows pc (needing a suitable enclosure) and purchasing recovery software that supports linux RAID and BTRFS.&nbsp; ReclaiMe is one package that folks here have used with the success.&nbsp; You could try it prior to purchase, and see if it finds your files.&nbsp; Actual recovery would require purchase.
&nbsp;
You could also try doing an OS reinstall from the boot menu with all disks in place.&nbsp; This is data safe and will do a partial reinstall of the OS and the NAS firmware.&nbsp; The reinstall will

set the NAS admin password back to password
set the network config to DHCP with no bonding
disable volume quota (which can be re-enabled from the volume settings wheel).

Another poster had a problem recently that sounds very similar to your symptoms (but not with an RN2120v2).&nbsp; he found that the system booted after the OS reinstall, but that the web interface prompted him to start the setup process.&nbsp; I don't recommend starting that process, as I think there is a good chance you'll lose data if you do.&nbsp; Still, if you run into this it would be useful to see if you can access the shares over SMB.
&nbsp;
If you are skilled with the linux command line (including mdadm and btrfs commands), you could also try booting the system in tech support mode, and then try to troubleshoot from there.
&nbsp;
&nbsp;
&nbsp;

Sandshark · Answer

You probably shouldn't do a USB recovery, so it's good that it didn't work.&nbsp; The flash is at least mostly OK since it booted diskless.&nbsp; You can fully verify the flash content and check the last remaining potential hardware issue by inserting just a scratch disk and seeing if the NAS initializes it.&nbsp; Once it has and you've created a volume on it, you can power down, move the drive to the next bay, and power up to see that it boots.&nbsp; Repeat until you test all bays.&nbsp;If the NAS can't properly initialize a new drive, then you either have a corrupt flash, or there is a problem with the SATA subsystem of the NAS.&nbsp; If you do get to this point, then try another USB drive for the recovery.&nbsp; Although OS6 units seem to be less picky than older ones as to the flash drive, they are sill known to be a bit picky.

StephenB · Answer

mtkoc&nbsp;wrote:
No, it would not initialize on a scratch drive.&nbsp; I actually filled the sleds with some old identical Seagate HDDs I had laying around.&nbsp;

Did you use the boot menu option to do a factory default?
&nbsp;
If not, try erasing one with Seatools to remove any formatting and partitions.&nbsp; Then try powering up the NAS with just that one disk installed.&nbsp; The simple overwrite option is sufficient for this.

mtkoc · Answer

I wanted to post an update.&nbsp; It took me a few days, but I took dd images of the drives as a precaution.&nbsp; A buddy of mine happened to have a ReclaiMe license that he let me borrow.&nbsp;&nbsp;I loaded the dd images into ReclaiMe and I was able to get the last 500Gb of data back that I needed.&nbsp; Worked surprisingly well.&nbsp;I want to thank everyone for their help!&nbsp; At this point, I consider the hardware a lost cause.&nbsp; I was taking it out-of-service anyway, so off to electronics recycling.

Forum Discussion

ReadyNas 2120v2 No Longer Network Accessible

9 Replies

Related Content

Enabling SSH access on Readynas Ultra 2

Readynas Ultra 6 Network issues??

RNDU4000 (ReadyNAS Ultra 4). No more accessible after years of not using

Accessing journalctl command on ReadyNAS 102

network

NETGEAR Academy

ProSupport for Business