2nd Ethernet port not working on TS-469L

[ballza]

Hi, There are 2 ethernet ports on my NAS and a little while back one of them stopped working. I'm thinking a storm/lightning may have damaged it. I was able to configure the other port so I could access the NAS.
Under control panel, network on my NAS there used to be both ethernet ports listed here, now there is only one. Not sure how this happened, but again it was probably a couple of years back now.

I'm worried if I ever loose the other ethernet port I will never get access to the NAS again. Is there some way to replace the ethernet port, or has it been disabled accidentally somehow.

Any help would be much appreciated.

Thanks.
Anthony

If it's a technical question of any kind, please remember to include:

Your Operating System you are using to access your NAS. Windows 10 Pro 64Bit
NAS model TS-469L
Firmware Version/Build numbers - not just "The latest" 4.2.3 (13-2-17)
Network Setup (ie Single Port or Port Trunking) Single port

[OneCD]

Hi, There are 2 ethernet ports on my NAS and a little while back one of them stopped working.

To help diagnose this, you'll need to SSH / PuTTY into your NAS as the 'admin' user to access the command line.

Then please run the following and post the output back here (copy and paste):

Code: Select all

ifconfig -a; echo; dmesg | grep eth0; echo; dmesg | grep eth1

Firmware Version/Build numbers - not just "The latest" 4.2.3 (13-2-17)

Good to see.

[ballza]

Hi OneCD, result as follows;

[~] # ifconfig -a; echo; dmesg | grep eth0; echo; dmesg | grep eth1
bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:08:9B:E4:30:6E
inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:256616518 errors:0 dropped:335639321 overruns:0 frame:0
TX packets:509403862 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19485837956 (18.1 GiB) TX bytes:769115456049 (716.2 GiB)
Interrupt:19 Memory:c0100000-c0120000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3627289 errors:0 dropped:0 overruns:0 frame:0
TX packets:3627289 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:878887344 (838.1 MiB) TX bytes:878887344 (838.1 MiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:1280 (1.2 KiB)


[ 127.775973] 8021q: adding VLAN 0 to HW filter on device eth0
[ 130.781452] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 135.303999] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

[OneCD]

That dmesg output isn't encouraging.

Next thing would be try it again with just the Intel driver name:

Code: Select all

dmesg | grep e1000e

[ballza]

I'm assuming that as ethernet port 1 is not mentioned, it is dead?

[~] # dmesg | grep e1000e
[ 130.781452] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 135.303999] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

[OneCD]

That's how it looks to me.

Although, eth1 should be the second NIC discovered, so you'll only see eth1 if the OS was able to find eth0.

I think that NIC is dead. Unless another forum member can suggest something else to test for?

[ballza]

Thanks very much for your help.

I'm thinking the NIC would be part of the motherboard in this unit so you wouldn't be able to replace it...?

[OneCD]

I'm thinking the NIC would be part of the motherboard in this unit so you wouldn't be able to replace it...?

Well, not from here. My arms are only so long.

They are on the system board (the two large, square chips in this photo):

[ballza]

LOL.

That might be a difficult solder job......

[ja666]

It also happened with 1st ethernet port of my TS-269L, when one of the system updates (Autumn 2016) failed as hanged-on at 35% (AFAIR).
I was fortunate I could access QTS through Hybrid Desk Station (HDMI monitor + USB keyboard & mouse) with no access through www browser (due to ongoing update hanged-on at 35% as above).
So using Hybrid Desk Station I switched QTS to 2nd ethernet port and then backed-up all the data to the external disk, and then made complete system reset from scratch (with formatting & initialising both HDDs).
After system restore, 1st ethernet port works as new.


-----

There are 2 ethernet ports on my NAS and a little while back one of them stopped working.

[jldurham6]

I've got the same problem. Reset my uLinux.conf file and no luck. I'm not aware of any power failures etc, I just noticed when I unplugged eth0 that the light stays on. Oddly enough eth1 actually gets assigned as eth0. Might try a complete backup of data and reload one of these days just to see. Bummed there's no way to replace or add a NIC.

[gggplaya]

You could add a stubby wirelessAC usb dongle to the NAS, that way if you do lose the ethernet port, you have a redundancy to still connect to the NAS. Just make sure you check the compatibility list to see what works on your NAS.

My 2nd ethernet port stopped working after the 4.3 update, they changed some things with the Vlan switching.

[rico666]

Same here, although my dmesg looks like

[770496.469939] e1000e 0000:04:00.0: eth1: Unable to allocate memory for the receive descriptor ring
[770496.618066] e1000e 0000:04:00.0: eth1: Unable to allocate memory for the receive descriptor ring

edit: reboot and/or FW upgrade fixed it.