My upgrade to 7.0 didn't go so well.  Both of my thunderbolt enclosures (OWC Thunderbay 8 and OWC Flex 1U4) failed to show any drives in unRAID 7.0 and I was forced to roll back to 6.12.14.  I tried to make some tweaks under system devices in 7.0 with no luck.  Aren't support for the thunderbolt controllers built into the kernel?  Working in 6.12.14 are the following: Intel Corporation JHL6540 Thunderbolt 3 Bridge and Intel Corporation JHL7440 Thunderbolt 3 Bridge and they are hooked to a Minisforum ms-01 using and Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller.  Attached logs from working 6.12.14 and not working 7.0.  I also hooked up a portable Thunderbolt SSD (intel controller) to both the host directly and downstream OWC enclosures ports and this was recognized in 7.0 with SSD information (unassigned devices) but drive showed as spun down and also didn't show any partitions or capacity and I was unable to bring up more info, clear or partition the SSD.  This again all working without issue in 6.12.14.  Any help is much appreciated.

unraid-diagnostics-20250208-2033_6.12.14.zip unraid-diagnostics-20250208_1227_7.0.0.zip

2 hours ago, Chris Teasdale said:

Aren't support for the thunderbolt controllers built into the kernel?

Yes, and a newer kernel should have better support, but that is not the issue, Thunderbolt is found, and the driver initialized, but it's then failing to initialize the JMicron SATA controllers:

 

Feb  8 20:24:17 unRAID kernel: thunderbolt 0-3: new device found, vendor=0x5a device=0xde58
Feb  8 20:24:17 unRAID kernel: thunderbolt 0-3: Other World Computing Flex 1U4
Feb  8 20:24:17 unRAID kernel: ata5: failed to resume link (SControl FFFFFFFF)
Feb  8 20:24:17 unRAID kernel: ata5: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)
Feb  8 20:24:17 unRAID kernel: ahci 0000:04:00.0: AHCI controller unavailable!

 

Well that is the step in the right direction.  Werid then the portable Wavelink Thunderbolt drive is detected and it showed the drive brand and name in unassigned devices in the GUI but with no drive size as also shown below in the log.  This is all a bit above my skill set but it seems strange.  Is there more info I can provide?

 

Feb  8 20:24:17 unRAID kernel: thunderbolt 0-101: Wavlink UTE02

Feb  8 20:25:18 unRAID emhttpd: device /dev/nvme1n1 has size zero

I would suggest downgrading foe now, then retest once a new Unraid release with a newer kernel is available.

As of Version 7.1.2 Unraid does not mount my drives in my thunderbolt enclosures (OWC Thunderbay 8 and OWC Flex 1U4) and they work perfectly in 6.12.14

在 7.1.2 版本中，将USB ThunderBolt 设备直通后，奇迹发生了，可以看到雷电磁盘柜了，也可以正常使用阵列。

In version 7.1.2, after passing the USB ThunderBolt device, a miracle happened. The Thunderbolt disk enclosures can be seen and the array can be used normally.

将这个设备直通，绑定 VFIO 设备：Pass this device through and bind the VFIO device:

这个JHL7440 控制器不要直通，如果也选上了，反而看不到设备！This JHL7440 controller should not be passed through directly. If it is selected, the device will not be visible!

重启后就可以看到设备了！smart 和温度信息正常！After restarting, you can see the device! Smart and temperature information are normal!

不得不说，这个坑够深的，希望能在后续版本得到正式解决。 在 6.12.15 版本是没有这个问题的，不需要直通 雷电接口就可以直连磁盘柜了。

我的设备：

主机：MinisForum MS-01

雷电磁盘柜：MILLENNION 8858T3

I hope it can be officially solved in the subsequent versions. There is no such problem in version 6.12.15. You can directly connect the enclosures without the direct pass-through Thunderbolt .

My equipment:

Host: MinisForum MS-01

Thunderbolt disk enclosures: MILLENNION 8858T3

I'm having the same issue. Any updates on this? Here are my Diagnostics on 7.1.2

yesihack-cube-diagnostics-20250527-1319.zip

Edited May 27, 20251 yr by yesihack

26 minutes ago, yesihack said:

I'm having the same issue.

Post the output from:

ls -l /sys/bus/thunderbolt/devices/

On 5/27/2025 at 1:45 PM, JorgeB said:

# ls -l /sys/bus/thunderbolt/devices/

total 0

lrwxrwxrwx 1 root root 0 May 30 08:44 0-0 -> ../../../devices/pci0000:00/0000:00:0d.2/domain0/0-0/

lrwxrwxrwx 1 root root 0 May 30 08:44 1-0 -> ../../../devices/pci0000:00/0000:00:0d.3/domain1/1-0/

lrwxrwxrwx 1 root root 0 May 30 08:44 1-0:1.1 -> ../../../devices/pci0000:00/0000:00:0d.3/domain1/1-0/usb4_port1/1-0:1.1/

lrwxrwxrwx 1 root root 0 May 30 08:44 1-1 -> ../../../devices/pci0000:00/0000:00:0d.3/domain1/1-0/1-1/

lrwxrwxrwx 1 root root 0 May 30 08:44 domain0 -> ../../../devices/pci0000:00/0000:00:0d.2/domain0/

lrwxrwxrwx 1 root root 0 May 30 08:44 domain1 -> ../../../devices/pci0000:00/0000:00:0d.3/domain1/Post the output from:

ls -l /sys/bus/thunderbolt/devices/

On 5/27/2025 at 1:45 PM, JorgeB said:

Post the output from:

ls -l /sys/bus/thunderbolt/devices/

I know that 1-1 is my ThunderBay 8 device. I have a script that changes Authorized to 1, but it changes back to 0 on reboot. I'm not sure what's making that change back to 0. And I don't see the drives in UnRaid Array.

#/sys/bus/thunderbolt/devices/1-1# cat device

0xde19

#/sys/bus/thunderbolt/devices/1-1# cat device_name

ThunderBay 8

#/sys/bus/thunderbolt/devices/1-1# cat authorized

0

/sys/bus/thunderbolt/devices/1-1# ls

authorized device generation nvm_authenticate nvm_version rx_lanes subsystem@ tx_speed unique_id vendor_name

boot device_name nvm_active1/ nvm_non_active1/ power/ rx_speed tx_lanes uevent vendor wakeup/

Edited May 30, 20251 yr by yesihack

49 minutes ago, yesihack said:

but it changes back to 0 on reboot.

This is normal Linux default behavior, does it start working after you set add a key and authorize?

# key=$(openssl rand -hex 32)
# echo $key > /sys/bus/thunderbolt/devices/1-1/key
# echo 1 > /sys/bus/thunderbolt/devices/1-1/authorized

59 minutes ago, JorgeB said:

echo $key > /sys/bus/thunderbolt/devices/1-1/key

I am unable to add a Key to the 1-1 folder. I don't think I can create files in the 1-1 dir, only modify them.

root@Yesihack-Cube:/sys/bus/thunderbolt/devices/1-1# echo 1 > /sys/bus/thunderbolt/devices/1-1/authorized

root@Yesihack-Cube:/sys/bus/thunderbolt/devices/1-1# ls

authorized device generation nvm_authenticate nvm_version rx_lanes subsystem@ tx_speed unique_id vendor_name

boot device_name nvm_active1/ nvm_non_active1/ power/ rx_speed tx_lanes uevent vendor wakeup/

root@Yesihack-Cube:/sys/bus/thunderbolt/devices/1-1# sudo echo $key > /sys/bus/thunderbolt/devices/1-1/key

bash: /sys/bus/thunderbolt/devices/1-1/key: Permission denied

OK, I think I found a solution. Went to Tools -> System Devices and checked the Thunderbolt controller. Then selected "Bind Devices to VFIO" At Boot" Rebooted and now Drives are showing up fine.

Well, that's odd, but great if it works.

I just wanted to add to this thread that the above suggestion also fixed my issues with my OWC Thunderbay 8 enclosure not being visible under Unraid 7. Selecting the following devices to bind to VFIO at boot solved the issues. The drives in the enclosure showed up right after a reboot. This is on my Intel Serpent Canyon NUC

Dropping a line here added the same 3 to vfio and got my nvme tb4 enclosure to work. Ty!

This fixes the issue on my system with external egpu and nvme: Add this line in the syslinux config. Before the devices showed up but did not initialise.

thunderbolt.host_reset=0