ReadyNas 104 - eth0 issues (unable to 1000/full duplex)
Hello,
I've taken off the shelf my old RN104 and I've ugraded it to the latest os, no issues.
ReadyNAS was connected directly to the netgear router got a connection, no issues.
I've then moved to configure my cisco 7350, regular port channel, access mode. I've multiple bond on this 24 port switch and they all work as expected, LACP 802.3ad port channels. The issue came to light when the readynas was connected to it. ETH0 (the port used on the router) refuses to blink. No detection on the switch, no messages in the kernel.
All tests that succeed on the second port fail on the first, when I connect eth0 to RN104 to the Nighthawk router, connection does happen, dhcp works, I get an address, however the avertised speed is "100mb/s Full Duplex" while the router can provide 1Gps (ish...). I've tried ethtool to negotiate duplex and speed, tested countless cables and tried and tried. Changing the port to 100mb/s full duplex gets connectivity, Cisco switch is 100% working, ports work well with multiple devices and cisco ports have been configured in a bond and worked as expected on multiple devices.
What looks to me is that eth0 is flapping, running multiple ethtool command lines in successions shows weird behaviour.
root@netnas:~# ethtool 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 Speed: 1000Mb/s Duplex: Half Port: MII PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: no
root@netnas:~# ethtool 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: No Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Half Port: MII PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: no root@netnas:~#
root@netnas:~# ethtool 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 Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: g Wake-on: d Link detected: yes
Then I get in the kernel multiple times in sequence.
Oct 08 22:44:51 netnas connmand[2085]: eth0 {newlink} ignoring slave, index 2 address 28:C6:8E:36:87:8B Oct 08 22:44:51 netnas kernel: mvneta d0070000.ethernet eth0: Link is Down Oct 08 22:44:51 netnas kernel: bond0: link status definitely down for interface eth0, disabling it Oct 08 22:44:54 netnas connmand[2085]: eth0 {newlink} ignoring slave, index 2 address 28:C6:8E:36:87:8B Oct 08 22:44:54 netnas kernel: mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Oct 08 22:44:54 netnas kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
Cisco Configuration for reference
interface GigabitEthernet1/0/7 description netnas.1 switchport access vlan 24 switchport trunk encapsulation dot1q switchport mode access channel-protocol lacp channel-group 3 mode active no shut ! interface GigabitEthernet1/0/8 description netnas.2 switchport access vlan 24 switchport trunk encapsulation dot1q switchport mode access channel-protocol lacp channel-group 3 mode active no shut ! interface Port-channel3 switchport access vlan 24 switchport trunk encapsulation dot1q switchport mode access no ip address no shut !
Re: ReadyNas 104 - eth0 issues (unable to 1000/full duplex)
It could be something in the NIC socket on the RN104, or an internal wiring failure in the NAS. Fast ethernet doesn't use all the pairs in the wiring, so internal failed connections could explain why gigabit ethernet negotiation fails.
It is a puzzle why you get no connectivity at all with the Cisco switch, but you do with the nighthawk. Did you try connecting eth0 with no bonding configured on either end?
The net here is that if the issue is internal to the NAS (which is what it looks like), then it is likely unrepairable. If the NAS is under warranty (3 years), then you can ask for an RMA via my.netgear.com.
You could of course give up on bonding - there isn't much (if any) gain on the RN104. Normally its performance is limited by the CPU and memory.
Re: ReadyNas 104 - eth0 issues (unable to 1000/full duplex)
Thank you Stephen,
I can connect to the cisco router if and only if I set 100mb/s full duplex. Reason for the bond is mostly for redundancy and if possible the speed benefit, the nas is definitely not in warranty it's prior 2014. Make it easy to maintain. I wasn't even trying to do the ports scross the LAG XD
I'll check the circuitery, give it a nice alchol clean, maybe the dust is playing up. I did not think to check out what pairs were used for the different speed, man I got rusty.
I found an old kernel bug for ARMADA cpu where Marvell were flapping and there was a miss identification of the PHY device... took me way out the problem 🙂 bloody occam scissor.
I'll open the box as soon as disk sync is done, any alternative firmware you would reccomend for the RN104? the ui is fancy, but I can't get pass btrFS, I've put this on the shelf after a power loss that caused the whole array to die.
See you in 120h or 60h, or 190h. RN is very confused.
I'll open the box as soon as disk sync is done, any alternative firmware you would reccomend for the RN104? the ui is fancy, but I can't get pass btrFS,
I don't know of alternative firmware.
@valk1 wrote: Also, any idea of the pin out of what it seems a UART connector?
