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)

Hello, I'm having issues trying to move from old Unifi Docker to this, I have taken a backup but when installing this Docker I get the following: docker run -d --name='unifi-controller-reborn' --net='bridge' --pids-limit 2048 -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UNRAID" -e HOST_CONTAINERNAME="unifi-controller-reborn" -e 'MEM_LIMIT'='4096' -e 'MEM_STARTUP'='2048' -e 'UMASK'='002' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:8443]' -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg' -p '8443:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8080:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw' --memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100 --tmpfs /tmp:exec,uid=99,gid=100 '11notes/unifi:10.1.85-unraid' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 838bb77e1a975b2b1fc32eb82c0d3b7cde527f563b43c78054fbd6e944de55f4 docker: Error response from daemon: driver failed programming external connectivity on endpoint unifi-controller-reborn (0d11e26333500a88b486606d2a5d74e83bb5cf93f5597734a8aadf6549d73b7d): failed to bind port 0.0.0.0:1900/udp: Error starting userland proxy: listen udp4 0.0.0.0:1900: bind: address already in use.

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.

Thanks, I ended up waiting all done now. A secondary question, save me opening a new thread: I'm now left with an old drive that can be removed from the array, is using the built in Unraid file manager GUI a suitable way to move data/folders from Disk3 to Disk1 etc before zeroing the drive out? I've seen a lot of people mention unbalance and krusader, but the built in Unraid file manager seems to be suitable, I just want to check before I started using it.

Hello, I am in the process of upgrading my array, I've started the Parity upgrade/rebuild first in maintenance mode just to be safe in case one drive fails during this. I have a ZFS mirror pool with daily data/shares I use, is there any way to have that accessible during this process or will I just have to wait a few days until it finishes?

Thanks for the response. MariaDB is showing up to date. I only ran the occ upgrade command for troubleshooting just to check if that worked, the 'latest' tag did auto upgrade and failed with the same error. I can't seem to find get the 30.0.14 tag to work, I can't see that specific release tag on the docker/github either, closest I can fine is "30.0.0-ls345" anything newer ("30.0.1-ls346") gives that same previous error. When it installs 30.0.0-ls345, I can no longer access the WebUI, it eventually times out with http Error 500 in the browser. This is the log from Nextcloud from Unraid docker section after rollback to "30.0.0-ls345" ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 30.0.0-ls345 Build-date: 2024-10-08T11:50:56+00:00 ─────────────────────────────────────── using keys found in /config/keys After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations. Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html [custom-init] No custom files found, skipping... [ls.io-init] done.

Hi all, I'm trying to troubleshoot an upgrade issue. I lost my Dockers apps and have been installing them from 'Previous apps' one by one, due to me not keeping them updated too often I'm having issues. On Nextcloud I'm getting the below errors when updating, any suggestions? I'm on an older MariaDB docker app (which was working fine before losing everthing) databases all look to be intact and MariaDBDcontainer is working/running on usual port.

This is definitely the case, I been going through the Docker container one by one, quite a few work fine from 'previous apps# it just happened that the first few I tried have issues due to age or bugs in newest updates, this is just to be troubleshooted on an app basis.

Sorry, yes can't remember what I had under network for the Dockers. Will post the Diagnostics when back home. Could it potentially be that I just had old versions of these Dockers (I tend not to update much) and now it's pulling the latest ones it's broken them?

I beleive that's what I have already done that, when I re-enabled the Docker it created it again and I don't know if the old one is saved anywhere (I did not realise enabling it would delete what I had) The Previous apps works but the applications do not behave the way I had them, I can remember what custom networks I had. Tailscale doesn't start, SWAG & Jellyfin start but Jellyfin is no longer able to work with the custom subdomain I had. I've stopped there now as everythign I'm trying seems to not works like previously. Is there a way to find where the old Docker vdisk is stored, or has that been overwritten now?

Hello, I recently upgraded hardware on my UNRAID machine, all was working fine but had a couple of crashes that turned out to be RAM which is now fixed. However when I finally got the server back running Docker was not running (I could see my containers on Dashboard) I set Docker to enabled in the settings, after I did that all the containers disappeared, I searched the forum and many threads said to just installed them again from "Previous Apps". I've tested one (Tailscale) and the container seems to pull through old settings, but it does not Start. I've stopped now to seek help before go any further. Is there anyway I can restore the Docker back? (I do have A Flash backup but nothing else)