ich777

I will send you a Private Message here on the forums when I have a package available for testing with instructions on how to install and test it. Give me a bit please.

You've only replaced bzmodules and bzfirmware and not bzroot on your currently running machine am I right? Do you have to do any modprobe or anything or is the tuner recognized on boot without any intervention by you? For what Unraid version did you prefer a prebuild package for testing? I have currently compiled it for 6.9.2 but can also compile it for 6.10.0-rc4 if that's what you are after. After everything is working fine I can implement this in the DVB Driver plugin, but some manual testing is needed first to make sure everything is working fine.

@untan wouldn't it be better to build it from the latest develop branch instead of master, it has various fixes for newer tuners from what I see in their Github?

You only install the Kernel module and the firmware file or am I wrong? In the installer is also a UDEV file included, do you installed that too on your system? Currently in the process of compiling the module and creating a basic package before I can integrate it somewhere.

Can you give me a bit more information on this? Is or are these common tuners that are used over there? Maybe I could integrate this in my DVB Driver plugin. I also have to look into this if I can compile this since everything is in Japanese (at least I think)... Do you know other people that maybe can test this or can you create a post on the Japanese language sub Forums here on the Forums (at the bottom at the main Unraid Forums page). I don't know if there that many Japanese users from Unraid here: Click I would really like to make sure that this is working properly. On what Unraid version are you currently? Oh and if you want to mention me here so that I get a notification, make a @ and then write my forum name and click on the pop up: (I've stumbled over this by accident)

From what I see you got a input/output error: Mar 30 01:27:27 Tower kernel: dvbdev: DVB: registering new adapter (SAA716x dvb adapter) Mar 30 01:27:27 Tower kernel: stv090x_write_regs: Reg=[0xf416], Data=[0x5c ...], Count=1, Status=-5 Mar 30 01:27:27 Tower kernel: stv090x_setup: I/O error Mar 30 01:27:27 Tower kernel: stv090x_setup_compound: Error setting up device Is the card working or at least, do you know that it is working? This card maybe needs custom drivers but I'm not too sure if they will compile against a newer Kernel: Click Do you have no other alternative? Where are you located at? Selling the card and picking up a inexpensive TBS or DVBSky card on the used market is maybe the better way to go from my perspective.

Because nowadays you can integrate almost everything with plugins and precompiled Kernel modules. Another reason is because the backup functionality from Unraid itself won't work with custom Kernels/modules. To close it down this was purely my decision because maintaining giving support for it was also sometimes a little hard for less experienced people. Which or what driver(s) do you need? Maybe I can help with a custom package and if someone else can use it I can create a plugin. Exactly, this is how Unraid works, everything from the bz* files on your USB Boot device is loaded on boot into RAM and executed from there and will be wiped after a reboot and will be again loaded into RAM on a new boot. As mentioned above they use precompiled packages with everything (and Kernel modules) included and they are installed on boot with a routine that loads the modules and so on. Keep in mind that is necessary to create new packages for every Unraid version (with the modules included) otherwise the driver plugins won't work. I've automated this process on my server for every driver plugin that is available that when a new Unraid version is found the build starts and the packages are built and uploaded to their corresponding repositories.

You are missing this variable: Please look at the run example on Github (I would also recommend that you try Unraid because there it works just flawlessly because there is already a template for the container available with all necessary variables, volumes,... ) Why shouldn't I? That's my container that I maintain and try to fix such issues and help out. Already pushed another update to the container that should fix this on non Unraid installations (btw, thank you for the report ).

Yes, see this from your log, after about 5 minutes after the driver got installed it runs into a Kernel Panic. Was the card working before? Have you changed anything to your setup (BIOS updated, BIOS changes, HW installation)? For what exactly do you use the card on your server? Do you have a monitor connected to the server? (Would it be possible for you to put the card in another computer to stress test it? <- this is only a thing I would recommend as last step after we troubleshooted everything else) Remove the 'nvidia-driver.plg' file that is located on your USB Boot device in .../config if you got any issue if it crashes instantly on boot, this basically prevents the plugin from installing on boot. Please double check if you have above 4G Decoding turned on in your BIOS. I would recommend doing this procedure: Stop the Array Disable Autostart from the Array Install the Nvidia Driver again See if it crashes -> if not reboot (without starting the Array) After reboot see if it crashed -> if not try to start the Array and see if it crashes again

Please post the full output, what does it say in the next line on your Docker page? Does the command succeed or does it fail?

The variable THUNDERBIRD_LANG is wrong, it should be en-US instead of en_US. This is actually my fault, I've changed it in the readme but forgot to change it in the Docker template. I've already pushed a update where it should be fixed but because you already have the language already wrong in your variables simply change it to en-US or whatever you like. I think you are French from what I see in your screenshot, maybe change it to "fr" (without the double quotes) in your case, you can get a full list here: Click Hope that helps!

Source: Click I would always recommend to use bridge not Host (Host only if needed for something like eg: Emby, Jellyfin, Plex to enable certain functionality).

Oh wait, you copy that over with Krusader? Please double check that the UID and GID from the file are 99 & 100 and the permissions of the file are set to 777 Seems like a permission problem.

My gameserver containers started as a small project and has gotten a little bigger over time. 😅 What mod engine are you using Valheim Plus or BepInEx

Probier doch mal das du den Portainer Autostart deaktivierst danach startest du Unraid neu und dann siehst du mal nach welchr Netzwerke das unter den Docker einstelkungen angelegt sind und ob denn der Container startet? Kann aber sein das du einmal auf bridge und dann wieder zurück auf br0 stellen musst.

Ich sehe hier eher das Problem das er zwei verschiedene Management Interfaces benutzt. Portainer mag durchaus seine Vorteile haben aber wie schon oben geschrieben, das wird sich vermutlich stören.

Hast du schon mal daran gedacht das Portainer dran schuld sein kann? das erstellt doch auch standardmäßig netzwerke und entfernt ihm nicht bekannte. EDIT: Hast du denn eigentlich auch Portainer-Agent installiert? Wie sieht eigentlich deine Docker Settings aus von dein Einestellungen?

Yes. Many people reporting issues with ZFS and Docker on 6.10.0 My main concern is why so many people having issues but I don't have... I run everything form ZFS (Docker, libvirt,...). Maybe it's because I've created a partition before or because I use the full path to the partition /dev/sdx1 who knows, would be really interesting, have to do some tests when I got more time on my test system. I've seen also some Github Issues that Docker fails in different scenarios while having everything on ZFS.

What game are we talking about?

Simply drop in a sv6 file in .../saves/ and change this value:

Why not, if it works it‘s good if it doesn‘t you can alwys go back to stable or stay on RC. In either way nothing is lost… and this should be done in a few minutes. 😉

I‘m not too sure what you mean. You are creating a server to server backup I think? What permissions can‘t be changed and where? On the source or on the destination? Why do you even try to change the permissions? What have you set or better speaking what boxes did you change in the task in luckyBackup? What filesystem are you using? This is a really weird issue that you are having, I backup my whole server to another Unraid server over SFTP and it‘s working just fine.

Do this (this will override the config file): in the template to change the ports (this will also change the second port to 7779) and you also have to change the query port from 27015 to 27016 (and so on) and then create the port mappings and of course delete the old ones. The same goes for this container:

Do you want to change the ports from AKR nor or Satisfactory? Why do you use Host for Satisfactory? Please tell me first what you want to do exactly and which container should have which port, please read the description again from the container, a simple change from the port won't work. You have to change the port first in the configuration file (make sure you stop the container first), then delete the old port in the container and create a new entry with the Container and Host port the same, then start the container again.

You can also run luckyBackup as root so that it is able to read these folder and copy the contents.