Readynas Ultra 4 on OS6 unresponsive displays " sg_next+0"

Question

Hi guys,Just a heads up.&nbsp; My Ultra 4 Plus stopped responding twice and needed hard reboot. Both times it was the same error: eth0 stopped responding and display shows "sg_next+0".&nbsp;kernel.log contains lot's of those at the time when error occured:Jul 29 12:57:35 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyJul 29 12:57:36 nas-8B-83-CE kernel: eth0: network connection downJul 29 12:57:36 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readyJul 29 12:57:39 nas-8B-83-CE kernel: eth0: network connection up using port AJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; interrupt src:&nbsp;&nbsp; MSIJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; speed:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1000Jul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; autonegotiation: yesJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; duplex mode:&nbsp;&nbsp;&nbsp;&nbsp; fullJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; flowctrl:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; noneJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; role:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; slaveJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tcp offload:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; scatter-gather:&nbsp; enabledJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:39 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-polling:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:39 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyJul 29 12:57:40 nas-8B-83-CE kernel: eth0: network connection downJul 29 12:57:40 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readyJul 29 12:57:43 nas-8B-83-CE kernel: eth0: network connection up using port AJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; interrupt src:&nbsp;&nbsp; MSIJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; speed:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1000Jul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; autonegotiation: yesJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; duplex mode:&nbsp;&nbsp;&nbsp;&nbsp; fullJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; flowctrl:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; noneJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; role:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; slaveJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tcp offload:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; scatter-gather:&nbsp; enabledJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:43 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-polling:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:43 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyJul 29 12:57:44 nas-8B-83-CE kernel: eth0: network connection downJul 29 12:57:44 nas-8B-83-CE kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readyJul 29 12:57:47 nas-8B-83-CE kernel: eth0: network connection up using port AJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; interrupt src:&nbsp;&nbsp; MSIJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; speed:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1000Jul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; autonegotiation: yesJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; duplex mode:&nbsp;&nbsp;&nbsp;&nbsp; fullJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; flowctrl:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; noneJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; role:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; slaveJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tcp offload:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; scatter-gather:&nbsp; enabledJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; tx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-checksum:&nbsp;&nbsp;&nbsp;&nbsp; enabledJul 29 12:57:47 nas-8B-83-CE kernel:&nbsp;&nbsp;&nbsp;&nbsp; rx-polling:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enabled&nbsp;The error is similar to this case, except I was running later version 6.7.5:https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-Ultra-4-on-OS6-unresponsive-displays-quot-sg-next-0/td-p/1033802&nbsp;I had the NAS for a long time. What has changed during the last few months is that my router now supports both IPv4 and IPv6. It seem that there has been some confusion regarding IPv6 on eth0? I have now deactivated IPv6 in NAS and it is still working correct.IPv4 is set to static, but I assume IPv6 was received via DHCP? Is there something wrong with IPv6 in my router or is this internal OS6 issue?&nbsp;BR,

JennC · Answer

Hello&nbsp;Grunf,

&nbsp;

This discussion might help:

&nbsp;

https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-Ultra-4-on-OS6-unresponsive-displays-quot-sg-next-0/td-p/1033802

&nbsp;

Regards,

Grunf · Answer

Thanks for the link but I have already read it. It is not much of a discussion really: somebody had the same issue and "resolved it" by holding the power button long enough for NAS to reboot. "Reboot it when it happens" is not really a remedy, is it?

What I am trying to say is that this is likely caused by kernel running out of memory in some buffer, triggered by IPv6 adress conflict. And I am looking forward to discuss it with somebody who can interpret kernel log.

BR

mdgm-ntgr · Answer

You're running OS6 on legacy hardware. Seeing it works fine with IPv6 disabled, I think that's a more than acceptable workaround for an unsupported use of OS6.

Forum Discussion

Readynas Ultra 4 on OS6 unresponsive displays " sg_next+0"

3 Replies

Related Content

Readynas Ultra 4 on OS6 unresponsive displays " sg_next+0"

Unresponsive RN214

ReadyNAS 104 Unresponsive after 1.30 Hours

Readynas 1100 unresponsive - quota check?

R7800 unresponsive on 2.4Ghz

NETGEAR Academy

ProSupport for Business