TS-473A Network Port Adapter and USB-A ports dead

English
1

On my new TS-473A I have 2 x 2.5GB Network Ports.
One of these no longer shows as existing in QTS (Port 1) No lights on port, checked cables by switching the cables from working to non working port.

Also seems that none of three USB-A Gen 3.2 ports appear to read any connected USB devices.

Im assuming these must be hardware failures if you can’t see the ports to configure in QTS.

Anyone got any ideas before I chase down warranty repairs. NAS only about 3 weeks old. Was working then 2 days ago just stopped.

Thanks
David

2

I would check the kernel ring messages


dmesg

See if any issues are in there that would point to a failure of USB and LAN ports.

3

How would I do that, being new to finding my way round a NAS?

David

4

Without a working network connection, only via a GPU inserted into the NAS or maybe network card
Both can be found here

You can also try to eject all drives and start the NAS setup (make sure ALL drives are out also M.2), if you can reach that via network, your NAS OS is borked, if that also does not work, it’s a hardware defect of the NAS

5

I have still have access to the NAS and can get to Control Panel.
Port 2 works as well as the Dual QXG 10GB network card. Just Port 1 has gone dead, port 2 has been renamed as Adapter1 and the Expansion Card named as Adapter 2 and 3.
The USB A ports also died at same time.
Examining logs there appears a gap as the system is set to auto boot every morning and switch off at times set in power schedule. But all the boot messages on the day of failure do not appear to exist. Can find no clues to anything changing?

6

Have you tried shutdown then disconnecting power for 10 sec then boot up?

7

So did you check dmesg via SSH ?

8

Logged in via SSH but only get a prompt not the console window so not sure what to enter now to see dmesg?

9

you have to exit out of this console or disable it

image
image1159×600 57.5 KB

10

OK done that - still in terminal - appear to be in a home directory as i can only list recycle bin with the ls command, about the only one I know.

11

you need to login to SSH via admin and issue the command dmesg

12

ive logged in via my admin user (not admin itself which is disabled on NAS) OK
message work now I got to understand what I’m looking for in the pages of output

13

You could filter the output for network and USB messages

e.g.

dmesg | grep "eth\|usb"

14

OK
Got This

2.084874] usbcore: registered new interface driver usbfs
[ 2.085856] usbcore: registered new interface driver hub
[ 2.086858] usbcore: registered new device driver usb
[ 11.437420] usbcore: registered new interface driver btusb
[ 11.458054] usbcore: registered new interface driver usbhid
[ 11.463621] usbhid: USB HID core driver
[ 13.632409] usbcore: registered new interface driver usblp
[ 13.691746] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 13.758143] usb usb4: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 13.776821] usbcore: registered new interface driver usb-storage
[ 13.783988] usbcore: registered new interface driver uas
[ 13.917857] usb 1-3: new high-speed USB device number 2 using xhci_hcd
[ 13.981851] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[ 14.117618] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 14.124240] scsi host7: usb-storage 3-2:1.0
[ 14.179928] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 14.200071] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 14.206440] scsi host8: usb-storage 2-1:1.0
[ 14.324598] usb 2-3: new SuperSpeedPlus Gen 2 USB device number 3 using xhci_hcd
[ 14.856853] usb 1-3.1: new high-speed USB device number 3 using xhci_hcd
[ 14.948092] usbcore: registered new interface driver r8152
[ 15.072085] usb 2-3.1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 15.171854] usb 1-3.2: new high-speed USB device number 4 using xhci_hcd
[ 15.247255] igc 0000:0d:00.0 eth0: MAC: 24:5e:be:6e:b8:93
[ 15.248122] Check proc_name[usb-storage].
[ 15.264824] Check proc_name[usb-storage].
[ 15.264835] Check proc_name[usb-storage].
[ 15.268849] Check proc_name[usb-storage].
[ 15.276843] Check proc_name[usb-storage].
[ 15.282406] Check proc_name[usb-storage].
[ 15.305279] Check proc_name[usb-storage].
[ 15.305286] Check proc_name[usb-storage].
[ 15.305608] Check proc_name[usb-storage].
[ 15.305684] Check proc_name[usb-storage].
[ 15.305687] Check proc_name[usb-storage].
[ 15.305695] Check proc_name[usb-storage].
[ 15.305697] Check proc_name[usb-storage].
[ 15.306105] Check proc_name[usb-storage].
[ 15.306180] Check proc_name[usb-storage].
[ 15.306181] Check proc_name[usb-storage].
[ 15.306189] Check proc_name[usb-storage].
[ 15.306190] Check proc_name[usb-storage].
[ 15.306812] Check proc_name[usb-storage].
[ 15.318528] Check proc_name[usb-storage].
[ 15.326533] Check proc_name[usb-storage].
[ 15.389167] usb 2-3.2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd
[ 15.486856] usb 1-3.1.1: new full-speed USB device number 5 using xhci_hcd
[ 15.587768] usb 1-3.1.1: not running at top speed; connect to a high speed hub
[ 15.650927] usb 2-3.1.3: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[ 15.671103] usb-storage 2-3.1.3:1.0: USB Mass Storage device detected
[ 15.677610] usb-storage 2-3.1.3:1.0: Quirks match for vid 152d pid 0567: 5000000
[ 15.685022] scsi host9: usb-storage 2-3.1.3:1.0
[ 15.744461] usb 2-3.4: new SuperSpeedPlus Gen 2 USB device number 7 using xhci_hcd
[ 15.801536] usb-storage 2-3.4:1.0: USB Mass Storage device detected
[ 15.807895] scsi host10: usb-storage 2-3.4:1.0
[ 15.817953] Check proc_name[usb-storage].
[ 15.822563] Check proc_name[usb-storage].
[ 15.827180] Check proc_name[usb-storage].
[ 15.831196] Check proc_name[usb-storage].
[ 15.851649] Check proc_name[usb-storage].
[ 15.855651] Check proc_name[usb-storage].
[ 16.151169] Check proc_name[usb-storage].
[ 16.155176] Check proc_name[usb-storage].
[ 16.361713] usbcore: registered new interface driver cdc_ether
[ 16.368459] usbcore: registered new interface driver rndis_host
[ 16.406721] Check proc_name[usb-storage].
[ 16.418920] Check proc_name[usb-storage].
[ 16.418952] Check proc_name[usb-storage].
[ 16.422937] Check proc_name[usb-storage].
[ 16.430950] Check proc_name[usb-storage].
[ 16.436375] Check proc_name[usb-storage].
[ 16.493894] Check proc_name[usb-storage].
[ 16.497910] Check proc_name[usb-storage].
[ 16.715131] Check proc_name[usb-storage].
[ 16.727292] Check proc_name[usb-storage].
[ 16.727300] Check proc_name[usb-storage].
[ 16.731337] Check proc_name[usb-storage].
[ 16.739361] Check proc_name[usb-storage].
[ 16.744771] Check proc_name[usb-storage].
[ 17.063604] Check proc_name[usb-storage].
[ 17.075845] Check proc_name[usb-storage].
[ 17.075855] Check proc_name[usb-storage].
[ 17.079870] Check proc_name[usb-storage].
[ 17.087891] Check proc_name[usb-storage].
[ 17.093505] Check proc_name[usb-storage].
[ 17.154862] Check proc_name[usb-storage].
[ 17.158878] Check proc_name[usb-storage].
[ 23.953603] atlantic 0000:09:00.0 eth1_tmp_657051: renamed from eth1
[ 23.960088] atlantic 0000:0a:00.0 eth2_tmp_663554: renamed from eth2
[ 23.966550] atlantic 0000:09:00.0 eth2: renamed from eth1_tmp_657051
[ 23.972997] atlantic 0000:0a:00.0 eth1: renamed from eth2_tmp_663554
[ 30.595293] usbcore: registered new interface driver pl2303
[ 30.600883] usbserial: USB Serial support registered for pl2303
[ 30.607920] usbcore: registered new interface driver cdc_acm
[ 59.559119] drbd r2: Method to ensure write ordering: flush
[ 60.738653] drbd r3: Method to ensure write ordering: flush
[ 61.923395] drbd r4: Method to ensure write ordering: flush
[ 133.612102] usbcore: registered new interface driver snd-usb-audio
[ 133.640424] usbcore: registered new interface driver snd-usb-caiaq
[ 133.652916] usbcore: registered new interface driver uvcvideo
[ 173.874084] 8021q: adding VLAN 0 to HW filter on device eth1
[ 174.262725] 8021q: adding VLAN 0 to HW filter on device eth2
[ 176.425873] igc 0000:0d:00.0 eth0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[ 179.305213] atlantic 0000:0a:00.0 eth1: atlantic: link change old 0 new 10000
[ 179.507743] atlantic 0000:09:00.0 eth2: atlantic: link change old 0 new 10000
[ 1816.976534] Check proc_name[usb-storage].
[ 1816.980554] Check proc_name[usb-storage].
[23518.664434] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[23576.520453] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[23629.768441] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[24397.255420] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[24482.760413] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[24562.120396] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[24599.495444] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

15

Doesn’t seem to make any ref to eth0 which I assume would mean port 1
Not sure what the USB data is trying to tell me?

16

What USB devices are currently plugged in ?

17

on the Gen 3.2 USB A - only one device a orico dock containing an WD SSD which was
reading OK until fault
on the USB-C Gen 3-1 the TR004 expansion which is working as expected. Current backing up data.

18

Is this dmesg a history log or current status?

19

dmesg is all kernel ring events since the kernel started

In your initial message you say no USB devices currently work, but now you say you are currently backing up to a USB connected TR-004

And for eth devices I do see in the logs eth0,1,2

On a device here with 5 network ports, ifconfig spits out eth0-eth4 (besides loopback, vswitch and all those used by VMStation and ContainerStation)

20

None of the USB A 3.2 ports work
the USB C 3.1 port does and is directly connected to TR004 USBc (not sure if thats Gen 1 or 2)

the eth0 is physically the Port 2 on the NAS
eth1 is mapped to the QXG 102G -t 107 network expansion port 1
eth3 is mapped to the QXG 102G-t 107 network expansion port 2
these are on the card in the PCI bus pciex4 slot 2.

eth 0 and 1 should be the two 2.5 gb physical ports the 2.5gb LAN but port 1 appears to have gone dead, port 2 has been mapped to eth0 and the pcie expansion card follows on from that. So it seems to show the kernel is not seeing both 2.5gb LAN hardware ports on the NAS box itself. Is that what you see?