I'm in desperate straits. We have many volumes of media (photos, videos) on our ReadyNas Duo that need to be accessed. We stopped using the device a few years back and the local SSD drive with media fried.
I am not networking savvy.
- I have powered up device and have it connected via ethernet to a switch and our TP Link Deco. The TP Link app sees other wired devices connected to the switch but does not see the ReadyNas Duo. Of course, Windows 11 does not see it either. Is there something that I'm missing?
My ReadyNas says its a RND2110 v2. However, the ports on the back of the device look like a V1.
What does RAIDar show? If the NAS doesn't show up with drives installed, try without them (but label them so they go back in the same slots).
Yes, you have a V1. A "real" V2 says so on the front, not just a sticker. Netgear really messed up using the V2 moniker when they'd already done so. But the V2 also never shipped with drives, so a 2110 has to be a V1.
Once you know the NAS is on the network, you will still have some issues:
If you previously assigned a static IP address from within the NAS GUI and have since re-configured, you are going to have to deal with that. There are a couple ways to do that, but let us know if you need it.
Your NAS only supports SMB, which are depreciated in Windows, and TLS1.0, which is disabled in modern browsers, respectively. You can turn SMB1 on in Windows, and there are work-around for TLS1.0 that are discussed in multiple posts in the forum.
RAIDar does not find the NAS. My TP Link Deco does not find the NAS either.
I will try your suggestion about removing the drives.
However, I may have already messed up. I did previously remove the drives to try to read them on a computer via a Sata cable. (it read fine, but I'm intimidated by the Linux to windows conversion). Along the way, I cannot confidently say which is the left drive and right drive.
What problems might I cause if I put the drives in the wrong bay?
I do not plan on using the ReadyNas going forward. Might it be more straightforward if I go down the path of converting the Linux?
I feel dumb about all this stuff... really appreciate your expertise and the accumulated knowledge on this forum.
That's not good. RAIDar uses a unique protocol to find a ReadyNAS, so it's typically a better tool to use to find one, especially if it's not fully booting.
The NAS is supposed to figure out which drive is which, it's just best to not make it have to. Keeping the drives in the same place also keeps any log entries associated with the drives consistent, but that's not going to help you since you can't even get to the logs.
You cannot read ReadyNAS drives on a PC, at least not without special software. You can mount them and test them non-destructively, but nothing more. So I hope you didn't do anything non-recoverable with them when you did mount them in a PC. Windows will normally warn you if you try to work with a partition it doesn't recognize, so you likely didn't.
Having it on your network without drives will tell you if the problem is on the drives (the NAS runs from the OS installed on them) or a hardware issue. Another ting you can try is to see if it will boot to the reset button menu. If you can, and the problem is with the drives, then @StephenB may be able to guide you through recovery via tech support mode. Alternately, you can use a package like R-Linux for Windows to read the drives in Windows and recover the data.
This will only work on the primary disk - the RAID mirror will show the operating system partition, but not the data. So you might need to try both.
Don't attempt to "convert" anything from linux formatting. This tool should be able to find the drive and the files, even though Windows can't mount it.
Once you've off-loaded the data, we can sort out whether the NAS can be resurrected or not.
