Hi, I think I have some Network problems with a NetGear Nv+ 4000 RND4000 NAS.
When it startup, everything is ok, but after some minutes, I loose any communication with it, and have to shut down (press button until "shutting down" message) and start it again.
I thought that maybe another machine have same IP, but it's strange cause it's in a different subnet (192.168.100.x others machines 192.168.1.x, and yes, I use 255.255.0.0). I discard Ip conflict.
I have this problem since I update to last firmware, RAIDiator - 4.1.10 - Sat Aug 25 00:55:19 2012 - 62948864
Anyone have any ideas how to test or solve this problem?
Thanks
Edited, some /var/log/syslog, I think problem section (changed some personal values):
Nov 6 18:39:50 MyNas avahi-daemon[1001]: Found user 'MyAdminUser' (UID XX) and group 'MyAdminGRP' (GID YY). Nov 6 18:39:50 MyNas avahi-daemon[1001]: Successfully dropped root privileges. Nov 6 18:39:50 MyNas avahi-daemon[1001]: avahi-daemon 0.6.15 starting up. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Loading service file /etc/avahi/services/afp.service. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Loading service file /etc/avahi/services/cifs.service. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Loading service file /etc/avahi/services/frontview.service. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Loading service file /etc/avahi/services/readyMyNas.service. Nov 6 18:39:50 MyNas avahi-daemon[1001]: New relevant interface eth0.IPv4 for mDNS. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Network interface enumeration completed. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Registering new address record for 192.168.X.Y on eth0. Nov 6 18:39:50 MyNas avahi-daemon[1001]: Registering HINFO record with values 'PADRE'/'LINUX'. Nov 6 18:39:50 MyNas kernel: ::chn=1, statu/LP_S=0x(d0/d050)29, 16 Nov 6 18:39:51 MyNas avahi-daemon[1001]: Server startup complete. Host name is MyNas.local. Local service cookie is 3436221296. Nov 6 18:39:52 MyNas avahi-daemon[1001]: Service "ReadyMyNas Discovery [MyNas]" (/etc/avahi/services/readyMyNas.service) successfully established. Nov 6 18:39:52 MyNas avahi-daemon[1001]: Service "FrontView on MyNas" (/etc/avahi/services/frontview.service) successfully established. Nov 6 18:39:52 MyNas avahi-daemon[1001]: Service "MyNas (CIFS)" (/etc/avahi/services/cifs.service) successfully established. Nov 6 18:39:52 MyNas avahi-daemon[1001]: Service "MyNas (AFP)" (/etc/avahi/services/afp.service) successfully established. Nov 6 18:39:57 MyNas syslogd 1.4.1#10: restart. Nov 6 18:40:18 MyNas kernel: ::GMAC: 37640300; GMT: 00000000; DMA RX: 0000c009; DMA TX: 00008009 Nov 6 18:40:18 MyNas kernel: Trying to free free IRQ17 Nov 6 18:40:18 MyNas avahi-daemon[1001]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 6 18:40:18 MyNas avahi-daemon[1001]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:18 MyNas avahi-daemon[1001]: Withdrawing address record for 192.168.X.Y on eth0. Nov 6 18:40:20 MyNas kernel: linked, 1000mbps mode Nov 6 18:40:20 MyNas avahi-daemon[1001]: New relevant interface eth0.IPv4 for mDNS. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Registering new address record for 192.168.X.Y on eth0. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Withdrawing address record for 192.168.X.Y on eth0. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:20 MyNas avahi-daemon[1001]: iface.c: interface_mdns_mcast_join() called but no local address available. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 6 18:40:20 MyNas avahi-daemon[1001]: New relevant interface eth0.IPv4 for mDNS. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Registering new address record for 192.168.X.Y on eth0. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Withdrawing address record for 192.168.X.Y on eth0. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:20 MyNas avahi-daemon[1001]: iface.c: interface_mdns_mcast_join() called but no local address available. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 6 18:40:20 MyNas avahi-daemon[1001]: New relevant interface eth0.IPv4 for mDNS. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.X.Y. Nov 6 18:40:20 MyNas avahi-daemon[1001]: Registering new address record for 192.168.X.Y on eth0. Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: Listening on 192.168.X.Y:50000 Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: setsockopt - IP_ADD_MEMBERSHIP: Address already in use Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: Failed to add membership for address 192.168.X.Y Nov 6 18:40:44 MyNas kernel: :<6>ehci_hcd 0000:00:17.2: EHCI Host Controller Nov 6 18:40:44 MyNas kernel: ehci_hcd 0000:00:17.2: new USB bus registered, assigned bus number 1 Nov 6 18:40:44 MyNas kernel: ehci_hcd 0000:00:17.2: irq 27, io mem 0x5c010000 Nov 6 18:40:44 MyNas kernel: ehci_hcd 0000:00:17.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 Nov 6 18:40:44 MyNas kernel: usb usb1: configuration #1 chosen from 1 choice Nov 6 18:40:44 MyNas kernel: hub 1-0:1.0: USB hub found Nov 6 18:40:44 MyNas kernel: hub 1-0:1.0: 4 ports detected Nov 6 18:40:45 MyNas kernel: USB Universal Host Controller Interface driver v3.0 Nov 6 18:40:45 MyNas kernel: PCI: VIA IRQ fixup for 0000:00:17.0, from 0 to 11 Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.0: UHCI Host Controller Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.0: new USB bus registered, assigned bus number 2 Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.0: irq 27, io base 0x5c001000 Nov 6 18:40:45 MyNas kernel: usb usb2: configuration #1 chosen from 1 choice Nov 6 18:40:45 MyNas kernel: hub 2-0:1.0: USB hub found Nov 6 18:40:45 MyNas kernel: hub 2-0:1.0: 2 ports detected Nov 6 18:40:45 MyNas kernel: PCI: VIA IRQ fixup for 0000:00:17.1, from 0 to 11 Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.1: UHCI Host Controller Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.1: new USB bus registered, assigned bus number 3 Nov 6 18:40:45 MyNas kernel: uhci_hcd 0000:00:17.1: irq 27, io base 0x5c001020 Nov 6 18:40:45 MyNas kernel: usb usb3: configuration #1 chosen from 1 choice Nov 6 18:40:45 MyNas kernel: hub 3-0:1.0: USB hub found Nov 6 18:40:45 MyNas kernel: hub 3-0:1.0: 2 ports detected Nov 6 18:41:00 MyNas usb.agent: ... no modules for USB product 0/0/206 Nov 6 18:41:03 MyNas last message repeated 2 times Nov 6 18:41:33 MyNas ntpdate[1353]: can't find host time-e.netgear.com Nov 6 18:42:29 MyNas ntpdate[1353]: can't find host time-h.netgear.com
Maybe this is the error: Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: Listening on 192.168.X.Y:50000 Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: setsockopt - IP_ADD_MEMBERSHIP: Address already in use Nov 6 18:40:36 MyNas upnpd(eth0)[1367]: Failed to add membership for address 192.168.X.Y
192.168.100.x and 192.168.1.x with a 255.255.0.0 ARE in the same subnet. Looking at the part of the log you posted I would say that you are getting an IP Conflict.
Are you using DHCP or a static IP address on the ReadyNAS? If static IP address, have you reserved that IP address or set the DHCP pool to not have the ReadyNAS IP Address?
If you could PM me your logs I can verify if it's an IP Address conflict or not.
In the mean time try statically setting your ReadyNAS IP Address and making sure it is an address not served up by the DHCP server.
All machines on network use 192.168.1.x, and any router or DHCP use this "network". All servers (with statics IP's) use 192.168.100.x, and there is not any router or any using DHCP with 192.168.100.x .
After reboot yesterday, this morning still have not problems, ssh and view log, and a few minutes again system hang up. This is log (first block of "code" are the last lines I watch with "tail -f /var/log/syslog", second one are after reboot)
Nov 8 20:00:06 MyNas ntpdate[2880]: step time server A.B.C.D offset 0.025744 sec Nov 9 04:00:06 MyNas ntpdate[3591]: step time server A.B.C.D offset 0.114688 sec Nov 9 06:25:28 MyNas syslogd 1.4.1#10: restart. Nov 9 06:25:31 MyNas ntpdate[4201]: step time server 209.249.181.23 offset 0.028534 sec Nov 9 08:00:05 MyNas ntpdate[4352]: step time server A.B.C.D offset 0.026888 sec Nov 9 09:28:48 MyNas kernel: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::nEOP Nov 9 09:28:48 MyNas kernel: rxS1(00a20000),rxS0(018001f4)
Nov 9 09:29:59 MyNas kernel: + ::padre_power_down_task Nov 9 09:30:00 MyNas init: Switching to runlevel: 0 Nov 9 09:30:08 MyNas exiting on signal 15 Nov 9 09:32:28 MyNas syslogd 1.4.1#10: restart. ....
I still are looking for any machine that can cause a IP collide.
With out the full set of logs it will be very difficult to determine what is causing the issue. Please PM the full zip file of logs so I can review them to find the problem.
