Hello,

I'm having issues with a Thunderbolt 4 External Enclosure.

UGreen D700 (ASM2464PD) (4TB SN7100 inside formatted exFAT)

Z790 Proart Creator MB.

The goal is to quickly move files from ZFS mirror pool (SN850X Drives) to the external drive.

First main issue is the drive only gets seen by Unraid if plugged in at boot, I can mount it in Unassigned drives and access it from Docker fine but as soon as I unmount and remove the drive, it is no longer seen again when plugging in unless I reboot Unraid.

Second issue is when the drive is working it's seems to be limited to 10Gbps.

Connected to Windows or Mac device the enclosure speed is close to 30Gbps with the same test files, so I know it's capable of that.

Is there any tweaks or anything specific in Unraid that needs to be done for Thunderbolt 4 compatibility?

I couldn't find much info.

Please post the diagnostics.

11 hours ago, JorgeB said:

Please post the diagnostics.

See attached, this is taken with drive plugged in but not showing in unassigned devices.

unraid-diagnostics-20260310-1919.zip

Diags with the device showing please.

9 hours ago, JorgeB said:

Diags with the device showing please.

See attached, fresh reboot drive showing/working.

unraid-diagnostics-20260311-1725.zip

Regarding the speed, and based on the diags and assuming I'm looking at the correct device (174c:2463 ASMedia), it appears to be operating in USB backward compatibility mode, and also it's connected to a USB port that supports 10Gbps max:

/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M

ID 174c:2463 ASMedia Technology Inc.

The board does have a faster port (20000M/x2), where a SanDisk flash drive is connected to:

/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

ID 0781:5583 SanDisk Corp. Ultra Fit

My suggestion would be to swap ports between both devices and retesting. You can also check the lsusb -vt output to see if it's now linking faster (but note that if it starts operating in true Thunderbolt mode, it won't be listed there)

18 minutes ago, JorgeB said:

Regarding the speed, and based on the diags and assuming I'm looking at the correct device (174c:2463 ASMedia), it appears to be operating in USB backward compatibility mode, and also it's connected to a USB port that supports 10Gbps max:

/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M

ID 174c:2463 ASMedia Technology Inc.

The board does have a faster port (20000M/x2), where a SanDisk flash drive is connected to:

/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

ID 0781:5583 SanDisk Corp. Ultra Fit

My suggestion would be to swap ports between both devices and retesting. You can also check the lsusb -vt output to see if it's now linking faster (but note that if it starts operating in true Thunderbolt mode, it won't be listed there)

Yes, that's the drive, not sure why it's showing those speeds for these ports but It's definitely connected correctly.

See attached, drive is connected to port 8 (USB C TB4/USB4) and the Sandisk is connected to port 7 (slower USB A port)

Would there be a reason it only shows on boot and can't be unplugged and plugged back in? (drive does light up)

It's make it unusable at this point.

Try the other USB Type-C port, port 6.

19 minutes ago, egtrev said:

Would there be a reason it only shows on boot and can't be unplugged and plugged back in? (drive does light up)

Not sure, but Thunderbolt support in Linux can still be a little flaky, though it's currently not operating in true TB mode. Still could be related; my suggestion for that would be to try Unraid 7.3 when that is out, it will use a much newer kernel, which should have a considerable number of TB related improvements.

44 minutes ago, JorgeB said:

Try the other USB Type-C port, port 6.

Not sure, but Thunderbolt support in Linux can still be a little flaky, though it's currently not operating in true TB mode. Still could be related; my suggestion for that would be to try Unraid 7.3 when that is out, it will use a much newer kernel, which should have a considerable number of TB related improvements.

Attached now with it it in port 6 (had to reboot again for it to show)

Asus specs do say that it's USB4 compliant too, if that makes any difference.

Is there a way to make Unraid rescan for USB drives or that automatically done?

Is there a test version of 7.3 or is it too early for that yet.

unraid-diagnostics-20260311-1943.zip

Still the same, Linux is detecting the port as 10Gbps:

/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M

ID 174c:2463 ASMedia Technology Inc.

First 7.3 beta should be out very soon, possibly next week, retest once that is out, but I suspect the port speed won't change, but maybe it helps with the hot plug.

10 hours ago, JorgeB said:

Still the same, Linux is detecting the port as 10Gbps:

/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M

ID 174c:2463 ASMedia Technology Inc.

First 7.3 beta should be out very soon, possibly next week, retest once that is out, but I suspect the port speed won't change, but maybe it helps with the hot plug.

Thanks for the help, I'll try that once released.

Also would you mind checking the diagnostics atatched if possible, this is with an older Sabrent 2TB USB C 10Gbps enclosure in the same port 6, but this hot plugs fine.

I don't know if the diags would show it recognised any different to the TB4 enclosure.

unraid-diagnostics-20260312-1837.zip

In the end, is detected the same way, since the other one is reverting to USB legacy mode, but the TB one does show as a TB device initially.

Mar 11 17:23:13 UNRAID kernel: ACPI: bus type thunderbolt registered

Mar 11 17:23:13 UNRAID kernel: thunderbolt 0000:0b:00.0: enabling device (0000 -> 0002)

I seem to remember, when I did some TB tests a few months back, the Asmedia bridge I used could be set to USB, USB/TB, or just TB mode using the firmware update utility, and the behavior changed based on the setting, IIRC I had to set it to TB only for it to operate in TB mode, but that means it won't work with regular USB-C

2 hours ago, JorgeB said:

In the end, is detected the same way, since the other one is reverting to USB legacy mode, but the TB one does show as a TB device initially.

Mar 11 17:23:13 UNRAID kernel: ACPI: bus type thunderbolt registered

Mar 11 17:23:13 UNRAID kernel: thunderbolt 0000:0b:00.0: enabling device (0000 -> 0002)

I seem to remember, when I did some TB tests a few months back, the Asmedia bridge I used could be set to USB, USB/TB, or just TB mode using the firmware update utility, and the behavior changed based on the setting, IIRC I had to set it to TB only for it to operate in TB mode, but that means it won't work with regular USB-C

Thanks for checking.

I can't see much in the BIOS relating to Thunderbolt so maybe just incompatible currently.

I should probably really check that the board is working too but I don't really won't to mess and temporary boot my Unraid machine to Windows for testing there.

Would it be possible for me to pass the Thunderbolt controller/ports completely through to one of my Windows VMs and test it that way?

10 hours ago, egtrev said:

I can't see much in the BIOS relating to Thunderbolt so maybe just incompatible currently.

Not the BIOS, the utility to update the TB device's firmware.

10 hours ago, egtrev said:

Would it be possible for me to pass the Thunderbolt controller/ports completely through to one of my Windows VMs and test it that way?

It should be, as long as the TB controller is on its own IOMMU group.

On 3/13/2026 at 7:43 AM, JorgeB said:

Not the BIOS, the utility to update the TB device's firmware.

It should be, as long as the TB controller is on its own IOMMU group.

Any chance could just check this diagnostics, I'm trying a different enclosure (TB3), is it still showing the same?

This time the drive never gets removed from the Unraid when unplugged (Unraid still thinks connected) then when plugged back in and attempting to mount to doesn't seem to work and Mount is greyed out in unassigned drives.

unraid-diagnostics-20260315-1823.zip

unraid-diagnostics-20260315-1856.zip

Edited March 15Mar 15 by egtrev
Added new diag (reboot)

Which device is it? Looks like it's not showing in the USB output, so possibly it's being detected as TB.

8 hours ago, JorgeB said:

Which device is it? Looks like it's not showing in the USB output, so possibly it's being detected as TB.

WD Black SN7100 4TB is the drive inside the TB3 enclosure.

nvme4n1 is what unassigned devices had as the reference when it showed up.

Hmm, in the diags that device is nvme3n1

Mar 15 18:43:57 UNRAID emhttpd: online: WD_BLACK_SN7100_4TB_25393Y800126 (nvme3n1) 512 7814037168

But it looks like UD is getting confused

Mar 15 18:44:10 UNRAID unassigned.devices: Mounting 'Auto Mount' Devices...

Mar 15 18:44:10 UNRAID unassigned.devices: Partition '/dev/nvme3n1p1' does not have a file system and cannot be mounted.

Mar 15 18:44:10 UNRAID unassigned.devices: Disk with ID 'WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1)' is not set to auto mount.

This doesn't make sense; it detects the partition as nvme3n1p1, and in the next line, the device as nvme4n1

Post the output from ls -l /dev/disk/by-id/ | grep nvme

On 3/16/2026 at 5:46 PM, JorgeB said:

Hmm, in the diags that device is nvme3n1

Mar 15 18:43:57 UNRAID emhttpd: online: WD_BLACK_SN7100_4TB_25393Y800126 (nvme3n1) 512 7814037168

But it looks like UD is getting confused

Mar 15 18:44:10 UNRAID unassigned.devices: Mounting 'Auto Mount' Devices...

Mar 15 18:44:10 UNRAID unassigned.devices: Partition '/dev/nvme3n1p1' does not have a file system and cannot be mounted.

Mar 15 18:44:10 UNRAID unassigned.devices: Disk with ID 'WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1)' is not set to auto mount.

This doesn't make sense; it detects the partition as nvme3n1p1, and in the next line, the device as nvme4n1

Post the output from ls -l /dev/disk/by-id/ | grep nvme

I had to reboot to get the drive back, heres fresh diags attached and below is the output of that command after reboot.

root@UNRAID:~# ls -l /dev/disk/by-id/ | grep nvme
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-WDC_WDS100T2B0C-00PXH0_2052FP445207 -> ../../nvme1n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WDC_WDS100T2B0C-00PXH0_2052FP445207-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-WDC_WDS100T2B0C-00PXH0_2052FR496801 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WDC_WDS100T2B0C-00PXH0_2052FR496801-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-WD_BLACK_SN7100_4TB_25393Y800126 -> ../../nvme4n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WD_BLACK_SN7100_4TB_25393Y800126-part1 -> ../../nvme4n1p1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WD_BLACK_SN7100_4TB_25393Y800126-part2 -> ../../nvme4n1p2
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-WD_BLACK_SN850X_4000GB_24491L4A0702 -> ../../nvme2n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WD_BLACK_SN850X_4000GB_24491L4A0702-part1 -> ../../nvme2n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-WD_BLACK_SN850X_4000GB_24491L4A0704 -> ../../nvme3n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-WD_BLACK_SN850X_4000GB_24491L4A0704-part1 -> ../../nvme3n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a41f1a8b3 -> ../../nvme2n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a41f1a8b3-part1 -> ../../nvme2n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a41f1a8e6 -> ../../nvme3n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a41f1a8e6-part1 -> ../../nvme3n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a46ae6cb4 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a46ae6cb4-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a46aee7e2 -> ../../nvme1n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b444a46aee7e2-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root 13 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b448b4f426a46 -> ../../nvme4n1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b448b4f426a46-part1 -> ../../nvme4n1p1
lrwxrwxrwx 1 root root 15 Mar 17 19:59 nvme-eui.e8238fa6bf530001001b448b4f426a46-part2 -> ../../nvme4n1p2

unraid-diagnostics-20260317-2000.zip

Now the device was initially detected as nvme4n1, and also the same by UD

Mar 17 19:59:17 UNRAID emhttpd: online: WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1) 512 7814037168

...

Mar 17 19:59:30 UNRAID unassigned.devices: Partition '/dev/nvme4n1p1' does not have a file system and cannot be mounted.

Mar 17 19:59:30 UNRAID unassigned.devices: Disk with ID 'WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1)' is not set to auto mount.

Was the device supposed to have a mountable filesystem? Also, post new diags after disconnecting it and reconnecting it.

10 hours ago, JorgeB said:

Now the device was initially detected as nvme4n1, and also the same by UD

Mar 17 19:59:17 UNRAID emhttpd: online: WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1) 512 7814037168

...

Mar 17 19:59:30 UNRAID unassigned.devices: Partition '/dev/nvme4n1p1' does not have a file system and cannot be mounted.

Mar 17 19:59:30 UNRAID unassigned.devices: Disk with ID 'WD_BLACK_SN7100_4TB_25393Y800126 (nvme4n1)' is not set to auto mount.

Was the device supposed to have a mountable filesystem? Also, post new diags after disconnecting it and reconnecting it.

Yes it exFAT system, I did manage to get it mounted.

See attached diags unplugged and plugged back in - unraid & UD both still think the drive is connected when unplugged (the uD mount option does go grey though) then when plugged back in I don't get the option to mount again until reboot.

unraid-diagnostics-20260318-1755 (plugged back in).zip unraid-diagnostics-20260318-1752 (after unplugged).zip

21 minutes ago, egtrev said:

Yes it exFAT system, I did manage to get it mounted.

I assume the filesystem is not on partition 1?

Regarding hot plug, the device is being detected, but it fails to wake up the PCI port up:

Mar 18 17:53:52 UNRAID kernel: thunderbolt 0-3: new device found, vendor=0x25 device=0x1

Mar 18 17:53:52 UNRAID kernel: thunderbolt 0-3: ACASIS TBU405

Mar 18 17:55:30 UNRAID kernel: pcieport 0000:41:02.0: Unable to change power state from D3cold to D0, device inaccessible

A few things you can try:

1. Click on the flash drive, scroll down to the Syslinux configuration section, make sure Menu View is enabled, and add after /bzroot to the default boot option, the one in green:

pcie_aspm=off pci=pcie_bus_perf

It should be added to the same line as /bzroot, just leave a space between that and the kernel option, then please reboot and retest.

2. Check your motherboard BIOS for these or similar settings:

   Discrete Thunderbolt Support: Enabled.

   Thunderbolt Boot Support: Enabled (this sometimes helps the OS maintain "ownership" of the controller).

   GPIO3 Force Pwr: Enabled (if available; this forces power to the TB3/4 slots).

   PCIe Resizable BAR: Sometimes toggling this (Off) can resolve address space conflicts with TB devices.

3. Open a terminal window and type:

echo 1 > /sys/bus/pci/rescan

Then see if anything is detected in the syslog after that

2 hours ago, JorgeB said:

I assume the filesystem is not on partition 1?

Regarding hot plug, the device is being detected, but it fails to wake up the PCI port up:

Mar 18 17:53:52 UNRAID kernel: thunderbolt 0-3: new device found, vendor=0x25 device=0x1

Mar 18 17:53:52 UNRAID kernel: thunderbolt 0-3: ACASIS TBU405

Mar 18 17:55:30 UNRAID kernel: pcieport 0000:41:02.0: Unable to change power state from D3cold to D0, device inaccessible

A few things you can try:

1. Click on the flash drive, scroll down to the Syslinux configuration section, make sure Menu View is enabled, and add after /bzroot to the default boot option, the one in green:

pcie_aspm=off pci=pcie_bus_perf

It should be added to the same line as /bzroot, just leave a space between that and the kernel option, then please reboot and retest.

2. Check your motherboard BIOS for these or similar settings:

   Discrete Thunderbolt Support: Enabled.

   Thunderbolt Boot Support: Enabled (this sometimes helps the OS maintain "ownership" of the controller).

   GPIO3 Force Pwr: Enabled (if available; this forces power to the TB3/4 slots).

   PCIe Resizable BAR: Sometimes toggling this (Off) can resolve address space conflicts with TB devices.

3. Open a terminal window and type:

echo 1 > /sys/bus/pci/rescan

Then see if anything is detected in the syslog after that

Not sure on the partition I just orignally formatted in Windows (does Automount now in Unraid), see attached how UD shows it on boot. I ran chkdsk in Windows and seems to have fixed the initial mount problem.

1. I've attached what I now have in Flash section.

2. First option was Enabled, I've now Enabled Boot Support and disabled Resizable BAR - I couldn't find the GPIO3 option.

3. This was the Syslog portion after that command.

   Mar 18 21:10:59 UNRAID kernel: pcieport 0000:40:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
   Mar 18 21:10:59 UNRAID kernel: pcieport 0000:41:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
   Mar 18 21:10:59 UNRAID kernel: pcieport 0000:41:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
   Mar 18 21:10:59 UNRAID kernel: pcieport 0000:41:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring
   Mar 18 21:10:59 UNRAID kernel: pci_bus 0000:42: busn_res: [bus 42-59] end is updated to 59
   Mar 18 21:10:59 UNRAID kernel: pci_bus 0000:5a: busn_res: [bus 5a] end is updated to 5a
   Mar 18 21:10:59 UNRAID kernel: pci_bus 0000:5b: busn_res: [bus 5b-72] end is updated to 72
   Mar 18 21:10:59 UNRAID kernel: pci_bus 0000:41: busn_res: [bus 41-72] end is updated to 72

Also have have attached Diags as of now - device back in.

Maybe just the Thunderbolt on this motherboard isn't compatible, might just have to give up on this one.

unraid-diagnostics-20260318-2114.zip

10 hours ago, egtrev said:

Maybe just the Thunderbolt on this motherboard isn't compatible

If hotplug is still not working with the kernel options it may be that, you can also try 7.3.0-beta.1, the much newer kernel might help.

On 3/19/2026 at 7:46 AM, JorgeB said:

If hotplug is still not working with the kernel options it may be that, you can also try 7.3.0-beta.1, the much newer kernel might help.

Thanks for the help, no difference on the new beta so I think this just isn't going to work for me.