egtrev

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

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. I've attached what I now have in Flash section. First option was Enabled, I've now Enabled Boot Support and disabled Resizable BAR - I couldn't find the GPIO3 option. 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 72Also 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

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

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

WD Black SN7100 4TB is the drive inside the TB3 enclosure. nvme4n1 is what unassigned devices had as the reference when it showed up.

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

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?

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

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

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.

See attached, fresh reboot drive showing/working. unraid-diagnostics-20260311-1725.zip

See attached, this is taken with drive plugged in but not showing in unassigned devices. unraid-diagnostics-20260310-1919.zip

I've disabled Docker completely and enabled it again on Unraid and everything seems to be working now, just restored my backup from old Unifi container and all seems to be working great, devices all showing online. Thanks for your help with this.

There are no other Docker containers running when I get the error (I have others dockers installed but stopped)

I did check that and there is nothing else showing as using that port except this container (container shows in Docker installed even though this error but if I start it then execution error) Note if I manually clear/delete the container and manually change this port when installing (example 1922) the message then changes to the same error except with the new port instead (example 1922)