craigr

EDIT: Solution Today I setup a separate physical nic for unRAID server and another physical nic for my docker containers and VM's. I have everything working perfectly except for the fact that I cannot access the WebGUI for binhex-delugevpn. I can access binhex-delugevpn GUI by using my Win10 VM with Deluge 2.0.4.dev38 setup as a thin client and connecting to the binhex-delugevpn docker that way. This is not a VPN issue or normal WebGUI issue. In fact, this is the supervisor.log: 2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started I can access all other docker WebGUI's including binhex-nzbget, binhex-krusader, PlexServer... This is my network config in unRAID, docker config, and delugevpn config. Any ideas on what the problem may be? Thanks, craigr

Hey this problem still exists in a different way on binhex-delugevpn. There is no way to get to the WebGUI even typing it in directly. The only possibility I have found is to use deluge running (in my case on Windows 10) as a thin client. Anyone have any ideas? Also bonienl, thanks for your help as always. I had everything working well, but what I did was not quite technically correct. Your guidance stopped the errors in Fix Common Problems In my case, I have one 10Gb connection for unRAID server and another 10Gb connection for my Win10 VM, deluge, and binhex-nzbget. It's working nicely because I have 2.5Gb internet service and my switches only support 1Gb and 10Gb, but my router has a 5Gb WAN and one 5Gb LAN, so I can hook the 5Gb LAN directly to unRAID now and have it for downloading torrents and nzb files and for my VM's. Another 1Gb ethernet port connects my router to my switch. Interestingly, the binhex-nzbget WebGUI works fine even though it is on br1 along with binhex-delugevpn. What's up with that?1? craigr

So I asked my friend who found that case how he found it. He said he started searching for "mining server case." I don't know why mining cases apply as mining generally doesn't need lots of storage, but that was the key for him. I'm curious if you guys ever come up with any other cases that way. craigr

I just found it here at Lazada as well. https://www.lazada.com.ph/products/14bay-hard-drive-tower-multi-disk-storage-server-desktop-computer-chassis-atx-compatible-main-box-quasi-power-supply-chia-mining-i2529032021.html craigr

A friend of mine found this case on Ali: https://www.aliexpress.com/item/1005003148866235.html 14x 3.5 bays up the whole front. Anyone tried it? It's pretty pricey at $257 without power supply (PS is optional). Looks ideal if it's not garbage. Is it similar to any other cases? Thanks, craigr

Man I always read the release notes too. Don't know how I missed that. Thank you! craigr

Sorry if this has been covered, but how are we supposed to run automated backups of the USB boot drive now? In Appdata Backup/Restore v2 it clearly states, "NOTE: USB Backup is deprecated on Unraid version 6.9.0 It is advised to use the Unraid.net plugin instead." However, I have searched for this "Unraid.net plugin" in CA with no luck and have googled many variants also with no luck. What's the deal? Right now I continue to use Appdata Backup/Restore v2 for USB backup despite the fact that it's deprecated. Thanks, craigr

I'm having the issue with cacert.pem. I replaced the modified cacert.pem file, but it does not help me. I am unable to upgrade to 21.1 when prompted. Any ideas? Spaceinvader to the resque again: Thanks craigr

Could you please point out where in the release notes where the workaround is. I have looked and do not see it. Sometimes release notes become scatter. I looked at these: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0 https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.2 I can't get pihole to run with the custom servers. I'd like to get that working, but for now I have just substituted 1.1.1.1 and 1.0.0.1. Thanks, craigr

I'd really appreciate a link, thanks. I'd like to know because I am not sure I understand. When the container launches it does so quickly so I don't think it's downloading any updated version or anything. For me, with the official PLEX docker it was the only repository that actually allows me to get the PLEXPass version properly. I now have been suspecting this may be why I wasn't having issues when others were. Kind regards, craigr

If you are running the official PLEX docker and want to run the PLEXPASS version, you should also change your repository to: plexinc/pms-docker:plexpass craigr

Yeah, it doesn't matter if the file or directory is there or not, just create it. You can use: touch /boot/config/modprobe.d/i915.conf Or simply navigate to the directory in your FLASH share and use Windows or whatever OS you are running. I did it in my VM's GUI. craigr

For whatever reason, I do not need to downgrade PLEX. On my system hardware acceleration of all kinds including h.265 4k HDR with tone mapping is working properly on all of the newest PLEX Server releases. My config is in my signature. Just saying not everyone may need to downgrade PLEX. I have no idea why it works fine for some and not others. craigr

Updated from 6.9.1 with no issues so far. VM's and dockers all working fine. craigr

https://forums.plex.tv/t/4k-hdr-hevc-hw-transcoding-is-broken-on-1-22-1-4200/702328/39 This is what I am wondering about for you? craigr

I just crawled out of bed and tried with tone mapping on or off, both work fine. I am using the official PLEX server docker. Based on your thread, the problem may be only with certain CPU's. I'm running an Xeon E-2288G. craigr

I think I read somewhere this was an issue but I thought it was solved. I’ll try turning mine off and on later if I can (got second covid shot yesterday and it kicked my butt). It may be that you need plexpass for it? Do you have a license? craigr

All the info is in the documentation. There is also plenty on runnin the Nvidia drivers. https://wiki.unraid.net/Unraid_OS_6.9.0#GPU_Driver_Integration See what happens if you leave “chmod -R 777 /dev/dri” in your go file. Mine didn’t need it, but some may. craigr

i915 Is for the Intel’s GPU. you can also create the file in windows just by navigating there and creating a new text file with extension .conf. craigr

This guide by lotetreemedia has been very helpful for me, but starting with unRAID 6.9.x the steps that are unraid specific should be done differently because unRAID has implemented GPU drivers. Everything lotetreemedia says to do in PLEX is still valid, but activating the driver is different. If you have lines in your "go" file you should remove them and change unRAID as follows: https://wiki.unraid.net/Unraid_OS_6.9.0#GPU_Driver_Integration After completing lotetreemedia 's steps in the PLEX docker, all I had to do to get QuickSync working with 6.9.1 was remove the lines from my "go" file and create a file in \flash\config\modprobe.d\i915.conf. The i915.conf file is just empty. craigr

All 17 data drives were spun up; not the PARITY drives though. craigr

Well hold on. I had rebooted earlier today and the drives had only had the SMART read once since then. I just restarted File Activity and each drive, one by one, is getting spun up and SMART read. This will require further investigation so I'll play with it. craigr

All my info is in my sig if you need it, version 6.9.1. I was running the file activity plugin, but I actually turned it off to test if this was causing the issue. Not surprisingly it's not the file activity plugin. With file activity running, it does not show any files being accessed either. The only thing is that the log says SMART is checked and the drive is spun down. craigr

Yeah, I have been wondering about this too. Mar 12 12:02:55 unRAID emhttpd: spinning down /dev/sdn Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdg Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdw Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdd Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdt Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sde Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdu Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdr Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sds Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdq Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdp Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdm Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdj Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdh Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdf Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdv Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdo Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdi Mar 12 14:06:20 unRAID nmbd[11338]: [2021/03/12 14:06:20.406871, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 12 14:06:20 unRAID nmbd[11338]: ***** Mar 12 14:06:20 unRAID nmbd[11338]: Mar 12 14:06:20 unRAID nmbd[11338]: Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.15 Mar 12 14:06:20 unRAID nmbd[11338]: Mar 12 14:06:20 unRAID nmbd[11338]: ***** Mar 12 14:41:42 unRAID emhttpd: read SMART /dev/sdj Mar 12 15:26:55 unRAID emhttpd: read SMART /dev/sdh Mar 12 16:09:26 unRAID emhttpd: read SMART /dev/sdi Mar 12 16:10:19 unRAID emhttpd: read SMART /dev/sdw Mar 12 16:11:08 unRAID emhttpd: read SMART /dev/sdu Mar 12 16:12:35 unRAID emhttpd: read SMART /dev/sdf Mar 12 16:12:46 unRAID emhttpd: read SMART /dev/sde Mar 12 16:13:23 unRAID emhttpd: read SMART /dev/sdd Mar 12 16:13:42 unRAID emhttpd: read SMART /dev/sdq Mar 12 16:13:57 unRAID emhttpd: read SMART /dev/sdp Mar 12 16:14:24 unRAID emhttpd: read SMART /dev/sdt Mar 12 16:14:42 unRAID emhttpd: read SMART /dev/sds Mar 12 16:15:34 unRAID emhttpd: read SMART /dev/sdr Mar 12 16:16:03 unRAID emhttpd: read SMART /dev/sdv Mar 12 16:17:54 unRAID emhttpd: read SMART /dev/sdg Mar 12 16:52:49 unRAID emhttpd: read SMART /dev/sdn Mar 12 16:55:00 unRAID emhttpd: read SMART /dev/sdm Mar 12 16:55:00 unRAID emhttpd: read SMART /dev/sdo Mar 12 17:11:09 unRAID emhttpd: spinning down /dev/sdu Mar 12 17:12:47 unRAID emhttpd: spinning down /dev/sde Mar 12 17:14:00 unRAID emhttpd: spinning down /dev/sdp Mar 12 17:14:27 unRAID emhttpd: spinning down /dev/sdt Mar 12 17:14:45 unRAID emhttpd: spinning down /dev/sds Mar 12 17:14:53 unRAID emhttpd: spinning down /dev/sdd Mar 12 17:15:51 unRAID emhttpd: spinning down /dev/sdr Mar 12 17:16:22 unRAID emhttpd: spinning down /dev/sdf Mar 12 17:16:29 unRAID emhttpd: spinning down /dev/sdw Mar 12 17:16:29 unRAID emhttpd: spinning down /dev/sdq Mar 12 17:16:36 unRAID emhttpd: spinning down /dev/sdi Mar 12 17:17:55 unRAID emhttpd: spinning down /dev/sdg Mar 12 17:18:20 unRAID emhttpd: spinning down /dev/sdv Mar 12 17:39:46 unRAID emhttpd: spinning down /dev/sdj Mar 12 17:41:18 unRAID emhttpd: read SMART /dev/sdj Mar 12 17:47:23 unRAID ool www[32538]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'smtp-init' Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdm Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdn Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdo Mar 12 17:56:24 unRAID emhttpd: read SMART /dev/sdv Mar 12 17:56:57 unRAID emhttpd: read SMART /dev/sdi Mar 12 17:57:13 unRAID emhttpd: read SMART /dev/sdr Mar 12 17:57:43 unRAID emhttpd: read SMART /dev/sde Mar 12 17:57:59 unRAID emhttpd: read SMART /dev/sdg Mar 12 17:58:30 unRAID emhttpd: read SMART /dev/sdp Mar 12 17:58:44 unRAID emhttpd: read SMART /dev/sdw Mar 12 17:59:05 unRAID emhttpd: read SMART /dev/sdf Mar 12 18:00:05 unRAID emhttpd: read SMART /dev/sdu Mar 12 18:00:16 unRAID emhttpd: read SMART /dev/sdt Mar 12 18:00:49 unRAID emhttpd: read SMART /dev/sdd Mar 12 18:01:10 unRAID emhttpd: read SMART /dev/sdq Mar 12 18:02:56 unRAID emhttpd: read SMART /dev/sds Mar 12 19:00:21 unRAID emhttpd: read SMART /dev/sdn Mar 12 19:03:21 unRAID emhttpd: spinning down /dev/sdg Mar 12 19:04:27 unRAID emhttpd: spinning down /dev/sdt Mar 12 19:04:57 unRAID emhttpd: spinning down /dev/sdu Mar 12 19:05:09 unRAID emhttpd: spinning down /dev/sdq Mar 12 19:05:12 unRAID emhttpd: spinning down /dev/sds Mar 12 19:05:31 unRAID emhttpd: spinning down /dev/sde Mar 12 19:06:00 unRAID emhttpd: spinning down /dev/sdp Mar 12 19:06:04 unRAID emhttpd: spinning down /dev/sdd Mar 12 19:06:10 unRAID emhttpd: spinning down /dev/sdr Mar 12 19:06:13 unRAID emhttpd: spinning down /dev/sdk Mar 12 19:06:31 unRAID emhttpd: spinning down /dev/sdw Mar 12 19:06:52 unRAID emhttpd: spinning down /dev/sdv Mar 12 19:07:01 unRAID emhttpd: spinning down /dev/sdh Mar 12 19:07:03 unRAID emhttpd: spinning down /dev/sdf Mar 12 19:07:08 unRAID emhttpd: spinning down /dev/sdi Mar 12 19:07:11 unRAID emhttpd: spinning down /dev/sdj Mar 12 19:11:23 unRAID emhttpd: read SMART /dev/sdk Mar 12 19:23:44 unRAID ool www[4095]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Mar 12 19:27:41 unRAID ool www[5874]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Mar 12 19:42:11 unRAID ool www[24315]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Mar 12 20:00:22 unRAID emhttpd: spinning down /dev/sdn Mar 12 20:41:34 unRAID emhttpd: read SMART /dev/sdj Mar 12 20:42:54 unRAID emhttpd: read SMART /dev/sdv Mar 12 21:51:09 unRAID emhttpd: spinning down /dev/sdj Mar 12 22:11:40 unRAID emhttpd: spinning down /dev/sdk