Crawdadius

Turns out that this is a known issue with reporting tools and Intel Arc GPUs. After fiddling with different slots and removing other PCIe devices I did a little more searching and found this info on the Intel graphics support KB.

A while back I jumped at the opportunity to switch from LSIO Nextcloud + mariadb images to Spaceinvader's AIO image and I haven't had any issues with it. Seems to have better performance than the former. Also, makes it effortless to add Collabora and increase functionality of Nextcloud Talk without faffing around with STUN/TURN server settings, which require a lot more setup with the LSIO image. I just followed the video guide. You definitely want to keep Nextcloud storage on it's own share and generally refrain from modifying those files from outside of Nextcloud. But if you want to access other stuff on your array through the Nextcloud interface then you can add the "NEXTCLOUD_MOUNT" variable to the AIO container and point it to whatever directory on the host you want to mount with the "External Storage" plugin inside of Nextcloud. You want to update the containers via the AIO interface rather than from the unRAID docker management page. From within Nextcloud, go to Administration Settings > Overview and click on "Open Nextcloud AIO Interface". I believe if there are updates available then you'll be prompted to do it from there. I have enabled auto-backups and auto-updates within the AIO interface per the SpaceInvader setup video. Slightly annoying that the unRAID interface constantly prompts to update the containters, but I've just ignored those warnings within Fix Common Problems. This is the way to go, IMO.

Hello Friends, Just recently upgraded from Xeon e5-2678 v3 with GTX 1060 to Ryzen 5900XT with Arc a380. Upgrade was easy! Everything is working, but I noticed that GPU Statistics plugin shows "PCIe Gen (Max): 1 (1)Lanes (Max): 1 (1)". Running "lspci -vv" confirms this on the a380. LnkSta: Speed 2.5GT/s, Width x1 I believe Arc a380 should be able to utilize the full PCIe Gen4 x8 speeds with my configuration. Any advice to get this working would be greatly appreciated! Running unRAID 7.0.1 on ASRock x570 Taichi with Ryzen 5900XT Sparkle Arc a380 ELF in slot PCIE1 Intel 82599 in slot PCIE3 WD SN750 in M.2_2 LSI 9211-8i in slot PCIE5 (running from chipset)

Info about this change can be found at this issue on the imagegenius github page. The suggested fix worked for my instance. I'm up and running again without any apparent issues.

Hey sorry for the late reply, I haven't had time to fiddle with this until now. Thanks for the instructions. I've used this rollback process before for another container and it is simple enough. I was able to pull down the 1.3.15_18_ge050905b2-1-01 bulid. Unfortunately none of my torrents appear in the client after reverting. Looks like I'm just going to have to add them all back in manually. No worries though, I will just continue to use the latest build with sonarr/radarr on the trackers that are compatible and create a new instance with 1.3.15 so I can keep seeding until the rest of my trackers add support for V2. The new interface is really flying and I am loving it. Thanks again for your hard work and assistance, binhex. You are the man!

Yeah, this update to v2 is actually a real problem for me as well. @2twisty You probably need to update your thin client to 2.03 in order to get it to connect to your Deluge daemon in the Docker container. Larger issue for me is that v2 is not supported by any of the trackers that I use (in fact a few of them have blacklisted it). The remote interface is far more responsive than it was with 1.3.15 but I cannot make the switch to v2 until my trackers decide to add support. Does anybody know if there's an easy way to roll back without having to re-check all of my torrents? Can I just use the "state" folder from my updated v2 instance in a new instance that is running 1.3.15?

Oh man, I was SO EXCITED when I saw an update available. I should've checked here before upgrading but now I've got the same issue as above. I know you'll get it sorted but I just wanted to say - Thank you so much for your work on this container! I am blown away by the rapid progress of this project and I'm excited for it to fully replace Plex.