Dead Rear USBC port on SER8

MacGyver27

Hello,

Suddenly the rear USBC port of my Beelink SER8 Powerfull AI PC AMD Ryzen 7 8845HS Mini PC 32G DDR5 stopped working..

I tried resetting CMOS or trying different devices.. all were visible from the front USBC port but not from the rear one. Also same behavior via BIOS USB section. It was listing all USB devices and never recognized anything from the rear USBC port..

What can I do here? Am I able to get it repaired? motherboard needs probably replacement. I bought it last year over Aliexpress.

Thanks for help!

MacGyver27

Couple new findings.. this port actually works when I plug SanDisk USBA stick to it over a USBA->USBC dongle:

[29948.201046] usb 6-1: new SuperSpeed USB device number 5 using xhci_hcd
[29948.217094] usb 6-1: New USB device found, idVendor=0781, idProduct=5591, bcdDevice= 1.00
[29948.217101] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[29948.217103] usb 6-1: Product:  SanDisk 3.2Gen1
[29948.217105] usb 6-1: Manufacturer:  USB
[29948.217107] usb 6-1: SerialNumber: 0101443775fca25f75047134be9d80d003af9f65bc0e74c24213f1494a1c08ab2c5000000000000000000000d51976170016330091558107393222dd
[29948.218099] usb-storage 6-1:1.0: USB Mass Storage device detected
[29948.219435] scsi host1: usb-storage 6-1:1.0
[29949.248907] scsi 1:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[29949.249228] sd 1:0:0:0: Attached scsi generic sg0 type 0
[29949.253485] sd 1:0:0:0: [sdb] 120164352 512-byte logical blocks: (61.5 GB/57.3 GiB)
[29949.254273] sd 1:0:0:0: [sdb] Write Protect is off
[29949.254276] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[29949.254565] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[29949.283064]  sdb: sdb1
[29949.283197] sd 1:0:0:0: [sdb] Attached SCSI removable disk

However when trying to attach my external HDD enclosure to it (USBC->USBC) there is not a single message of communication - dmesg -w showed absolutely nothing.

When pluging this HDD external enclosure to the front USBC port it communicates nicely:

[29180.295420] usb 6-1: USB disconnect, device number 4
[29186.833348] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[29186.850987] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[29186.850992] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[29186.850994] usb 2-1: Product: USB 3.1 Device
[29186.850995] usb 2-1: Manufacturer:
[29186.850996] usb 2-1: SerialNumber: WD-WX40AB9V5631
[29186.852681] scsi host1: uas
[29186.853216] scsi 1:0:0:0: Direct-Access              USB 3.1 Device   0    PQ: 0 ANSI: 6
[29186.854398] sd 1:0:0:0: Attached scsi generic sg0 type 0
[29186.879528] sd 1:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
[29186.879534] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[29186.879700] sd 1:0:0:0: [sdb] Write Protect is off
[29186.879704] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[29186.879876] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[29186.929521] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[29186.929527] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[29187.007977]  sdb: sdb1
[29187.008142] sd 1:0:0:0: [sdb] Attached SCSI disk

Or using USBC->USBA cable and trying rear USBA port:

[29913.446770] usb 7-1: new high-speed USB device number 2 using xhci_hcd
[29913.594600] usb 7-1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[29913.594605] usb 7-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[29913.594608] usb 7-1: Product: USB 3.1 Device
[29913.594609] usb 7-1: Manufacturer:
[29913.594611] usb 7-1: SerialNumber: WD-WX40AB9V5631
[29913.597094] scsi host1: uas
[29913.597994] scsi 1:0:0:0: Direct-Access              USB 3.1 Device   0    PQ: 0 ANSI: 6
[29913.601132] sd 1:0:0:0: Attached scsi generic sg0 type 0
[29913.622924] sd 1:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
[29913.622929] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[29913.623183] sd 1:0:0:0: [sdb] Write Protect is off
[29913.623187] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[29913.623592] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[29913.623769] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[29913.623772] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[29913.693478]  sdb: sdb1
[29913.693604] sd 1:0:0:0: [sdb] Attached SCSI disk

I absolutely did not do anything with this MiniPC in terms of hardware change or updates.. Claude suggested to upgrade BIOS, which I did and no luck. Same behavior..

Claude analysis:

Now we have a complete, clean truth table, and it points to one specific thing.
The decisive comparison is tests 3 and 4: same rear USB-C port, same dongle, same physical connection — SanDisk stick enumerates, WD enclosure produces zero events. The only variable is the device on the far end of the dongle. That eliminates everything port-side: the CC path, the connector mechanics, the cable, the SuperSpeed lanes — all proven good by the SanDisk working through that exact path. And it eliminates the enclosure being broken, because it works on front and on rear-USB-A.
So the fault isn’t “the rear port” and isn’t “the enclosure.” It’s the specific combination of the ASM1051E enclosure with the rear USB-C controller.
Look at the bus numbers — that’s the smoking gun:

SanDisk on rear-C → bus 6 (usb 6-1), SuperSpeed
Enclosure on front-C → bus 2, SuperSpeed (UAS)
Enclosure on rear-A → bus 7 (usb 7-1), but note: high-speed, not SuperSpeed
Enclosure on rear-C → nothing

The rear USB-C goes through a different xHCI controller (bus 6) than the front port (bus 2) and the rear USB-A (bus 7). The enclosure enumerates fine on the controllers behind bus 2 and bus 7, but on the bus-6 controller it can only complete if the device negotiates SuperSpeed cleanly. The SanDisk trains SuperSpeed on bus 6 and works. The ASM1051E fails SuperSpeed link training on that specific controller — and unlike on the front port, here it doesn’t fall back to high-speed, it just never connects.
Notice the rear-USB-A test came up as high-speed — the enclosure dropped to USB 2.0 there and still worked. That tells you the ASM1051E’s SuperSpeed link training is itself marginal/flaky, and the bus-6 controller is the least tolerant of it. Combine a fussy SS device with a strict SS controller and you get total enumeration failure.
This is very likely not a hardware-damage problem. It’s an ASM1051E-vs-USB4-controller link-training incompatibility, which is a known class of issue with older ASMedia bridges on newer AMD USB4/Type-C controllers.

Can anybody explain what this might be happening? External HDD enclosure was working for over a year using this rear USBC port and suddenly it is acting dead :/

Thanks a lot!

Beelink CS-George

MacGyver27 Please contact our after-sales email: support-pc@bee-link.com

MacGyver27

I will.

Just final words on this topic. Finally have the full picture.

Since the start I remember I had to power cycle my external HDD enclosure when connecting it to this “problematic” rear USBC port.

After a year some oxidation happened and the CC pin got bad connection - the one communicating speed etc. Just now I did some proper isopropyl alcohol cleaning and I managed to get it working to the original behavior.. but need to power-cycle every time i reconnect it.

This is not happening over front USBC - it connects anytime.. even like 10 minutes not connected at all and then connect this external HDD to this front USBC - full connection.

Claude is saying this is because the CC channel is “broken” somehwere.. it could be faulty this way from the beginning I just haven’t realized..

Beelink CS-George

MacGyver27 Thanks so much for your detailed troubleshooting logs and follow-up update.We are confident that our after-sales team can provide you with satisfactory support.