NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JadeMonkee
Nov 25, 2015Aspirant
ReadyNAS Duo (v1) leaking current over ethernet cable
Hello, I have had many good years' use out of my now outdated ReadyNAS Duo. After recently moving overseas and having the item shipped here with the rest of my stuff, upon first boot (back in Sept...
StephenB
Nov 25, 2015Guru - Experienced User
JadeMonkee wrote:
Ok:
I just hope that it's not been damaging any of the other equipment attached to my switch.
Again, you are jumping to an electrical root cause. It could be something else altogether. A packet storm of some sort (or simply a failed switch).
What else is connected to the switch?
Also (assuming the electrical theory) - is the NAS using the same power circuit as the PC?
JadeMonkee
Nov 25, 2015Aspirant
I appreciate your thoroughness, thanks. In answer to your questions:
The PC is battery powered. The problem occurs when it is connected via AC (official adapter) or by battery only.
Connected to the switch:
1x Wifi extender
1x Ethernet over Power adapter
1x Arm-based server (CubieTruck)
1x ReadyNAS Duo
1x Macbook Air (via thunderbolt ethernet)
Note that, as these all have Australian plugs and I am now in the UK, all of these (with the exception of the PoE) are connected to one Australian power board, which has an AU > UK adapter attached.
The PoE (which has a UK plug) is running on the power socket next to where the power board plugs in.
I have just powered off and disconnected everything except the Mac and the NAS from the switch, and powered the NAS back up.
The touchpad seems fine so far, but I can't connect to the NAS to run the fan recalibration (which previously made the problem re-appear), as there is no connection between the NAS and the DHCP server/router.
I shall now connect the WiFi extender.
Woah. Immediately upon connecting the WiFi extender's ethernet cable, the problem re-appeared.
I shall now connect the WiFi extender using a different cable.
Notably, after disconneting the WiFi extender, the problem didn't go away.
After disconnecting the NAS (without the WiFi extender connected) it did go away.
After plugging in the WiFi extender (NAS disconnected) the problem doesn't manifest.
Immediately upon reconnecting the NAS, it appears.
While leaving the NAS connected to the switch, I shut the NAS down. Trouble instantly disappears as I hear the NAS click off.
I turn the NAS back on (the WiFi extender is still connected, as is my Mac), the problem doesn't instantly re-appear. But appears as I hear disk 1 spin up, calms for a moment. Then disk 2 spins up. Then acts up. Them calms down again. Then comes back as before.
I disconnect the NAS, and the problem immediately goes away.
I hope this helps.
- JadeMonkeeNov 25, 2015Aspirant
Oh, one more thing:
The main household recently upgraded their router to a TP-Link Archer D9.
I'm not a great fan of TP-Link, and these feelings have continued since they installed this router.
It's DNS is terrible: almost nothing on the network can find anything using its host name - I have to use an IP address.
For instance, to SSH into one Raspberry Pi from my Mac, I used to be able to type the command 'ssh pi@max2play' but now I have to type 'ssh pi@192.168.1.139'. Similarly, I used to be able to type in http://max2play/ to my browser to access its web config interface. Now I have to type in its IP address.
Curiously, on my OpenELEC Raspberry Pi, it references the movies stored on the NAS as directories using its host name, rather than its IP address. These largely (though not flawlwessly) still work. Although connecting to http://abernathy/admin doesn't (ERR_NAME_NOT_RESOLVED).
Given that you suspect that it could be a packet flood problem, is it at all possible that the NAS is polling the router like crazy to try and establish its own host name?
Extra curiosity: I just reconnected the NAS to the switch (it's been on but disconnected the last 10 minutes) and the problem with my touchpad didn't appear until I tried logging into Frontview. Then it happened.
EDIT: I bumped the power board's connection to the power socket and I heard my NAS fan spin up, as if it just shutdown for a second. I'm just now going to find a new kettle cable with a UK plug so that I can connect it directly to the wall, rather than to the power board.
- JadeMonkeeNov 25, 2015Aspirant
Upon connecting the NAS directly to the wall (rather than through a power board and a AU > UK adapter) the problem hasn't manifested on my Mac.
Now, what's really interesting is that the NAS now reports that my new fan isn't working (I can see it spinning, but it says 'out of spec' on the status page).
So, is it then possible that a surge or spike similar to what just happened and caused my NAS to instantly reboot was the problem the first time I got the fan error?
I have now shutdown my NAS, and am about to boot it back up in the hopes that it doesn't report a fan error.
NAS is now booting: no touchpad problems as hard drives spin up.
Fan is reported as working at 1973 RPM.
Booted the CubieTruck connected to the switch, still no touchpad problems.
This is wonderful news: could this all be because of an AU > UK power adapter, or a dodgy power board?
Perhaps also worth noting: when I plugged in the new UK cable, the power brick on the NAS was rather hot to touch. I don't know if this is normal or not.
- JadeMonkeeNov 25, 2015Aspirant
Ok, just to add some completion to this:
Using the same powerboard, I swapped over to a different AU > UK adapter, and the problem hasn't yet reappeared.
Big thanks, StephenB, for helping me test some of the assumptions I'd made and guiding me to a solution.
I am so happy that my ReadyNAS Duo is still going strong!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!