ich777

age (pronounced: [aɡe̞]) Is a simple, modern and secure file encryption tool, format. It features small explicit keys, no config options, and UNIX-style composability. Based on the excellent work form FiloSottile: https://github.com/FiloSottile/age This tool is command line only and meant for backup scripts. https://raw.githubusercontent.com/ich777/unraid-age/master/age.plg Basics: After installing the plugin it will create a key file on your USB boot device that is named 'key.age' and located in /boot/config/ ATTENTION: I STRONGLY RECOMMEND TO BACKUP THIS FILE TO SOME OTHER LOCATION (PREFERABLY ON A SPARE USB KEY) OR PRINT IT OUT AND STORE IT SOMEWHERE SAFE! IF YOU LOOSE THIS KEY YOU CAN'T DECRYPT ANY OF THE DATA THAT WAS ENCRYPTED WITH THIS KEY FILE!!! Note: even if you uninstall the plugin the key.age file will not be deleted from the USB Boot device for security reasons (accidental deinstallation of the plugin) Usage: age-keygen Is called automatically on plugin installation and will create the 'key.age' key file mentioned above that will look something like this: # created: 2021-06-10T12:00:00+02:00 # public key: age1me4cr6ll89gy0r3r5hftu0sxjr8nlyd37nylufjq6adlljzdjpuqul5et0 AGE-SECRET-KEY-1AFWSPAZ7ZLM6UR9ZGXNT4U276EVHHEPNX0YRWW8EH05P487N89VQUA0HJA (I strongly recommend as stated above to backup this key file to a spare USB Key or print it out and store it somewhere safe, I would also recommend to remove the last line from the file on your USB Boot device after you made a backup of the file since this is the actual key that you need to decrypt the files - again, IF YOU LOOSE THIS KEY YOU WON'T BE ABLE TO DECRYPT THE FILES THAT WHERE ENCRYPTED WITH THIS KEY FILE) age To encrypt a single file you need your public key from the 'key.age' file, as a first example we take a picture with the filename 'test.jpg' that is located in /mnt/user/Pictures/ age -r age1me4cr6ll89gy0r3r5hftu0sxjr8nlyd37nylufjq6adlljzdjpuqul5et0 /mnt/user/Pictures/test.jpg > /mnt/user/Pictures/test.jpg.age This will keep the original file intact and create a file with the extension .age that is fully encrypted (of course you can also point to another output path for example if you have a disk through UnassignedDevices mounted just replace '> /mnt/user/Pictures/test.jpg.age' with '> /disks/YOURDISKNAME/Backup/test.jpg.age' for example) You can also store the public key in a variable with something like this: AGE_KEY="$(cat /boot/config/key.age | grep "public key:" | awk '{print $4}')" and then modify the above command to use the variable: age -r ${AGE_KEY} /mnt/user/Pictures/test.jpg > /mnt/user/Pictures/test.jpg.age If you want to create a encrypted tar archive from a directory (in this case from the USB boot device) do it as follows: cd /boot tar -cvzf - --exclude='./bz*' --exclude='*.tgz' --exclude='*.txz' --exclude='./previous' --exclude='./config/key.age' . | age -r ${AGE_KEY} > /mnt/disks/YOURDISKNAME/Backup/$(date '+%Y-%m-%d_%H-%M')_USB_BACKUP.tgz.age Explanation: cd /boot (will change the directory to the boot device) tar -cvzf - (will create a tar archive to the pipe) --exclude='./bz*' (will exclude all bz files, the main OS, since we only need the config files) --exclude='*.tgz' --exclude='*.txz' (will exclude all plugin archives, since we only need the plg files) --exclude='./previous' (will exclude the backup from the any previous installed Unraid version) --exclude='./config/key.age' (will exclude the 'key.age' file) --exclude='*.zip' (THIS IS OPTIONAL and not in the command above but recommended if you have saved diagnostics or logs on your USB Boot device) . (tells tar that this is the directory that it should pack up as a tar archive) | (hand over the output from the pipe to age to encrypt the data that is created by tar) age -r ${AGE_KEY} (use age and the public key in the AGE_KEY variable to encrypt the date from tar) > /mnt/disks/YOURDISKNAME/Backup/$(date '+%Y-%m-%d_%H-%M')_USB_BACKUP.tgz.age (output the file to a UnassignedDevices mount that is located in /mnt/disks/YOURDISKNAME/Backup/ and named something like this: '2021-06-10_12-00_USB_BACKUP.tgz.age') DECRYPT FILES: age --decrypt -i /boot/config/key.age /mnt/disks/YOURDISKNAME/2021-06-10_12-00_USB_BACKUP.tgz.age > /mnt/disks/YOURDISKNAME/2021-06-10_12-00_USB_BACKUP.tgz Explanation: age --decrypt (use age to decrypt a file) -i /boot/config/key.age (use the 'key.age' file that is located on your USB Boot device to decrypt the files ATTENTION: If you deleted the last line in the 'key.age' file like mentioned above you have to first restore your backup file with the last line included to your USB Boot device otherwise the decryption will fail) /mnt/disks/YOURDISKNAME/2021-06-10_12-00_USB_BACKUP.tgz.age (the filename to decrypt) > /mnt/disks/YOURDISKNAME/2021-06-10_12-00_USB_BACKUP.tgz (the filename of the decrypted file that will be created) There are many ways you can utilize this tool and these are only a few examples how to use age.

Probier mal das zu deiner syslinux.cfg hinzuzufügen: "hpet=enable" (ohne Anführungszeichen) und reboote Sieht so aus als würde irgendwas mit deiner clocksource nicht stimmen... Eventuell behebt es das Problem in deinem fall wenn du die clocksource gleich auf hpet stellst. EDIT: Btw das bedeuted übrigens TSC: Klick

After I updated the container today I get an error that the execution of /bin/tar has been denied and the container isn't able to start, the message repeats over and over again. I attached the log: tvheadend.log Has something changed that I've been missing? Also may I ask what is the difference between the version-9476680f vs. 9476680f-ls100? I've reverted now back to version: 63784405-ls97 which is running fine.

Depending on the container that you use: you should make post in the appropriate support thread for the container @binhex: @clowrym:

For the Nvidia driver start here (you have to be on 6.9.0+ to see the plugin in the CA App): I think the HBA's aren't supported anymore if I'm not wrong, please read this post here:

@audioclass, @tianyun123lo & @Suriniya Valve fixed SteamCMD and installations from game server containers work now flawlessly again when installing games from scratch without the disk write error. To update SteamCMD restart one container and it will update SteamCMD. Please look here: Click You can append it to the GAME_PARAMS in the Docker template or you can edit the server configuration itself that is located at (the screenshot is from that site that I've linked - in your case you have to choose the Linux paths):

Sollten die Karten nicht schon alle mit UEFI laufen mittlerweile da sich Nvidia dazu entschlossen hat keinen Code43 mehr zu produzieren in VM's sobald der Treiber installiert ist? Muss aber ehrlich gestehen VM's sind nicht wirklich mein Spezialgebiet... Mich würde aber brennend Interessieren ob die User hier die einen 11th Gen haben denn wirklich mit UEFI booten.

Nein, das heißt einfach das du gezwungen wirst im UEFI mode zu booten ansonst funktioniert die iGPU nicht mehr und du brauchst eine dGPU wenn du im Legacy bootest. Aber ob das stimmt, bin ich mir nicht sicher, wäre interessant ob User die einen 11th Gen haben was dazu sagen können (soweit ich weiß ist bei den Asrock Boards sogar schon eine Warnung hinterlegt im BIOS wenn du Legacy aktivierst das die iGPU unter Umständen nicht mehr funktioniert). EDIT: Hab mir den Artikel erst jetzt durchgelesen, da ist sogar ein Screenshot von der Asrock Warnung im BIOS.

Probier es mal so das du folgendes in die Post Commands (wenn du die Erweiterte Ansicht anschaltest) rein machst: -c "knxd -e 1.1.99 -E 2.0.1:8 -i --send-delay=70 -b ipt:10.9.8.7" Sprich (Bild ist leider abgeschnitten aber ich glaub du weißt was ich meine ) :

This is just a Warning and can be ignored the message "Setting breakpad minidump AppID = 346110" is actually the message that the server is started and waiting for connections. Yes, I have appended this text to the GAME_ID description in the template (if you pull a new one from the CA App):

Then I can't help and you won't see it in luckyBackup because this is basically the default command that is run by luckyBackup with a Cron schedule. But at least you can run the backups on a schedule for now this way...

Try this command: docker exec -i --user luckybackup luckyBackup env DISPLAY=:0 /usr/bin/luckybackup --silent --skip-critical /luckybackup/.luckyBackup/profiles/default.profile > luckybackup/.luckyBackup/logs/default-LastCronLog.log 2>&1

Does this happen when executing from the terminal itself or from the User Scripts, if from the User Scripts change '-ti' to '-i' (always forget about that... ).

Please read the post from above, slightly modified. No, no log output since I'm redirecting this to /dev/null... Remove the '> /dev/null' part and you will get a output.

Yes, you should create a new script in the User Scripts plugin. For testing purposes you can run just the full command from the Unraid terminal (not the Container terminal!). You will see no output but the Backup should run just fine, this is because it is running silently, but this is basically the same as when you create a Cron entry within luckyBackup. Make sure that the task was run once.

Sure thing create a new Cron entry on the host with the following script contents and the preferred execution schedule: #!/bin/bash docker exec -i --user luckybackup luckyBackup env DISPLAY=:0 /usr/bin/luckybackup --silent --skip-critical /luckybackup/.luckyBackup/profiles/default.profile A short explanation: docker exec -i --user luckybackup (sends a command to the container as user "luckybackup") luckyBackup (this is the actual name of the container, change it if your container is named differently) env DISPLAY=:0 /usr/bin/luckybackup --silent --skip-critical /luckybackup/.luckyBackup/profiles/default.profile (is the actual command that is passed to the container that it should execute - ATTENTION change the underlined text 'default' at the end to eg: 'myjob' (without quotes) if your job that you created in luckyBackup is named 'myjob') (Please make sure you've run the task once from the GUI otherwise the Cron job will not work) If you have any questions feel free to ask.

Warum?

First of all this is the wrong thread, please post in the Nvidia Driver thread. Anyways, you are trying to convert a HEVC movie but the GT730 doesn't support HEVC (h.265). Have you already looked at the CPU utilization? Please try to convert a h.264 file instead with that card and it should display that it is transcoding. Also keep in mind that you can install the GPU Statistics plugin from @b3rs3rk to see the utilization on the Unraid Dashboard. One thing do you use 'watch nvidia-smi' or simply 'nvidia-smi'?

I don't own FarmingSimulator19 and from what I know you need a extra License to get this to work and also it runs really unstable (at least what I know from FarmingSimulator18 when I tried it back then) with WINE.

That depends on the type of OS do you run on your home computer, for Linux you can use something like 'badblocks' for Windows you can use 'chkdsk', for OSX you can use Disk Utility I think... I'm really wondering why it doesn't work on your system...

I still wonder why it's not installing properly at boot on your system because that's what the plugin does basically. Can you run memtest and also can you test if your usb boot device is in good condition?

Passt perfekt, lies dir bitte diesen Thread durch (auf den kleinen Pfeil nach rechts oben klicken): Du musst für deine Hardware den gleichen Eintrag wie im geposteten Beitrag in deiner syslinux.cfg machen und dann Unraid neustarten. Genau das passiert wenn du diesen Eintrag und 11th Gen nicht drin hast da das Kernel Modul die CPU eigentlich noch nicht unterstützt aber mit dem Eintrag sagst du prüfe mal das Gerät mit der HW ID und schau ob es funktioniert. Ohne dem Eintrag schlägt der Befehl 'modprobe i915' einfach fehl und du hast dann natürlich auch kein Verzeichnis '/dev/dri'.

Please read this post: Valve broke SteamCMD and there is a workaround in that post.

Have to say sorry, wasn't aware that Minecraft 1.17 needs Java16. Also change the template that Java16 is selected by default for no installations, should take a few hours to update in the CA App. Thank you for the report, much appreciated!

Sorry seen now that you actually need JRE16, pushed an update of the container, do the following: Stop the container Delete the runtime folder once again Force an update from the container Go in the template and click on "Show more..." Change the Entry "Runtime Name" to: 'jre16' (without quotes) Click on Apply