Hi all, Last night my RNPP (Pro Pioneer) dropped off my LAN completely. Couldn't browse via Explorer, Web interface (Frontview), RAIDar or anything. My only option was to shut it down hoping it'd show up on the network, which it did. Nothing in logs about it either..and since the power button worked I'm assuming it was operational.
Today morning, I wake up to find my NV+ has done the same thing...its too much of a coincidence to be the NAS itself that are dropping from the network. Any ideas?
The front LED (RNPP) pops up when I unplug - replug the LAN cable, the switch shows the LED as an active connection...yet it won't ping or anything.
Totally lost.
*edit* Update 1 After reading way too many people suffering the same issue, here are some updates as to my setup (besides whats in my sig)
Both NAS are Static IP Both NAS are connected to same switch, which all other devices are also connected to (Laptop, PC x2 - all Win7 based)
Both NAS: The Enable disk spin-down… option is NOT checked. The Power Timer is NOT checked The Wake-on-LAN is disabled No cable teaming iTunes Streaming Server, SqueezeCenter, ReadyDLNA, Bonjour service = OFF No BitTorrent client running. UPnP = ON RSync = OFF
Switch shows the device as connected (green light for 1000mbit, orange for 100mbit) NAS display panel shows as lost network link if I unplug the eth cable and after I plug it back in, the IP shows again as it should be (Static and exactly what I’ve set)
RNPP - 1 disk changed due to high re-allocated sector count. This was a day before it dropped from the network. After it was dropped from the network, the only way to bring it back was to use the power button on the front, shutdown and then start it up again. So yes, the front power button did work, unlike some of the others who've had to do a cold reboot by turning off the power. NV - No change at all, device has been working fine since the PSU replacement some months ago.
*edit* Update 2 Since I couldn't figure out anything with the NV+ also dropping off and its front power button does nothing, I'm assuming its frozen...so a cold boot done, its now doing a full FS check.
Just happened again on the RNPP. I decided to try a few things, what worked was using eth1 instead of eth0. Seems for some reason eth0 likes to just stop working. Unfortunately this solution wont work on my NV+ as it has only 1x eth port. I'll eventually have to reboot the RNPP as I fear that eth1 might stop working in the near future and the reboot is all that solves it all.
I'm reviving this old thread of mine because I'm having similar symptoms yet again.
As per advice from a friend, I had (painfully, I don't have a few TB of space lying around) done a factory reset in the hopes that the above issue would go away, it did...but after a few months I changed all the Hard Disks and so I really don't know if I fixed it earlier, just that it hadn't happened YET.
A month now since I've had these WD Reds and last week I had a network drop out issue again, the port lights weren't blinking and logs are as follows http://pastebin.com/1Vwk7Dp3
Based on my timeline, this would be the offending log that shows it dropped off:
Nov 22 06:25:03 READYNASMEDIA syslogd 1.4.1#18: restart. Nov 23 00:15:50 READYNASMEDIA kernel: eth0: network connection down Nov 23 00:15:50 READYNASMEDIA ifplugd(eth0)[2636]: Link beat lost. Nov 23 00:15:51 READYNASMEDIA ifplugd(eth0)[2636]: Executing '/etc/ifplugd/ifplugd.action eth0 down'. Nov 23 00:15:51 READYNASMEDIA avahi-daemon[3103]: Withdrawing address record for 10.0.0.166 on eth0. Nov 23 00:15:51 READYNASMEDIA avahi-daemon[3103]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.0.166. Nov 23 00:15:51 READYNASMEDIA avahi-daemon[3103]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 23 00:15:52 READYNASMEDIA ifplugd(eth0)[2636]: client: No udhcpc found running; none killed. Nov 23 00:15:52 READYNASMEDIA ifplugd(eth0)[2636]: Program executed successfully.
Is it a bad network cable/connection? Because I unplug it, re-plug into Ethernet port 2 (as you can see from logs) and it works...
Just now I saw Ethernet port 2 is down and I had to plug into Ethernet port 1 again for it to work. :?
