ich777

I've always done it this way because otherwise you would overwrite the snapshots. You can always go into the .luckybackup directory to recover files in the according folder since there should be your snapshots. I would recommend that you create an issue on Sourceforge itself since the developer is a really helpful and smart guy, maybe he can help out and can fix this issue for you.

How long is the password? make sure that is at least 6 characters longe, maybe also avoid special characters.

That's my best guess, it can be also the case that something is missconfigured, I would recommend that you join @Spectral Force's Discord, maybe he can help. https://discord.gg/VwwYA5h

Today I released in collaboration with @steini84 a update from the ZFS plugin (v2.0.0) to modernize the plugin and switch from unRAID version detection to Kernel version detection and a general overhaul from the plugin. When you update the plugin from v1.2.2 to v2.0.0 the plugin will delete the "old" package for ZFS and pull down the new ZFS package (about 45MB). Please wait until the download is finished and the "DONE" button is displayed, please don't click the red "X" button! After it finishes you can use your Server and ZFS as usual and you don't need to take any further steps like rebooting or anything else. The new version from the plugin also includes the Plugin Update Helper which will download packages for plugins before you reboot when you are upgrading your unRAID version and will notify you when it's safe to reboot: The new version from the plugin now will also check on each reboot if there is a newer version for ZFS available, download it and install it (the update check is by default activated). If you want to disable this feature simply run this command from a unRAID terminal: sed -i '/check_for_updates=/c\check_for_updates=false' "/boot/config/plugins/unRAID6-ZFS/settings.cfg" If you have disabled this feature already and you want to enable it run this command from a unRAID terminal: sed -i '/check_for_updates=/c\check_for_updates=true' "/boot/config/plugins/unRAID6-ZFS/settings.cfg" Please note that this feature needs an active internet connection on boot. If you run for example AdGuard/PiHole/pfSense/... on unRAID it is very most likely to happen that you have no active internet connection on boot so that the update check will fail and plugin will fall back to install the current available local package from ZFS. It is now also possible to install unstable packages from ZFS if unstable packages are available (this is turned off by default). If you want to enable this feature simply run this command from a unRAID terminal: sed -i '/unstable_packages=/c\unstable_packages=true' "/boot/config/plugins/unRAID6-ZFS/settings.cfg" If you have enabled this feature already and you want to disable it run this command from a unRAID terminal: sed -i '/unstable_packages=/c\unstable_packages=false' "/boot/config/plugins/unRAID6-ZFS/settings.cfg" Please note that this feature also will need a active internet connection on boot like the update check (if there is no unstable package found, the plugin will automatically return this setting to false so that it is disabled to pull unstable packages - unstable packages are generally not recommended). Please also keep in mind that for every new unRAID version ZFS has to be compiled. I would recommend to wait at least two hours after a new version from unRAID is released before upgrading unRAID (Tools -> Update OS -> Update) because of the involved compiling/upload process. Currently the process is fully automated for all plugins who need packages for each individual Kernel version. The Plugin Update Helper will also inform you if a download failed when you upgrade to a newer unRAID version, this is most likely to happen when the compilation isn't finished yet or some error occurred at the compilation. If you get a error from the Plugin Update Helper I would recommend to create a post here and don't reboot yet.

May I ask what python3 application is using your card? Do you use it in other containers too? If yes, does it work in the other containers? So this is happening in the Linuxserver container, maybe try the official one or mine and see if the issue persists, what you can also try is to buy a Emby Premiere membership for one month and test if it works in Emby. I can also confirm that HW transcoding is working in Emby too.

Yes, but Satisfactory uses another Engine as far as I know than 7DtD and the save games may be not compatible. If you start a new server without a save game it is working or am I wrong? Are you sure that the server and the save game are on the same game version? I only can think of a issue with the file itself or that it is like mentioned above not compatible with Linux when you've transferred it over to Linux.

I think this has to be an issue with the card itself, but I could be wrong about that. Then your CPU is hit pretty hard I think in terms of utilization or am I wrong? When transcoding can you try to open up a terminal from unRAID itself and type in: watch nvidia-smi What exact encoders did you set in the Jellyfin settings? From what I see this a SDR movie and not HDR, there should be no issue transcoding these kind of files.

It is maybe possible that the Linuxserver container have different paths than mine, I can only tell for sure that the official Jellyfin is compatible with my container if you change the repo.

I've now tried the following: Set up a source folder with 3 files in it called "1", "2", "3" and also set up a empty destination folder Set up a task in luckyBackup and set the "Snapshots to keep" to 5 (just in case) Run the first sync, all 3 files are synced properly Delete file "2" from the source Ran another sync, file "2" is now also deleted from the destination Restarted the container (just in case) Opened "Manage Backup" and selected the first sync, clicked on "Restore" and restored it to a third directory All three files "1", "2" and "3" are now in the 3rd directory

This is a bug in a linbrary on Debian and can be ignored. These are all warnings and will not harm your connection in any way. But most of these issues are caused feom your vpn.ovpn file, I would go through your vpn.ovpn file and see if you can resolve those issues.

Ah, you've put a save file into it? How did you do that and what did you change in the serverconfig.xml? Keep in mind that some game servers are not compatible between Windows and Linux.

That is not necessary. Please look at the log again, first it fails and then it loads just fine because it searches in multiple places for it.

What have you set in terms of Use Cache in the Share settings for your appdata folder? Please make sure that "Only" or "Prefer" is selected. Can you try to start over please. Delete the container, delte the 7dtd folder in your appdata directory and pull a fresh copy from the CA App. On what Hardware/CPU do you run unRAID? EDIT: Just tested it and the container boots up fine and I also can see it in the Steam Server Browser.

Don't know if CoreFreq will help you see this... What do you mean with this?

Have you installed a cache drive in your server? Does it actually loop or did you restart the server? Looks like you have nothing changed in the template or am I wrong? Are you on unRAID 6.9.2 or a lower version?

I would think that CoreFreq is more accurate but also keep in mind that the WebGUI is maybe a little bit behind because it needs to reflesh and so on...

Ohne zu wissen welche Hardware du hast kann dir hier keiner weiterhelfen. Bitte poste deine Diagnostics.

This should not be a problem (can't parse every version correctly since some modules have very weird naming schemes for the version if they are existent at all). Can you open up a terminal from unRAID and do: ls /dev/dvb If you get a output with in your case "adapter0" and "adapter1" your card should work fine.

This is a V5.5 card, this plugin supports only V6.0+ cards. You can try however the LibreELEC package but I'm not too sure if that works because V5.5 cards are pretty old now...

But does it work for a certain period of time? What do you mean with the loop? Can you post the log? How do you try to connect to the server? Can you post a screenshot from your entire Docker template for 7DtD?

Please read the last paragraph from the linked post:

I hope this answers your question: Click It is not strictly an error, it is more a "warning" or "alert".

I think it's because the sandbox is disable because, well you don't need the sandbox in a Docker container because Docker is a sandbox and it is also using the test type flag, I think there is nothing I can do about this... Have to investigate further but as said above I don't think I can do anything in this case...

Yes, then this is the cause of issue... since the latest driver is about 230MB in terms of size. You can however delete the "previous" folder on your USB boot device, this directory holds the previous unRAID version that you've had installed.

May I ask what do you mean exactly?