List of working Thunderbolt services and supported Thunderbolt card / host combinations in Unraid

Hello again.

Could do with some further help if that's ok.

I've now bought a Thunderbolt device. An OWC ThunderBay 8.

dmesg | grep -i thunderbolt

[ 12.213797] ACPI: bus type thunderbolt registered

[ 511.431435] thunderbolt 0-0:1.1: new retimer found, vendor=0x8087 device=0xd9c

[ 512.193274] thunderbolt 0-1: new device found, vendor=0x5a device=0xde78

[ 512.193277] thunderbolt 0-1: Other World Computing ThunderBay 8

The only scenario I've managed so far where the thunderbay's disk show up (only in unassiged devices, not as an option in the array), is to turn off both unraid and thunderbay, unplug thunderbay, turn on unraid, wait until I can run terminal, plug thunderbay in, then run echo 1 > /sys/bus/pci/rescan - at whicn point it shows up as an unassigned device.

Any ideas on how to get unraid to spot it at the point of powering on?

I have ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1" in 99-local.rules already.

I've also tried this script

#!/bin/bash

LOGFILE="/boot/config/thunderbolt_log.txt"

echo "--- $(date): Starting Thunderbolt init ---" >> "$LOGFILE"

DEVICE_PATH="/sys/bus/thunderbolt/devices/0-1"

# Wait for the Thunderbolt device to appear

for i in {1..30}; do

if [[ -d "$DEVICE_PATH" ]]; then

echo "Device found at 0-1" >> "$LOGFILE"

# Check if already authorized

AUTH=$(cat "$DEVICE_PATH/authorized")

if [[ "$AUTH" -eq 1 ]]; then

echo "Already authorized" >> "$LOGFILE"

else

echo 1 > "$DEVICE_PATH/authorized" 2>>"$LOGFILE" || echo "Failed to authorize device" >> "$LOGFILE"

fi

break

fi

echo "Waiting for device... ($i)" >> "$LOGFILE"

sleep 1

done

# Rescan PCI to detect drives

echo 1 > /sys/bus/pci/rescan

echo "Rescanned PCI" >> "$LOGFILE"

echo "--- Done ---" >> "$LOGFILE"

running as a scheduled task "At First Array Start Only" with no joy.

EDIT:
I ran FORMAT from Unassigned Disk Devices to see if that would make it show up in ARRAY. It hasn't. I followed my own instructions and rebooted/plugged in. It's back in unassigned devices with FORMAT as an option

text error warn system array login

Jul 2 15:37:39 Node304 kernel: ata13: SATA max UDMA/133 abar m8192@0x86010000 port 0x86010100 irq 209 lpm-pol 0

Jul 2 15:37:39 Node304 kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Jul 2 15:37:39 Node304 kernel: ata13.00: ATA-10: TOSHIBA HDWG31G, 0601, max UDMA/133

Jul 2 15:37:39 Node304 kernel: ata13.00: 31251759104 sectors, multi 16: LBA48 NCQ (depth 32), AA

Jul 2 15:37:39 Node304 kernel: ata13.00: Features: NCQ-prio

Jul 2 15:37:39 Node304 kernel: ata13.00: configured for UDMA/133

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] 4096-byte physical blocks

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] Write Protect is off

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] Mode Sense: 00 3a 00 00

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] Preferred minimum I/O size 4096 bytes

Jul 2 15:37:39 Node304 kernel: sd 13:0:0:0: [sdf] Attached SCSI disk

Jul 2 15:37:41 Node304 emhttpd: online: TOSHIBA_HDWG31G_Z3H0A00QFX0G (sdf) 512 31251759104

Jul 2 15:37:41 Node304 emhttpd: read SMART /dev/sdf

Edit no 2.

OK. So I've managed to get the disk in the array. It took 18 hours to clear (a second time), then formatted, then brought the array online. I then shut the server down and brought it back up. ThunderBay is missing.
echo 1 > /sys/bus/pci/rescan

does nothing.
I shut down. Remove Thunderbay. Turn back on. Wait until system is settled.
I then run
echo 1 > /sys/bus/pci/rescan
and the drive shows up in unassigned for a split second before disappearing. I wait for 30 seconds, then add an extra slot to the array, forcing the missing disk(s) to show up where it's expected.

I have tested spin down on it, let it sleep then wake it up. No drop offs.

This isn't ideal. I would like to be able to boot Unraid with it plugged in, but beggers can't be choosers.

Edited July 4, 20251 yr by elmuziko