Duo stops listening

What firmware is it currently on?
How full is the volume?
Have you checked the health of the disks using vendor tools?
Do you have ssh enabled?
Do you have a backup?

Sounds like a full OS partition (not the data volume).

If you have enough time, try deleting the logs in the short bootup window (first system, and then backup). Netgear (including mdgm) have other ways to do it.

Do you happen to have ssh installed?

I agree, just gathering as much info as possible. Full data volumes also seem to cause some problems albeit not as frequently as the dreaded full OS partition.

vandermerwe wrote:
I agree, just gathering as much info as possible. Full data volumes also seem to cause some problems albeit not as frequently as the dreaded full OS partition.

Our replies collided (I posted mine a couple of seconds after yours). I wasn't meaning to disagree; your requested info is relevant. If it is filling, then he does need to clear logs quickly.

Thanks for the replies

It was running 4.1.13

I now have sshd running

It is now running 4.1.14

System disk free is fine, data disks are fine

I pulled /var/log/syslog & messages (before the upgrade)

These (<<<) look odd around the period of a 'hang's

Oct 27 00:44:36 nas-66-05-64 syslogd 1.4.1#10: restart.
Oct 27 00:49:28 nas-66-05-64 syslogd 1.4.1#10: restart.
Oct 27 00:50:25 nas-66-05-64 kernel: chn=0, statu/LP_S=0x(d0/d050)29, 32
Oct 29 23:38:31 nas-66-05-64 kernel: chn=0, statu/LP_S=0x(d0/d050)29, 32
Oct 29 23:40:17 nas-66-05-64 syslogd 1.4.1#10: restart.
Oct 30 12:00:40 nas-66-05-64 syslogd 1.4.1#10: restart.
Oct 30 12:04:28 nas-66-05-64 syslogd 1.4.1#10: restart.
Nov 23 18:39:36 nas-66-05-64 kernel: rxS1(00720000),rxS0(011001ea) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Nov 23 18:59:23 nas-66-05-64 kernel: rxS1(00720000),rxS0(01100166) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Nov 23 19:06:49 nas-66-05-64 kernel: rxS1(00e20000),rxS0(018001d4) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dec  2 10:02:38 nas-66-05-64 kernel: + padre_power_down_task
Dec  2 10:02:55 nas-66-05-64 exiting on signal 15

Dec  3 22:06:13 nas-66-05-64 kernel: chn=0, statu/LP_S=0x(d0/d050)29, 32
Dec  3 22:09:13 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008205ee) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dec  3 22:22:58 nas-66-05-64 kernel: + padre_power_down_task
Dec  3 22:23:12 nas-66-05-64 exiting on signal 15

Dec  3 22:25:24 nas-66-05-64 kernel: hub 3-0:1.0: 2 ports detected
Dec  3 22:25:36 nas-66-05-64 usb.agent: ... no modules for USB product 0/0/206
Dec  3 22:25:39 nas-66-05-64 last message repeated 2 times
Dec  3 22:26:57 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008005ee) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dec  3 22:36:38 nas-66-05-64 kernel: + phy_irq 0400 repeated 1
Dec  3 22:36:38 nas-66-05-64 kernel: unlinked                                     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dec  3 22:36:45 nas-66-05-64 kernel: linked, 1000mbps mode               <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dec  3 22:39:22 nas-66-05-64 kernel: padre_power_down_task
Dec  3 22:39:31 nas-66-05-64 exiting on signal 15

grep "kernel: rxS1" messages gives (message starts in Jul):

Oct  9 09:08:06 nas-66-05-64 kernel: rxS1(00e20000),rxS0(0182021d)
Nov 23 18:39:36 nas-66-05-64 kernel: rxS1(00720000),rxS0(011001ea)
Nov 23 18:59:23 nas-66-05-64 kernel: rxS1(00720000),rxS0(01100166)
Nov 23 19:06:49 nas-66-05-64 kernel: rxS1(00e20000),rxS0(018001d4)
Dec  2 10:11:29 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008005ee)
Dec  2 10:31:10 nas-66-05-64 kernel: rxS1(005a0000),rxS0(001000dd)
Dec  2 10:31:11 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008200e2)
Dec  2 10:38:08 nas-66-05-64 kernel: rxS1(00e20000),rxS0(018001be)
Dec  2 20:00:02 nas-66-05-64 kernel: rxS1(00e20000),rxS0(008000f4)
Dec  2 20:15:34 nas-66-05-64 kernel: rxS1(005a0000),rxS0(001000f5)
Dec  2 20:24:10 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008005ee)
Dec  2 20:39:20 nas-66-05-64 kernel: rxS1(00e20000),rxS0(018001ca)
Dec  3 22:09:13 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008205ee)
Dec  3 22:26:57 nas-66-05-64 kernel: rxS1(00ca0000),rxS0(008005ee)
Dec  3 23:39:31 nas-66-05-64 kernel: rxS1(00e20000),rxS0(018001ea)

Are those rxS1 network related ???

Even running 4.1.14 it is still not right, - the last entry is under 4.1.14

It used to happily stream video (not HD) over 100mbps cat 5 (using hubs rather than switches) to my TV, put it doesn't any more. Very bursty with long pauses.

https://www.readynas.com/forum/viewtopi ... 24&t=76500 is almost identical

Google gives other similar symptoms not just for DUOs but only ReadyNAS



Example sample ping from the Duo:

64 bytes from 10.0.1.33: icmp_seq=313 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=314 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=315 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=316 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=317 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=318 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=319 ttl=128 time=3.12 ms
64 bytes from 10.0.1.33: icmp_seq=320 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=321 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=322 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=323 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=324 ttl=128 time=1.50 ms
64 bytes from 10.0.1.33: icmp_seq=325 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=326 ttl=128 time=98.1 ms
64 bytes from 10.0.1.33: icmp_seq=326 ttl=128 time=98.4 ms (DUP!) <<<<<<<<<<<<<<<<<<<<<<<< what ???
64 bytes from 10.0.1.33: icmp_seq=327 ttl=128 time=0.440 ms
64 bytes from 10.0.1.33: icmp_seq=328 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=329 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=330 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=331 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=332 ttl=128 time=255 ms
64 bytes from 10.0.1.33: icmp_seq=333 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=334 ttl=128 time=0.481 ms
64 bytes from 10.0.1.33: icmp_seq=335 ttl=128 time=29.2 ms
64 bytes from 10.0.1.33: icmp_seq=336 ttl=128 time=17.3 ms
64 bytes from 10.0.1.33: icmp_seq=340 ttl=128 time=93.8 ms
64 bytes from 10.0.1.33: icmp_seq=341 ttl=128 time=429 ms
64 bytes from 10.0.1.33: icmp_seq=342 ttl=128 time=1.56 ms
64 bytes from 10.0.1.33: icmp_seq=343 ttl=128 time=0.501 ms
64 bytes from 10.0.1.33: icmp_seq=344 ttl=128 time=101 ms

That dup makes no sense at all to me !!!!

Any more ideas (other than buy some new hardware)?

Thanks