ReadyNAS Duo v2 - IP available but won't connect

[mladen5]

Hi, I wonder if somebody would know how I can reaccess my readynas duo v2 again, all of the sudden I seem unable to connect to it.  RAIDar shows that he status us "Healthy" with the one drive connected (green tick against it), and also the ip address (which is 192.168.168.168 if connected directly to my PC).  However, entering the ip address in my browser brings nothing "192.168.168.168 refused to connect."  When I click on my usual link to access I get "Windows cannot access \\READYNAS\backup", it also doesn't show up in my network devices or be able to access it via my mobile phone like I used to.

Any help or guidance on how I can get this working again would be appreciated.

[mladen5 · Accepted solution]

Unfortunately it's the only disk.  Nevertheless, I decided to cancel the R-Linux scan which still brought up a red "Rocognized0" volume.  I right clicked on this to select "open drive files", and voila!  I can view the files in the existing folder structure and recover only those I want to keep.   I'll probably bin this one buy a more recent NAS which will hopefully be a tad more reliable.

Thanks for your help though, it is very much appreciated.

[StephenB]

192.168.168.168 is the fail-over IP address when DHCP fails for some reason.  It's not compatible with most home network settings.

You say the cable is directly connected to your PC?  Is that the usual way you have it set up?

What IP address do you see when it is connected to your router?

[mladen5]

Thanks for the prompt response, I did try to connect direct to the PC to try to bypass any potential issue with the router (although not sure why there would be as it worked previously).  If I connect direct to the router (which is how I've been connecting to it to date), the ip address for the readynas is 192.168.0.15.  My local PC ip address is 192.168.0.17 if that makes any difference.  I've spent quite a bit of time on it and not sure what else to do. 😞

[mladen5]

The model is RND-2B if that makes any difference?  Failing that, is there a way to read/mount the drive directly via a sata cable so that I can at least retrieve some data from it?

[StephenB]

does entering \\192.168.0.15 into file explorer give you a different result?

Can you log into the NAS web ui to https://192.168.0.15/admin?

[mladen5]

Both give the same result, "192.168.0.15 refused to connect".  Interestingly I can ping it in command prompt.

[StephenB]

---

@mladen5 wrote:

Both give the same result, "192.168.0.15 refused to connect".  

---

Have you tried rebooting the NAS?

Also, you could try running CMD and entering

net use * /delete /y
net use t: \\192.168.0.15\C /user:admin nas-admin-password

using the real NAS admin password of course.  Be careful on the typing (especially the two different slashes).

The second command attempt to mount the NAS data volume (C) as drive letter T.

[mladen5]

Tried rebooting multiple times by unplugging and plugging back in.  The commands suggested didn't yield much unfortunately, see screenshot.  Anything else worth trying? really appreciate your help btw.

[StephenB]

---

@mladen5 wrote:

The commands suggested didn't yield much unfortunately, see screenshot. 

---

Thx for the screenshot.  Turns out I typed the NAS IP incorrectly (and you used that IP in your command).

So try that again.

---

@mladen5 wrote:

Anything else worth trying? 

---

There are a couple other things we can try.  But I think it's better to go step-by-step right now.

[mladen5]

Well spotted, although same result unfortunately 😞

[StephenB]

If you are running Win 10 or Win 11, then go into "turn windows features on or off" and make sure the SMB 1 client is enabled.

If it isn't, then enable it, and try again.

If it is, then the next step is to try an OS reinstall. See pages 16-17 here: https://www.downloads.netgear.com/files/GDC/RND2110/ReadyNAS_Duov2_NV+v2_HW_en_23-Mar-12.pdf

Be careful not to do a factory default by mistake - that will wipe your data.

This does have a side effect - the network password will be reset to password.  Also, the net use command I gave earlier won't work until you reset the admin password to something else.

[mladen5]

That's done, seemed to only take a moment once I'd pressed that reset button at the back to finalie the option to resintall OS.  However, now RAIDar doesn't see it at all, and going to the IP via the browser still doesn't connect.  Although the router shows as still be connected via the old IP, and it still pings fine.  SMB Client is also enabled.

[StephenB]

I should have asked before - is there any internet security software running on the PC (Norton, Avast, Kaspersky, etc).  If so, try disabling that, and see if it makes a difference.

One thing you can do is power down, and then connect one of the disks to a Windows PC, and install R-linux for Windows (free).  https://www.r-studio.com/free-linux-recovery/

That should let you off-load the data.  Once that is done, you can do a factory default on the Duo, rebuild it, and then restore the data.

[mladen5]

The only security is the windows default, tried turning this off but it made no difference unfortunately.  Onto recovery.....

With R-Linux, is it just a case of scanning the partition and going from there, is there no way to view the folder structure without scanning?  Will I need a drive the same size as the partition to dump it to, or will it allow me to choose only the files I want to save?  Just started the process and it seems slow going, only 400mb read after 5 minutes, with quite a few "Read Disk .....failed after 1 attempts. This request failed due to a fatal device hardware error (483)".

[StephenB]

---

@mladen5 wrote:

With R-Linux, is it just a case of scanning the partition and going from there, is there no way to view the folder structure without scanning?  Will I need a drive the same size as the partition to dump it to, or will it allow me to choose only the files I want to save? 

 I've never needed the software myself, but I believe you can choose the files you want to save.

---

@mladen5 wrote:

quite a few "Read Disk .....failed after 1 attempts. This request failed due to a fatal device hardware error (483)".

---

I suggest trying the other disk.

[mladen5 · Accepted solution]

Unfortunately it's the only disk.  Nevertheless, I decided to cancel the R-Linux scan which still brought up a red "Rocognized0" volume.  I right clicked on this to select "open drive files", and voila!  I can view the files in the existing folder structure and recover only those I want to keep.   I'll probably bin this one buy a more recent NAS which will hopefully be a tad more reliable.

Thanks for your help though, it is very much appreciated.

[StephenB]

---

@mladen5 wrote:

Nevertheless, I decided to cancel the R-Linux scan which still brought up a red "Rocognized0" volume.  I right clicked on this to select "open drive files", and voila!  I can view the files in the existing folder structure and recover only those I want to keep.   

---

Yes, harddiskVolume17 is the data volume.  15 is the OS partition, 16 is (I think) swap.  Temporary, in any event.

---

@mladen5 wrote:

 I'll probably bin this one buy a more recent NAS which will hopefully be a tad more reliable.

---

It is an old NAS (became end-of-life in 2013).  

But it looks to me like the issue here is actually the disk. In any event, the only way to protect against data loss is to back up the data to another device (RAID protection isn't enough, and of course you weren't using it anyway).

[mladen5]

Tried factory reset and now I get bad disk detected (see screenshot), is there any way to use this drive, or is it a write-off?

[mladen5]

For info, I'd replaced the disk with another showing as "healthy" and all appears to be working as it should.  The issue's I had seem to be the result of the WD Red drive failing as you thought.

[StephenB]

---

@mladen5 wrote:

Tried factory reset and now I get bad disk detected (see screenshot), is there any way to use this drive, or is it a write-off?

---

I'd say any disk that fails the self-test is a write-off.