After upgrade to 3.5.7.RKU2, 10Gbps interface are "unplugged"

[dstel]

Hello,

I connected to the administration of my NAS (through the bond of interface 1 and 2) and there was a popup about a new update of ADM. I clicked. After reboot, the NAS was not reachable. I had to connect with interface 3 that I manually connected for the occasion.

With this new connection, I can connect to the administration and see that the bond of 1 and 2 is offline because interface 1 and 2 are "unplugged".

Here is ip adress output:

Code: Select all

# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 10:bf:48:8d:d0:c2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 10:bf:48:8d:d0:c3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.81/24 brd 192.168.2.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 2a01:cb00:8d7:7a00:12bf:48ff:fe8d:d0c3/64 scope global dynamic 
       valid_lft 1786sec preferred_lft 586sec
    inet6 fe80::12bf:48ff:fe8d:d0c3/64 scope link 
       valid_lft forever preferred_lft forever
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP800> mtu 1500 qdisc mq master bond0 qlen 1000
    link/ether 10:bf:48:8d:d0:c0 brd ff:ff:ff:ff:ff:ff
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP800> mtu 1500 qdisc mq master bond0 qlen 1000
    link/ether 10:bf:48:8d:d0:c0 brd ff:ff:ff:ff:ff:ff
6: bond0: <NO-CARRIER,BROADCAST,MULTICAST,UP400> mtu 1500 qdisc noqueue qlen 1000
    link/ether 10:bf:48:8d:d0:c0 brd ff:ff:ff:ff:ff:ff
7: bond1: <BROADCAST,MULTICAST400> mtu 1500 qdisc noop qlen 1000
    link/ether 66:b2:88:29:3b:f9 brd ff:ff:ff:ff:ff:ff
8: bond2: <BROADCAST,MULTICAST400> mtu 1500 qdisc noop qlen 1000
    link/ether a6:38:c6:3c:0f:21 brd ff:ff:ff:ff:ff:ff
9: bond3: <BROADCAST,MULTICAST400> mtu 1500 qdisc noop qlen 1000
    link/ether de:65:14:44:00:18 brd ff:ff:ff:ff:ff:ff
10: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:bd:9d:70:a6 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:bdff:fe9d:70a6/64 scope link 
       valid_lft forever preferred_lft forever
12: vethe5be4c3@if11: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master docker0 
    link/ether e2:92:eb:03:aa:b7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::e092:ebff:fe03:aab7/64 scope link 
       valid_lft forever preferred_lft forever

It seems that LAN1 and LAN2 are eth3 and eth4 (or the opposite). But they are considered offline (or unplugged in the web interface) while they are physically detected on the router side. Nothing changed in the hardware configuration after the reboot from the update.

Can someone help me?

[orion]

"dmesg" might have certain clues about it. However it's better to send a support ticket to asustor directly.