Can't connect to the device

Legacy Products My Book Live
1

Preface to this being I’ve been using it just fine for about ~1 year and then sometime last week my My Book Live Duo seemed to become unreachable.  I’m unable to connect to the dashboard tools for it or connect to it through file explorer.  Initially I had just assumed its IP had changed so I checked the devices on my router but it was at the same IP as it has been.  I was able to ping it through CMD.  

I then brought out the installation disc to try and ‘discover’ the drive and only sometimes will it show up, but now the name of the drive is showing up as ‘/etc/nas/nasde’ and when I try to complete the setup it crashes out with a Setup exception (didn’t look into this too far as I assumed it wasn’t tied to the root of my problem?).  WD Quick View briefly shows it but now the drive name is changed from “My Book Live Duo” to “/etc/nas/nasde” with its Used % at 0% and temperature unknown.

Finally, I took the drives out of the container and connected them with an adapter to my PC to check them to see if that would reveal any issues.  Disk Management shows them both as having all healthy partitions but I’m assuming they’re formatted in Linux so I was unable to actually open the drives on my Windows PC.

Really unsure where to go from here, any thoughts?

2

Hi, have you tried connecting the My Book directly to the PC or  using another Ethernet cable? If the problem continues you can press the reset button on the back of the My Book for 4 seconds, this will not delete your files, it will just restore the My Book configuration back to default. You can also try using the WD Link tool to find the My Book on your network. Check the link below for the steps. 

Mapping a drive letter on a WD Network hard drive using WD Link

3

I tried swapping to a different Ethernet cable to see if that would help, as well as connecting to my PC using both ethernet cables but to no avail.  The Duo is just sitting at a constant yellow light and holding the reset button doesn’t seem to affect it / cause anything to happen.  It’s got me wondering if something with the enclosure itself is wrong as opposed to the drives?