Leaderboard

This release contains bug fixes and minor improvements. Refer to Summary of New Features for an overview of changes since version 6.8. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.c

Next point release can you update docker to 20.10.5 It patches 3 CVE's including these 2 ugly ones: https://github.com/moby/moby/security/advisories/GHSA-6fj5-m822-rqx8 https://github.com/moby/moby/security/advisories/GHSA-7452-xqpj-6rpc

Yeah just a min, actually about 15. I put it on the wrong branch 😆 Ok good to go now, sheesh

BTW, great to see an update already, great work team

Hi Guys, I am a total idiot and can not figure this out. I use delugevpn and radar and sonarr and jackett run thru the delugevpn by proxy. I tried adding the ports to the variable created but nothing works. I am able to get into each of the gui's. Can someone who is running this setup maybe post screen shots of each docker showing what changes need to be done. Or maybe some kind of step by step tutorial. I am really at a loss on what to do. I am messing more s**t up then I will remember what to change back. Thanks again, and I realize this is probably alot of work but

@SavagelyCalm I have the same problem. Edit your Docker repository link to this "binhex/arch-sonarr:v3" and it'll re-download a working version. Worked for me.

6.9.1 breaks this again

Thank you @ljm42.

Easiest is to use a lockfile (or semaphore) Near the start of the script if [ -e /var/lock/scrip.lock ]; then echo "Still running" exit fi touch /var/lock/script.lock Then at the end of your script rm -f /var/lock/script.lock

首先说明，unraid 是买了授权的。 第一我的黑裙用了多年，我的服务器是8盘SAS。 unraid盘是1T的NVME， 安装黑裙直接可以直通我的8块硬盘，虽然Unraid有很多app docker，但我觉得太麻烦，我使用黑裙的备份，图库，文档，以及诸多功能，目前运行一年了依旧非常稳定，承担了很大的业务量； 个人不是NAS重度使用者（万兆NAS做视频），日常用Unraid 直通显卡之类的用用ubuntu 虚拟Win远程 办事 各有所需，Unraid有他的优点，黑裙也有黑裙优点，Unraid能很好的支持我的服务器主机，虚拟机让所有的虚拟系统都可以快速部署，这套系统就已经够用了！

just upgraded. posting what i had to do for others in case they had similar issues to me. docker-compose all of my containers are in a single docker-compose.yml file and that reloaded without any problems after the array was started. hooray! ssh per the release notes, a password is required now. i enjoy the convenience of no password so i ended up just setting up private key authentication instead. and...that's it. pretty seamless upgrade. thank you!

I imagine this may be an issue for others so posting my experience here: After upgrade from 6.8.3 (all smooth), I removed the following from my go file: modprobe i915 chmod -R 777 /dev/dri I then created the blacklist override as per release notes and rebooted: touch /boot/config/modprobe.d/i915.conf This correctly loads the i915 module: root@Tower:~# ls /dev/dri by-path/ card0 renderD128 However the permissions seem to be an issue: root@Tower:~# ls -la /dev/dri total 0 drwxr-xr-x 3 root root 100 Mar 3 11:57 ./ drwxr-xr-x

Yeah that shows me what I needed to see. I will push a fix for it tonight or tomorrow morning and then issue a plug-in update. Thanks for your help and patience. You can uninstall/reinstall to set everything back to normal.

Thanks for the update to the guide mate

@CHBMB, @aptalca, @memphisto, everyone else who thinks I somehow disrespected anyone here, would you have felt the same way if we just integrated the bloody Nvidia vendor driver right into Unraid OS distribution like we do other vendor supplied drivers: RocketRaid, Realtek, Tehuti? It is not difficult to do this; actually it's quite easy. The problem is, this driver alone along with support tools adds 110MB to the download and expands close to 400MB of root file system usage. Only a fraction of Unraid users require this, why make everyone bear this cost? Same situation for all the other dr

Ok so I just added a path in the Krusader container settings (attached), restarted the container, and that seemed to solve the issue.