ich777

@guboehm ja, es liegt an dem Plugin, hab grad noch eine Bestätigung bekommen.

Thank you for the report. Please update the container itself, this is now fixed.

Ich hab das hier gemeint: Das ist sehr interessant, ich werde das mal versuchen bei mir zu reproduzieren und weiter zu leiten.

Wo sind denn deine Diagnostics bzw. wäre ein syslog mit aktivem syslogserver bzw. Spiegelung auf den Stick hilfreich.

Hier auch keine Probleme. Verbrauch ist jetzt sogar besser meiner Meinung nach. Aber ich muss auch ganz ehrlich sagen ich sehe hier nirgends welches System du hast und wie du getestet hast. powersave governor hilft bei mir auch merklich.

Ja, bitte probier das mal. Das ist aber interessant, kannst du das mal weiter beobachten und evtl. einmal das syslog schicken vom rsyslogserver schicken wenn du so eine Meldung bekommen hast?

Kannst du bitte mal testweise das probieren: Stoppe alle container, einen nach dem anderen Klicke auf Reboot Es gibt momentan vermehrt solcher Meldungen über unclean shutdowns aber ich konnte das noch nicht reproduzieren auf meiner Test Maschine bzw. auf meinem Produktiv System. SSH session hast du sicher auch nicht mehr zu dem Server offen wenn du auf Reboot klickst oder? BTW, wenn du den Server mittels Reboot heruntergefahren hast, sollte es sicher sein den Parity Check abzubrechen. Aktivier auch bitte mal den syslogserver und spiegel es auf den Stick bei einem Reboot und schalt es dann nachher wieder aus nur das wir das log bekommen was da vorgeht.

Please include the full Diagnostics, this is only a snippet from the syslog that you've provided. The Diagnostics are essential to troubleshoot such issues.

@almulder did you solve your issue already?

But then you should use something more efficient like a Nvidia T1000 and even consider switching to the iGPU from your 7700 since it is really, really more efficient (a few μW in Idel and depending on your iGPU up to around 12W max). I don't want to start a war in terms of quality but some say that the Intel iGPUs are far superior than Pascal and older NVENC. Sure the Nvidia cards are faster in terms of FPS but do you need that for HW transcoding...? Most applications like Emby and Plex throttle the transcoding anyways. So to speak you even can transcode with a Intel iGPU 4-6 simultaneous streams. Sure I'm the maintainer from the Nvidia Driver plugin and for people who have no iGPU or are in need of 10+ simultaneous streams I completely get the point but for people with only a few streams a Intel iGPU does the job good enough (of course if someone wants to do something else too ). When 6.13 is released ARC will be natively supported and it will also just work, even easier than a Nvidia GPU because you don't have to install a driver that is about 200MB, add three additional parameters to the Docker template (okay, you also have to add one entry) and you don't have to restart the Docker service/entire Server, so I don't see this as a valid argument. I've now run a few test with my Intel ARC A380 on a custom built Unraid version and these cards are fast, really fast (keep in mind that the official 6.12.x release doesn't support ARC) : I haven't tested the power draw yet because this was not my main goal, it was just to investigate what's needed to get them running on Unraid back then. I saw that there where reports about high power draw in Idle but there is already a fix out there (I think). Please keep also in mind that this is more or less a feature request thread and where people can communicate about their Intel ARC experience and custom Kernels, they are not really interested in Nvidia cards because they most certainly already have a ARC GPU on hand and don't want to buy a new one. Hope you get my point and answered most (or hopefully all) of your questions.

Your iGPU is barely used in this screenshot and you won‘t see any power draw unless it is used more. Intel iGPUs are drawing near to 0W in Idle (only a few μW).

This is somewhat related to the path in the template and that I set it by default to /mnt/cache/... but as said that is done on purpose to avoid issues with the game servers itself. But I hope that explains why it may be crashes and won't work anymore.

I introduced this settings to the plugin because of the macvtap change in Unraid and tested this excessively. The only thing that is really necessary is that you enable Host access on the Docker page and that you also tick the box Change networks from existing containers. You can also use virhost0 instead of eth0 but I don't recommend that and would actually not display the correct traffic on the LXC page <- please note that you will now only see the whole traffic for eth0 right next to the containers, this is a downside from macvtap and I can't do much about that.

Please do the following: Enable Host access in the Docker Settings: On the LXC Settings page set the network to eth0, click the Box "Change network from existing container" and then hit Apply: This should do the trick.

This is your issue: Here you can also see that you have date for sonsoftheforest on the Cache and on the disk1: You have configured your appdata share to be moved to the Array and in the template the path /mnt/cache/... is specified, that can't work because every time the mover kicks in it will try to move the data from the Cache to the Array. You have two options, change the path in the template to /mnt/user/... instead of /mnt/cache/... or you can change the appdata share so that it stays on the Cache and is not moved to the Array <- it is recommended that you leave appdata on the cache so that the Array can go to sleep, so I would strongly recommend that you go that route. For the SteamCMD path this is fine because it uses by default /mnt/user/... and it won't cause problems but for the GameFiles I always recommend to use the real path like /mnt/cache/... since for some games it can cause trouble when you use /mnt/user/...

I've just gone through the Diagnostics and can't find nothing obvious, just saw that in your go file: mkdir -p /etc/systemd/system/docker.service.d/ cat I would recommend that you remove these lines (/boot/config/go). May I also ask why you have installed this: hpsahba.plg - 2022.07.21 (Up to date) You don't have any suitable hardware for that plugin installed as far as I can see.

@almulder please use the support thread from the Nvidia Driver plugin as @ConnerVT pointed out. ...please also include your Diagnostics in that post.

You don't need parameters for BattleNet and EpicPrefill anymore, you have to just configure them as for your Steam account and my container will then execute the prefill. This changed a few months back and is also described here how to configure:

Please consider joining @Spectral Force's Discord because he helps me out with support for it because I'm not really familiar with the game: https://discord.gg/VwwYA5h

Then please provide screenshots from your Docker template and from your share where the game is located on, most certainly cache.

I don't think so, maybe the Oxide mod is incompatible now and needs to be updated by the devs. Have you yet went to the Oxide mod forums and see if it is compatible with the latest release of the game?

I've edited my post, please don't get me wrong about my questions. I just want to clarify things for not that experienced users and I not only see that from my perspective. BTW I'm also not mad or anything like that if you build the packages, I'm more than happy if anyone else does it because that means more free time for me...

Can you please be a bit more clear in these two points: Do you plan to overtake further development of the plugin Do you plan to offer the latest stable branch too (regardless how old it is) alongside with a build from the latest master branch I'm just trying if it is worth to switch over to the new plugin because the old one is working just fine and for me personally I want to stay on the stable branch regardless how old it is because for me it is working. The next thing is that it would be beneficial to other users to see that this plugin is built from the latest master branch which in it's current form it doesn't tell and that it is a alternative to the existing plugin: Don't get me wrong, I just want to clarify things and not that experienced users can get confused by two basically "identical" plugins.

Have you yet tried to boot with Legacy Boot (CSM)? In what slot do you have the card? The card reports an error as described in this post:

Is this a new card? You still have the same Xid error in your syslog: Sep 5 11:36:45 Ironman kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 0000(0000) 00000000 00000000