ich777

That depends on the Codec that they are using... My suspicion is that they use a fairly new codec/options to transcode the media and those old cards not very capable in terms of codecs, even h265 is not supported. I will report back when I tested this on my Nvidia T400.

This has nothing to do with the GUID, I think it's a different issue. May I ask what Motherboard and CPU you've had before and what Motherboard and CPU you are running now? Exactly, this is not needed for this container. Have you yet tried to change the Display in the template to 1? I would recommend that you reboot the host if you change this value from one to another.

Also wenn es nichts kritisches ist, mach entweder einen 2. Cache Pool mit nur einer Platte und XFS oder du bindest das ganze mit Unassigned Devices ein. Ist dir überlassen, ich würd einen 2. Cache Pool machen wenn du die Platte direkt einbauen kannst und du die Platte dann auch als 2. Cache verwenden kannst der die Daten dann auf's Array schaufelt. Oder du machst das ganze über Unassigned Devices mit einer Externen Platte aber dann musst du die Dateien irgendwie selbst aufs Array schaufeln mit einem Skript oder dergleichen oder du lässt es einfach auf der Platte liegen.

Darf ich fragen welche Container? Ich würd generell alles was dauernd liest schreibt auf dem Cache behalten oder auf einer Platte in Unassigned Devices wenn es nichts kritisches ist das gespiegelt werden sollte.

Warum mach das System das? Ich hatte noch nie probleme damit, aber wie gesagt hier gehen die Meinungen stark auseinander...

Oh, that's too bad, but I'm not sure how the 1660 would act in a x4 slot, it always depends... Are you sure that you don't have a option like "PEG/PCI/PCIE" in your BIOS to set the main graphics card?

Update the plugin and you won't see the message on next reboot, have already update the plugin.

Schon mal neu gestartet, sprich System ganz stromlos machen und vom Netz trennen, dann den Ein-/Aus und den Reset Schalter ein paar mal drücken (zum Caps lerren), 30 Sekunden warten und dann wieder ans Netz und einschalten, vielleicht hilft das. Vielleicht sind auch die SSDs kaputt, ist alles im Bereich des möglichen. Ich würde beim Cache eher zu Samsung oder Crucial SSDs tendieren. Kenn diese Intenso nicht und weiß nicht wie "gut" die sind.

This is actually not an error, it tells you that ERST support is enabled.

This link is dead... From the console? Was GVT-g working or not? This is only a cosmetic issue.

Simply try it with various games and you will have the answer, maybe someone else has test this. As @ghost82 said, SeaBIOS is not an option because this is basically Legacy (CSM) boot and Windows 11 needs UEFI that is basically OVMF.

The last time I tried it it was working just fine because I made a custom ffmpeg version that supports NVENC for this container. What card are you using? Are you transcoding any streams currently? I will try it a little later, please see this post where I added NVNEC support for the container:

Is the second slot not shared with the first slot in your system, like it is the case on Intel systems?

This will make no difference even if you put it in a PCIe 3.0 8x slot, same goes for my 1070Ti.

Can you maybe try to disable this option and see which card is the console output? I think it would be best to use the 1050Ti for console output since you are using this card in Docker containers. If the console output from unRAID happens on the wrong card, simply try to swap the PCIe slots for the cards physically.

I think you can't install a AMD Chipset driver because the Chipset is recognized as OVMF because it's actually emulated (you can't use the hosts chipset anyways) and not as AMD, I don't think you can change that.

Where did you see this message? Have you got any Diagnostics? Can you please post the output from: find /lib/modules/5.14.15-Unraid/ -name "*mdev*"

No, that won't solve nothing also I don't think that's the root cause of the issue, have you somewhere your Diagnostics? You also have to know I'm not the specialist when it comes to VMs and Passthrough, what card is the primary display output? The 1050Ti from your signature? If you have two cards in your server I think you don't even need video=efifb:off if you have set the primary card to the 1050Ti in your BIOS.

No, it's only a indicator if the card is properly recognized in the container if the command is available, but also keep in mind that it is also possible that you get another error if you try to open nvidia-smi in the container of missing libraries. Better speaking if nvidia-smi is available in the container you've passed through the command --runtime=nvidia properly. It is always a question that I ask because sometimes this argument from above is missing in the container template at the Extra Parameters.

The GT1030 should work just fine, you can always check what cards are supported here, simply click on "Supported Products" (in this case it's for driver v495.44 This card will only work with the v470 drivers.

Are you talking about the Nvidia Driver plugin on unRAID or in a VM? What card do you own? Please remember 600 and 700 Series cards where dropped from Nvidia with the new driver versions, the v470 drivers are the last ones that support those cards.

The maintainer from the container has to change that, for example Handbrake needs to be compiled with NVENC support. Here is an alternative to the container on the CA App: Click (from what I know it should be compatible to the existing template on the CA App, you only need to switch the repository). Sorry I'm not very familiar with Tadarr... What do you mean exactly with "commands to the client"? Have you looked at the description, maybe it is mentioned there what you have to do. Also please see the second post what you need to add to the template. In the container console? If yes, then it basically works in the container but if the application was compiled without NVENC/CUDA support then it can't make use of it. Hope that makes sense to you. I also got a few reports about Plex that not all containers work on the first try and even a user solved this issue by deleting the container and installing it from scratch with the Nvidia necessary entries. Also a few posts above the same happened with Emby: Click These should support the Nvidia transcoding, I also run Plex (official repo) and Jellyfin (my repo) and transcoding is working just fine. No, you don't need UEFI turned on, I also run my server with Legacy (CSM) and it is working just fine, sometimes, or at least with older drivers I had some issues with UEFI where the card wasn't properly recognized by the driver itself. Anyways UEFI and Legacy (CSM) should work fine.

I really don't want to change anything to the template. Such changes are up to the user since this game is in "alpha" and they will fix the issues that are currently happening in upcoming versions from the dedicated server I think, like it was the case for Valheim.

Welche treiberversion hast du denn installiert? Beachte das Nvidia die "alten" 600 und 700 Serie in den neuen treibern rausgeschmissen hat. Für die 600 und 700 Serie musst du einen 470er Treiber wählen, alle die über v470 sind unterstützen dies Karten nicht mehr. Bitte check auch mal ob du im Nvidia Driver plugin deine Karte überhaupt angezeigt wird. Sent from my C64

This could have various reasons and is maybe don't related to the plugin. What Handbrake container are you using, keep in mind that the container or better speaking the app has to be built with NVENC support so that will work, from what I know the currently available Handbrake container in the CA App doesn't support NVNEC at all. Which container are you using, never used Folding at Home but maybe I could try it if it works on my system. I now tried on my development server to change the drivers back and forth with reboots in between but I don't experience any Parity checks at all, I'm currently on unRAID v6.10.0-rc2 but that shouldn't matter at all. If you are able to pass the argument '--runtime=nvidia' to the Extra Parameters in the template and the container starts up fine then everything went well. You also could try to run 'nvidia-smi' in a container console window as root and see what the output is (keep in mind that this maybe will not work in every container).