[Help] TerraMaster D5 Hybrid needs physical reconnect after Linux reboot
Posted: 20 Mar 2026, 20:34
Hi!
I have a D5 Hybrid attached over USB-C directly to a server running Fedora 34. Everything works smooth and fast.
The only downside is that, when I reboot the OS, the D5 Hybrid doesn't get recognized afterwards.
The device its lights stay on, disks are running, but the OS can't find it at all.
I need to manually unplug and plug the USB-C cable for the device to start working again. So it seems the device is in some kind of weird state.
This is after a reboot:
When I unplugged and plugged the device again, this is the output:
This is weird behavior, I tried different USB hubs and hard disk drives, and they all seem to be available after a reboot.
I also tried regular USB-2 HDD's attached to a USB-C hub and attached the hub to the USB-C of the server. Also works.
So for some reason this behavior of the D5 Hybrid where it stays unconnected after a reboot is very specific for that device, and not seem related to server hardware or OS.
I have a D5 Hybrid attached over USB-C directly to a server running Fedora 34. Everything works smooth and fast.
The only downside is that, when I reboot the OS, the D5 Hybrid doesn't get recognized afterwards.
The device its lights stay on, disks are running, but the OS can't find it at all.
I need to manually unplug and plug the USB-C cable for the device to start working again. So it seems the device is in some kind of weird state.
This is after a reboot:
Code: Select all
lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 002: Dev 002, If 0, Class=Communications, Driver=cdc_acm, 12M
|__ Port 002: Dev 002, If 1, Class=CDC Data, Driver=cdc_acm, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 001: Dev 003, If 0, Class=Billboard, Driver=[none], 12M
|__ Port 005: Dev 004, If 0, Class=Billboard, Driver=[none], 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 10000M
Code: Select all
lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 002: Dev 002, If 0, Class=Communications, Driver=cdc_acm, 12M
|__ Port 002: Dev 002, If 1, Class=CDC Data, Driver=cdc_acm, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 10000M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
|__ Port 001: Dev 003, If 0, Class=Mass Storage, Driver=uas, 5000M
|__ Port 003: Dev 004, If 0, Class=Mass Storage, Driver=uas, 10000M
|__ Port 004: Dev 005, If 0, Class=Mass Storage, Driver=uas, 10000M
I also tried regular USB-2 HDD's attached to a USB-C hub and attached the hub to the USB-C of the server. Also works.
So for some reason this behavior of the D5 Hybrid where it stays unconnected after a reboot is very specific for that device, and not seem related to server hardware or OS.