NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

JimboDumbo's avatar
JimboDumbo
Aspirant
Feb 23, 2019

ReadyNAS 102: network link is 100 mbit instead of 1000 mbit (gbit)

Hello!

 

ReadyNAS 102, Firmware: 6.9.5

 

Today I had found that large data from my nas ReadyNAS 102 is copied with the speed about 8-9 Mb/s, so it is exactly equal to the LAN = 100 Mbit (Mbps) instead of 1000 Mbit (Mbps) (1gbit). I can't say exactly when this had occured, because mostly I had worked with a small files and rarely, so if it was about 8-9 Mb/s (instead of 60-80 Mb/s) - it was enough.

 

On the rear panel of my ReadyNAS 102 I see two LEDs. The left one (green) is off, and the right one (yellow, amber) is blinking. As I see in documentation of ReadyNAS 102 it means, here is a quote:

 

Two LED status indicators are built into this port, one green and one amber. They
indicate port speed and activity as follows:
• Green on, amber off. 1000 Mbps connection speed, no activity.
• Green blinking, amber off. 1000 Mbps connection speed, activity.
• Green off, amber on. 10 Mbps or 100 Mbps connection speed, no activity.
• Green off, amber blinking. 10 Mbps or 100 Mbps connection speed, activity.
• Green off, amber off. No connection.

 

So, it is actually means that I have a connection for a 100 Mbps instead of 1000 Mbps. But... why?

 

In the admin panel of the ReadyNAS 102 I see:

Name: eth0
Bandwidth (Mbps): 1000
MTU: 1500

Here is a some log after ReadyNAS 102 restart:

Feb 24 00:33:10 NASHOST kernel: md: md127 stopped.
Feb 24 00:33:10 NASHOST kernel: md: bind<sdb3>
Feb 24 00:33:10 NASHOST kernel: md: bind<sda3>
Feb 24 00:33:10 NASHOST kernel: md/raid1:md127: active with 2 out of 2 mirrors
Feb 24 00:33:10 NASHOST kernel: md127: detected capacity change from 0 to 2995624607744
Feb 24 00:33:10 NASHOST kernel: BTRFS: device label xxxxxxxx:data devid 1 transid 327348 /dev/md127
Feb 24 00:33:10 NASHOST kernel: Adding 523964k swap on /dev/md1.  Priority:-1 extents:1 across:523964k 
Feb 24 00:33:32 NASHOST kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 24 00:33:36 NASHOST kernel: mvneta d0074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Feb 24 00:33:36 NASHOST kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

 

I think words "ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx" means 1 gbit.

 

So... why?

 

I had connected my ReadyNAS 102 as experiment directly to my notebook with another one cable (just to be sure, that there are no issues with the switch and/or with the cable). What I see? In the Windows "Network Connections", adapter status (connection status) it is written as "1 Gbit". On the notebook network card I see left green LED is on, and right yellow (amber) LED is blinkg - that is mean really 1 Gbit connection. But ReadyNAS 102 rear panel network card's LEDs are the same: left green LED is off, right yellow (amber) LED is blinking, what is mean the 10/100 Mbit connection. And, of course, copying files from ReadyNAS 102 to my notebook (.avis and other large files, etc) - 8-9 Mb/s as 100 Mbit connection.

 

Here is some other log from NAS:

eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          inet addr:192.168.0.22  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:33904 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18963 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532 
          RX bytes:3291303 (3.1 MiB)  TX bytes:572141398 (545.6 MiB)
          Interrupt:26 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:58 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:4218 (4.1 KiB)  TX bytes:4218 (4.1 KiB)

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.0.6    0.0.0.0         UG        0 0          0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.0.6    0.0.0.0         255.255.255.255 UH        0 0          0 eth0
Settings for eth0:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Half 1000baseT/Full 
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Half 1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Link partner advertised link modes:  10baseT/Half 10baseT/Full 
	                                     100baseT/Half 100baseT/Full 
	                                     1000baseT/Full 
	Link partner advertised pause frame use: Symmetric
	Link partner advertised auto-negotiation: Yes
	Speed: 1000Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 0
	Transceiver: external
	Auto-negotiation: on
	Supports Wake-on: g
	Wake-on: g
	Link detected: yes
/net/connman/service/ethernet_xxxxxxxxxxxx_cable
  Type = ethernet
  Security = [  ]
  State = ready
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = Wired
  Ethernet = [ Method=auto, Interface=eth0, Address=xx:xx:xx:xx:xx:xx, MTU=1500 ]
  IPv4 = [ Method=manual, Address=192.168.0.22, Netmask=255.255.255.0, Gateway=192.168.0.6 ]
  IPv4.Configuration = [ Method=manual, Address=192.168.0.22, Netmask=255.255.255.0, Gateway=192.168.0.6 ]
  IPv6 = [  ]
  IPv6.Configuration = [ Method=off ]
  Nameservers = [ 192.168.0.6 ]
  Nameservers.Configuration = [ 192.168.0.6 ]
  Timeservers = [ 192.168.0.6, time-e.netgear.com, time-a.netgear.com ]
  Timeservers.Configuration = [  ]
  Routes = [  ]
  Routes.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [ Method=direct ]
  Proxy.Configuration = [  ]
  Provider = [  ]

Any ideas what to do?

What is may be?

 

Is network card in NAS partially damaged/corrupted, so it works only as 100 Mbit instead 1000 Mbit?

 

Please help me to understand the issue and fix it if possible.

3 Replies

  • StephenB's avatar
    StephenB
    Guru - Experienced User

    It's odd that the LED status is out-of-sync with the logs.  

     

    I'd begin by rebooting the NAS, and then try a different ethernet cable. 

     

    The NIC in the ReadyNAS can't be repaired - so you might also want to check your warranty status.  The hardware warranty is 3 years for the original purchaser (and is not transferable).

    • JimboDumbo's avatar
      JimboDumbo
      Aspirant

      > It's odd that the LED status is out-of-sync with the logs.

       

      Yep, it is strange.

       

      > I'd begin by rebooting the NAS, and then try a different ethernet cable. 

       

      I had wrote that I done all of this. I had shutted down the NAS, removed AC cable to be sure that it is really powred off, and then booted it again. The same. :(

       

      I had used another ethernet cable and connected NAS directly to the notebook (more details are written in my first post) - the same behavior :(

       

      > The NIC in the ReadyNAS can't be repaired - so you might also want to check your warranty status.  The hardware warranty is 3 years for the original purchaser (and is not transferable).

       

      That's very strange, because it just a common NIC, as I understand. Or it is totally embedded to the NAS motherboard?

       

      Warranty is expired, because I bought that NAS at 2015 or something. :(

       

      Thank you.

      • Sandshark's avatar
        Sandshark
        Sensei - Experienced User

        The NIC is embedded.  There are no replacement parts available for ReadyNAS products. Even if you have the soldering skills and equipment, the part is not readily available in single quantities from any source.

         

        It does sound to me like your NIC is faulty, though just a bad connector is also a possibility.  I have a Duo V2 that does the same thing that was damaged by a power surge.

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More