ich777

Yes and no, I would recommend to leave it on something that is non volotile like a HDD ot SSD, but you can of course do it with the downside that some things can/will take longer, because they will be regenereated every time when the cache is deleted. But do I understand that yorrect that you are mounting a directory/RAM disk from the host to /tmp directory inside the container or am I wrong?

Can you please post a screenshot from your template and post your Diagnostics?

Can you post your Diagnostics? Have you yet tried to upgrade to 6.9.2? Seems like something else is wrong, can you do a Memtest on your system?

Dann würd ich im Support Thread vom Container selbst nachfragen.

Please don't do /tmp/jellyfin the directory /tmp is way enough and I always recommend mounting it to /tmp without any sub directories. I don't know what you exactly mean with that... What exact script do you have in the User Script or go file?

Correct, Alder Lake is a differnt thing because it's not "properly" supported by the Kernel on rc4 and older.

What CPU do you have? I‘ve know a few people that had issues when no monitor or HDMI Dummy device is plugged in to the iGPU and they try to transcode, issues like that the Kernel module for the iGPU generetad a Kernel panic, server crashes,…

Do you guys in here have a display connected to the iGPU or do you run it headless without any display connected?

These modules are actually the campaign/scenario that you want to load/play and depending on that you have to maybe put other files in the folder if necessary. This should be documented on the NWN:EE forums.

I have now tried it and it downloaded the binaries without a hitch. Do you have any AdBlocking software somewhere in your network? Did you maybe stop or restart the container on the first start and did not wait for the download to finish? I would recommend to start over by doing the following: Delete the container Delete the nwnee folder that is located in your appdata directory Pull a fresh copy from the CA App and wait for it to fully start for the first time (it will throw an error that it can't find any module anyways on the first start like it did in my log output below) Here is the log from my server: nwnee.log

Thank you for the report, have to look into this. Please give me a few days and I will report back.

I have a bit of experience with BIOS modding and I'm also a member of the win-raid forums, can you point me to a thread over there?

Can you please add the plugin URL somewhere or the link to the source on Github or wherever it is hosted? Also your plugin support link from the CA App points to this thread.

Please update the plugins and reboot, warnings are now hidden.

Unterstützt denn der Container VAAPI bzw. QuickSync (ist fast das gleiche, aber nur fast), für Kamera Streams sollte aber die VAAPI aber auch reichen. Der Container muss HW Beschleunigung unterstützen sonst hast du Pech, selbst wenn du die iGPU durchreichst. Generell ist das ganz einfach, du musst nur Sicherstellen das du die iGPU aktivierst, funktioniert am einfachsten wenn du dir das "Intel GPU TOP" Plugin aus der CA App lädsts. Im Docker template (auf das Symbol vom container klicken und Edit wählen), gehst du unten auf "Add another Path, Port, Variable, Label or Device" und legst dann ein "Device" wie folgt an: Dies funktioniert aber nur wenn du vorher die iGPU aktivierst wie beispielsweise oben beschrieben mit dem Plugin. Vergiss nicht deine CPU kann nur h264: Klick Es würde auch spezielle Container geben für Überwachungssysteme wie zB Frigate oder Shinobi (glaub ich).

Why are you doing this? I can't see any benefit from this? Please remove this script, also remove the parameter that it only has 2GB of memory (this is only the maximum amount of memory the application can consume) and add this to your extra parameters: --mount type=tmpfs,destination=/tmp,tmpfs-size=8589934592 This will basically create a tmpfs on the Docker start in /tmp (yes, that's perfectly fine and should used like that since then there is no chmod or anything else needed) and change the transcoding path in Emby to /tmp

This was done by intention and is the case on most of my containers…

How have you created the container? Do you and your friend have a cache drive? To what is you appdata Share setbin the Share settings in terms of Use Cache? Can you post a screenshot from your Docker template?

You have multiple ways of running the script the easiest would be that you add it as a User Script Do the following: Go to Settings Click on User Scripts Click on Add new script Enter a name for the script, something like "Corel Temp" would be appropriate Click OK Click on the little gear icon where it says "Corel Temp" Click on Edit Script Paste this: #!/bin/bash INTERVAL=15 WRITE_FILE=/mnt/user/appdata/coraltemp.txt while true do echo "$(date "+%Y-%m-%d %T") Coral Temp: $(cat /sys/$(udevadm info --query=path --name=/dev/apex_0)/temp | sed 's/.\{3\}$/.&/' | sed 's/.\{1\}$//')C" >> ${WRITE_FILE} sleep ${INTERVAL}s done Click on Save Changes Click on the Drop Down from "Coral Temp" where it says "Schedule Disabled" and select "At First Array Start Only" Click on "Apply" Reboot your Server By default this script will write a file to /mnt/user/appdata/coraltemp.txt every 15 seconds, you can of course change the path and also the interval if you want too. This will only read the temp from the first TPU if someone else is trying this script... Very courious to see what the issue is on your system... If you want to remove this script do the following: Go to Settings Click on User Scripts Click on the little gear icon where it says "Corel Temp" Click on Delete Script Click on OK Have you changed anything else? Please also post the output from: cat /boot/config/plugins/coral-driver/settings.cfg (simply run this from a terminal from Unraid)

No… not after a thermal shutdown… Looks like a thermal issue… @morethanenough what kind of TPU do you own? Do you have a little Airflow over you TPU or betrer speaking is it cooled enough? A shutdown is troggered in your case at 104.8 C and it seems like your TPU are gitting that temperature, otherwise it wouldn‘t shutdown. Please keep in mind when a TPU isn‘t properly cooled it could be a fire hazard (this is also mentioned in the documentation/specification from the TPUs). That‘s why the USB TPUs run at a way lower clock speed than the PCIe ones… If you are interested I can send you a script wich writes the temperatures into a file so that you can monitor them.

You can always send them directly to me... This is not really an issue at all and I don't think that thay are caused by the Nvidia plugin, rather I think they are caused by another plugin, but I could be wrong about that, maybe I've also introduced such a new message with the update from the plugin where I introduced the automatic update check to it. As said above these are not really issues at all, I don't think you have any trouble running a plugin or something causes instability or am I wrong? This is mostly because I have to run a background process that checks my Github repo every day if there is a newer Nvidia driver available. One background process is also running for the Plugin Update Helper (don't know if you have seen it already in action) which is always running regardless of which Driver Plugin (Nvidia, DVB, ZFS, USBIP,...) you have installed. That are maybe the two things that causes this messages. But as said above these messages will not harm your system in any way, have to look into it if I can hide those messages, but I'm really not entirely sure...

Sure, on the first post in this thread or in the CA App on almost every app from me is a Donate button.

Mach den haken mal raus bitte, klick auf "Apply" und dann öffne ein Terminal und gib folgendes ein und poste den output bitte hier: ls -d /boot/*/ Ich finde solche Aussagen nicht wirklich durchdacht und auch ein wenig bis ziemlich Arrogant, ist dir noch nie ein Fehler passiert...? Man weiß außerdem gar nicht was auf deinem System passiert bzw. ist die Fehlersuche nicht abgeschlossen waum es bei dir nicht funktioniert. Hab es jetzt mal auf meinem 6.10.0-rc4 Server probiert: Vorher: Nachher: Wieder im Ursprungszustand: Bei meinem Test hab folgendes gemacht auf Flash geklickt -> den Haken gesetzt -> dann auf Apply geklickt -> zurück zu Main -> Flash geklickt -> Haken raus genommen Apply geklickt -> zurück zu Main -> Flash geklickt -> siehe letzter Screenshot. Poste evtl. bitte auch mal deine Diagnostics.

Von 6.10.0-rc4 auf 6.9.2 kannst du problemlos downgraden, haben sich keine config Dateien so geändert das irgendwas nicht funktionieren würde, sollte eigentlich immer funktionieren, ausgenommen war downgrade von 6.9.x auf 6.8.x da mit 6.9.x Multiple Cache Pools eingeführt wurden. Du kannst dir auch die zip Datei von 6.9.2 ziehen und die bz* Dateien inklusiver der changes.txt von dem Archiv auf dem USB Stick ersetzen, würde auch einem Downgrade gleich kommen wenn du den alten stick noch hast mit dem config Verzeichnis.

I would not recommend to use a AiO in a Server anyways because what if the pump dies, those coolers are most likely not designed for 24/7 usage and I would rather recommend buying a Noctual NH-U12S or NH-U14S or something similar, depending on what you can fit in your case. Nowadays a good air cooler can keep up with the existing AiOs and they are often quieter and you eliminate a single point of failure by going with an air cooler, the pump... Maybe you can sell your AiO for a few bucks...