Hoopster

I assume you are trying to switch to Wireguard instead of Open VPN? I believe that in the template-based DelugeVPN docker container for unRAID you just have to make sure the container is set to privileged. You should not have to create anything. Then create the VPN_CLIENT key with the wireguard value as instructed. I am also a PIA user and have it set to Wireguard (the wg0.conf exists as it should) in the above manner.

Obviously, had that happened to me, I would also be frustrated. However, it is clearly not a generic problem that affects everyone. I have been through updates to 6.9.0 RCs, 6.9.0 and 6.9.1 and hardware transcoding has continued to work for me without any problem in both Plex and HandBrake (I don't use Emby) on two servers. If that were a general issue, there would be many, many complaints in these forums. Since adding the modprobe i915 capability directly to unRAID was a new feature in 6.9.0, I am sure it was tested extensively in their labs. The real problem is they cannot test all hardware, docker, plugin, VM, etc. combinations and, invariably, there are scenarios where problems appear. The good news is you found a solution that works for you but it would still be nice if the real problem was able to be identified. There were some docker related issues for some in the latest upgrade and perhaps that affected you.

You best best might be to use a power supply sizing calculator to determine how many watts your rig draws when at full load and then plug that number into a UPS calculator. This is for APC specifically, but anything that provides the recommended protection from other manufacturers should be OK.

On certain motherboards, taping over pins B5 and B6 on the PCIe connector of the card is necessary to get the board recognized. I had to do this with my Dell H310. Although this is very common with the H310, the IBM M1015 is essentially the same card and, in some cases, tape is needed on them as well. See this post for more details.

What is your indication that the card is "down" and does not work in unRAID? In Settings --> Network Settings does the interface appear? Here is my second NIC (eth1) which I have taken down in unRAID by clicking on the Port Down button. FYI - if the Port Down button is active, the NIC is actually active and recognized by unRAID. If the Port Up button is active (as seen below), it means the card has been deactivated and can be brought up again in unRAID by clicking the button.

FYI - obviously not a common problem, but 6.9.1 refused to show up for me in Tools --> Update OS. I was able to update the old fashioned way by downloading 6.9.1 from unraid.net and manually copying over the bz* files to the flash. Even though it now shows 6.9.1, this is what I saw in Update OS when on 6.9.0 as well (status unknown and no update appearing and no way to check): EDIT: And just to be clear, there was no check for updates button in the GUI just like there is not one now. On the backup server, things functioned normally,

Well, that was interesting. I too got the "multiple NICs on same subnet" message from FCP. I had forgotten I even had eth1 assigned in unRAID as it was not serving any real purpose. I thought, what the heck, I'll make an active backup bond with the two NICs. Bad choice apparently. Fortunately I did backup the flash before making this change and that saved my bacon. When I made the bond and l clicked apply, I lost network connectivity on my entire LAN, Nothing with a wired Ethernet connection had Internet access and, of course, I lost the unRAID GUI. WiFi still worked. I pressed the power button to down the server gracefully, or so I thought. As soon as the unRAID server went offline, all network connectivity was restored to the rest of the LAN. I then copied over the config folder from the flash backup (instead of just network.cfg because I did not know if anything else was impacted.) After restoring from backup, the server again booted properly but it started a parity check which I cancelled for now. Everything is back the way it was and I will just start by taking down eth1 in unRAID and disconnecting the cable.

Right. As I said in a prior post, you need to install network and other missing drivers from the virtual dvd drive. Go into Device Manager, right click on network adapter, update driver and tell it to look for a driver on the pc by specifying the virtual dvd drive. Repeat with other missing drivers. Sent from my iPhone using Tapatalk

Not currently. The VM is more for experimental purposes and right now I am just connecting via VNC.

You are correct. The IOMMU groups on this board do not separate out the USB controllers as there appears to be only one. If you want to pass through a USB controller, you will need to install a PCIe USB controller that should then be in a separate group. I even installed a USB 2.0 card in the server connected to a motherboard USB 2.0 header for making sure I was booting unRAID from USB 2.0. However, that is not a separate controller as all USB ports from the PCH are tied to the same controller. Of course you could also try the acs override method to try and breakout a usb hub from the controller.

A VM BIOS has nothing to do with your actual motherboard. VM stuff is a virtualization of actual hardware. The bus types in the VM config will specify what type of devices are emulated. I set mine to USB 3, SATA, etc. At some point in the install, you will also need to specify virtual disk drivers before you can select a “disk” to which to install Windows. You will also need to install network and other drivers by looking for drivers on the virtual DVD drive. Sent from my iPhone using Tapatalk

I set mine to SATA and still got the Shell> prompt. I was able to get out of it, however.

Not that I have seen. The CPU temps look roughly the same in Performance mode as they did in Power Save mode. I'm not sure Power Save really buys you much other than it taking longer to ramp up CPU speeds. I suppose power consumption might depend on if you were doing any heavy in either unRAID or a VM. At idle/low usage, I see no difference.

You can try typing "exit" at the shell prompt to see if that takes you to the Tianocore BIOS screen as it did for me. Once there, you may need to select the UEFI DVDROM as your boot device and then you should be on your way. If I recall correctly, "exit"ing the shell is what got me going.

No, I enabled Turbo Boost a few months ago. Through the Tips and Tweaks Plugin I had the CPU Scaling Governor set to Power Save and on this setting, the CPU would throttle down when idle; sometimes as low as 800 MHz. I decided to install a Windows 10 VM yesterday and read that there were many performance issues with VMs with the Scaling Governor in Power Save mode. Performance mode is recommended (or On Demand if CPU uses cpufreq driver rather that Pstate). I now have it on Performance with Turbo Boost enabled and I see very high CPU frequencies. Here is Power Save with Turbo Boost disabled. And here it is after sitting idle for about 20 minutes with Power Save and Turbo Boost enabled, but I suspect I caught it before Turbo Boost kicked back in after being enabled. In all cases, the VM is running.

Since updating to 6.9.0 and the accompanying reboot 5 1/2 days ago, the unRAID WebGUI via the System Temp plugin has been reporting proper MB temps in the 26-31 C range, but IPMI continues to report MB temps from 83-88C. Who knows how long it will be until the System Temp plugin decides to once again join the madness. No lockups though so there is that.

Yeah, not sure why that would make a difference but the important thing is that it is working. The solution I suggested is one that is mentioned in the Plex forums for those with EAC3 audio issues. Your problem obviously had a different solution but at least there is a solution.

Delete the codecs folder in [path to your Plex appdata folder]/Library/Application Support/Plex Media Server This will force Plex to again download codecs as needed. It is likely some corrupt codes are causing EAC3 audio issue.

I was using AquilaWakeOnLAN from my Windows desktop to wake up the server and it worked great. I had a different utility on my phone. It does have a scheduler but that may only work on the machine on which it is installed. May be worth checking out. If your server wakes up and then shuts down shortly thereafter you might want to go through your BIOS settings or check the NIC settings, etc.

I used it to wake my backup unRAID server; but then I was waking it from another server. Perhaps it cannot be used to wake the actual machine on which it is installed (which makes some sense). That I do not know. Installation of it also allowed me to use etherwake in scripts to wake/sleep my server when backups were finished.

I used to have this WOL plugin installed, but I am doing things differently now that I have IPMI boards. I can't recall what functionality it provides but it may be worth a look.

Doubtful, since unRAID has no bearing whatsoever on how/what things are displayed in the Plex interface. It sounds like something might have been tweaked or corrupted in the Plex databases, especially since you see the same thing in both containers and with multiple Plex clients. Do you have backup of the Plex database from before the problems and have you tried restoring a database backup? EDIT: You might find this helpful.

I am glad that worked for you (others as well), but it is certainly not normal or expected. Have you tried a reboot after it came up and did it take that long again? If so, your configuration should be checked as something is not right.

Are you using the Nvidia Driver plugin or the now deprecated and no longer supported Unraid Nvidia plugin? It is failing at that point because it cannot find the appropriate driver. If you are not doing so, you need to be using Nvidia Driver plugin.

You can re-install any previously installed docker container from the Previous Apps section on the APPS tab. It will be configured as it was before with settings intact.