uraid

Thank you for the comment (and also @bmartino1 ). After seeing this I tried to hunt down the bottleneck I have in my system and managed to optimize it. Now I'm receiving ~36Gbit/s, so really RDMA is not necessary for this. I retract my vote then, and thanks again!

+1 and bumping. This is essential for networking above 10Gbit/s

Thanks for letting us know and for all the work you've done 🙏

I have this exact card in my unRAID 7.1.4 and also my PC, and the plugin's msftlint crashes for me with a 'segmentation fault'. I've found this GH issue: https://github.com/Mellanox/mstflint/issues/1157 Seems like ConnectX-3 got deprecated in msftlint v4.30.0-1 and the plugin uses v4.31.0. I have ConnectX-4 incoming (should be here ~2 months from now)- will update if they work.

Just after uninstalled this old plugin that I realized the whole Web UI slowness was due to it! Definitely recommend using the new one, even though it requires Unraid >=6.12.3. Worth it

Removing all images that depend on the baseimage and reinstalling fixed that Thank you for the help!!

> find /mnt/user/system/docker -type f -name XDG_CONFIG_HOME -exec ls -l {} ';' -rwxr-xr-x 1 root root 19 Mar 4 00:41 /mnt/user/system/docker/docker/overlay2/1b4c1a6ce7c69003987c594a5c290aadc8bffb182520255ac0437467d8d0e296/diff/etc/cont-env.d/XDG_CONFIG_HOME -rwxr-xr-x 1 root root 19 Mar 4 00:41 /mnt/user/system/docker/docker/overlay2/43e0ae77fc00c2938365c254110c931a887d5081f804135b462180553d366b2a/diff/etc/cont-env.d/XDG_CONFIG_HOME -rw-r--r-- 1 root root 15 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/9dea0516110d7786064b03a3d40baf3dc5c33c025b60e09722ac19393e99a443/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 15 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/9dea0516110d7786064b03a3d40baf3dc5c33c025b60e09722ac19393e99a443/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/3773e9a5770523a0d13e0333e1dc26f0e8fa2c66599458a46d6eed46fbba79a2/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/3773e9a5770523a0d13e0333e1dc26f0e8fa2c66599458a46d6eed46fbba79a2/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/24692c298fd3025a60186296661d0a75f584e7ab7fed986afdb45dcf1b15a686/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/24692c298fd3025a60186296661d0a75f584e7ab7fed986afdb45dcf1b15a686/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/52a704cda63af32cff7eda72a87a90ceebcb8a5b68e56c4696550c275297be63/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/52a704cda63af32cff7eda72a87a90ceebcb8a5b68e56c4696550c275297be63/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 7 Apr 24 06:01 /mnt/user/system/docker/docker/overlay2/4f22de215505b404c4efdd239d47729e5076bdfb642f855ef5c2de9e4fd12851/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/8332619b68ec53c3d0ac9a664723c4ea3788f8ffcaeae9a745998ecf0c64d508/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/8332619b68ec53c3d0ac9a664723c4ea3788f8ffcaeae9a745998ecf0c64d508/merged/run/s6/container_environment/XDG_CONFIG_HOME

Unraid 6.12rc2, Docker data-root as directory on Nvme SSD

Nothing has changed unfortunately

Same here. Also for any docker that uses VNC (MakeMKV + MKVToolNix). Tried reinstalling those containers and resetting their data, but didn't help

Doesn't matter what I do, I cannot boot a 7.0.1 with ARPL loader. Tried v1.1 beta 2 and even old v1.0 beta 3. Tried virtio-net + e1000 network card type. Nothing helps. I can ping it after booting for like 3-4 seconds and then it gets stuck. How do I get the logs? EDIT: logs can be read using `cat /dev/pts/1`. Change ID to yours (from unraid vm logs)

Missed this button Zoomed in too much, and the main confusion was having the top Done button (and I see there is a bottom Done button as well?). Will report back by editing in a couple of hours. EDIT: That was it. Thank you for the help!

Thanks in advance!

I encountered a problem on a fresh install of 6.11.5 with zfs drives. Whenever I try to assign an alias on a disk, it isn't applied. I tried: pool1, Pool1, Pool_1 but whenever I click the Done button I see it didn't change anything. Clicking on the drive settings again - I see its name reset. Am I missing something?

@thecode Thank you! Created a pull request. @Skitals Please merge the changes @Mat W Yeah, that looked like an easy fix so I tried to help out.

I have forked the plugin repository and commited a fix for the stray warning. May you check if you still have the warning after a restart so I'll make a Pull Request? @mrslaw @Snowman @Mat W @GigaTech Can't restart my server to test this unfortunately. https://github.com/uraid/unraid-theme-engine/raw/fix-stray-dash/plugins/theme.engine.plg The only change I've made is this: https://github.com/Skitals/unraid-theme-engine/compare/master...uraid:unraid-theme-engine:fix-stray-dash

Just built locally from source to get new rutorrent v4.0 and works great. Had to replace the `root/install.sh` file line 102 with this one (to get around `git://` deprecation) https://github.com/pyroscope/pyrocore/pull/117/: git clone -b update-to-head-patch "https://github.com/stevezau/pyrocore.git" "/opt/pyrocore" && cd "/opt/pyrocore" ------------------------------------------------------------------------------------------------------------------- EDIT: If someone encounters an error with the `autodl-irssi` plugin: autodl-irssi: __init2: ex: Exception info: No content elem with id autodl-prefs-contents-upload Change the code inside the container in the folder `/usr/share/webapps/rutorrent/plugins/autodl-irssi/` to this pull request: https://github.com/autodl-community/autodl-rutorrent/pull/58 ------------------------------------------------------------------------------------------------------------------- EDIT2: If you encounter an error with the `throttle` plugin like so: throttle: Plugin failed to start. It's because of this commit: https://github.com/Novik/ruTorrent/commit/06222a00375bdd0f1f1b5b58bda29e7025316428 It means the first part of the commit (editing `/usr/share/webapps/rutorrent/conf/config.php`) wasn't applied. Simply add the line: $throttleMaxSpeed = 327625*1024; to your `/usr/share/webapps/rutorrent/conf/config.php` file and enjoy!

Thanks for the help! It worked for me. Seems that the images were rebuilt on Thursday, but saw it only after applying your fix.

Thank you! Deleting the 'README.txt' file from the 'cont-init.d' folder fixed it for me. Python 2 was installed automatically in latest version.

Thank you! Adding '.conf' extension to the configuration files helped me solve it quickly.

Thank you for the hard work! Been using this container for a few years now, so very much appreciated Is there any chance to compile a separate beta tag with ruTorrent v4.0-beta 1 release 10 days ago? https://github.com/Novik/ruTorrent/releases A lot of interesting changes and wanted to try it out. Thanks again!

I managed to kill 2 docker containers that just won't get stopped using this method: The `docker kill` command didn't work either :/

Just wanted to let you know that I've made a PR that fixes the 'manage.py create_library' command to let it create a custom path library and it got pushed to the latest v0.22.0 release This seems to be a problem with the initial scanning of a library. Just restart the docker container and it'll start processing the images. @cedev - Thank you for posting this template! Really appreciate it and also made a PR to fix object and face recognition for rotated photos (like selfies), so should pick up even more photos. For anyone who tries to run a second Redis instance on unraid and can't figure out how to change ports like I encountered, just run inside the container the following command after switching ports: `redis-cli -p {port}`

I intend to ultimately move to wireguard as well, so that's a no for me, but everyone is free to make their choice. Openvpn is more mature and peer reviewed, but seems to be that wireguard has all the attention nowadays

Click on the openvpn-as docker icon -> edit and add to the repository value ":{Version}" . Just don't forget that version is the one I wrote above. Excuse my brevity I'm on mobile