dedi

So I run into the same issue with the current version of OSMC. I solved it with AI, by adding the following lines to /etc/nfs.conf on my Unraid host (file didn't exist before for me): [nfsd] vers4.0=y vers4.1=y vers4.2=yQuick console command to add it and restart nfs: cat << 'EOF' >> /etc/nfs.conf [nfsd] vers4.0=y vers4.1=y vers4.2=y EOF /etc/rc.d/rc.nfsd restartIt worked after rebooting my OSMC. To make it permanent, place it in the go file (did not test the reboot right now): cat << 'EOF' >> /boot/config/go cat << 'INNER_EOF' >> /etc/nfs.conf [nfsd] vers4.0=y vers4.1=y vers4.2=y INNER_EOF /etc/rc.d/rc.nfsd restart EOFI hope this is something to setup in the GUI in the future.

I am a noob in this topic, but I found out that not every docker container has curl, like some alpine based containers. I replaced the extra parm command to use wget for these containers: --health-cmd="wget --no-verbose --tries=1 --spider http://1.1.1.1 || exit 1" --health-interval=100s --health-retries=3 --health-timeout=30s --health-start-period=60s I also replaced google with 1.1.1.1 so it's not affected by a dns problem

The nzbgetvpn docker from jshridha is now 17 months old. Any chance that it gets updated / switched to a newer docker image?

A bit surprising that did not come up yet, but I had permission issues of files written by ABS (644 owned by root) and access them via SMB. --user=99:100 as extra parameters did the trick and now it writes as nobody:users owner I had to fix apppdata permissions once: chown nobody:users appdata/audiobookshelf -R

Newly created cover and metadata files have read only permissions for root/root. -rw-r--r-- 1 root root cover.jpg -rw-r--r-- 1 root root metadata.json Can that be fixed somehow?

Thanks, that was as issue for me too, and this fixed it. (appdata\plex\Library\Application Support\Plex Media Server\Codecs)

It is really hard to find even after I googled to this thread and it feels misplaced

Hi! A bit late to the topic but here is what I experienced: I have a WDC WD60EFRX-68MYMN1 hard drive that has been causing problems for 5 years (when I started using unraid). Although I've tried troubleshooting it a few times, I haven't found any solutions. Initially, I thought the drive might be failing or there was something wrong with my setup, so I started using it as an additional parity drive. However, it always starts to count errors after running for a while, although all parity checks and extended SMART tests have been successful over the years. I recently upgraded my unraid server and am now using a SAS card, but the drive continues to exhibit the same behavior. Additionally, it sometimes gets disabled after running for 1-3 weeks. Once, it happened exactly when I clicked on the spin-up/spin-down button, so I'm not sure if this is related to the spinning state. I've tried switching cables and controllers, but it hasn't made a difference. WDC WD60EFRX-68MYMN1 log.txt

I had the same thought. Also it's not really true that all files within that location will be deleted. I have existing backups as well as custom folders and files there, they all stay fine. Only thing ever getting overwritten there are the contents of subfolders caBackupUSBStick and caBackupVM/libvirt.img when running a backup.

The NICs for eth0 and eth1 are switching around on boots, making it sometimes unreachable from the network. I'm running Unraid on proxmox, when running correctly eth0 is on proxmox br0, eth1 is my 10G card with PCIe passtrough. I do not have any option in the network config to specifically assign the NICs. I also don't have a network-rules.cfg, if I create one it gets removed on reboot. diagnostics-20221205-1809.zip

Can confirm, backing up subfolders works great now. Thank you!

Thanks for all your effort! Just as a thought: adding single folder names in addition to full paths would be a nice solution too that would give a better overview (and maybe is not a lot more work to implement). A bigger/scaling input field is an other idea.

Yes, that is the case. I use it a lot since there is a lot of diskspace hungry stuff that does not need to get backed up. (The UI isn't great to add these, that's why I edit it in notepad.)

That is not working here, still creates full backups. (All data are on cache only). I tried to switch "Appdata Share (Source):" to /mnt/cache/appdata too but that also didn't help.

Hi! Switched to the new fork, re-entered all config options, enabled "Create separate archives (one per folder)." It's now ignoring my list of excluded subfolders. Whole apps are still getting excluded, but I have a lot of cache/thumbnails/metadata folders that grow the backups way too big. (This was working before.)

Update came out

I switched today from another nzbget vpn docker. Whatever I configure for LAN_NETWORK makes exactly that network not working. Only when VPN is activated. I do have 2 IPs for my unraid. if I configure like that: 192.168.200.0/24,192.168.0.0/24, then I can't connect at all. If I only use one, the other one is working. If I enter something totally unrelated, then it works on both IPs. Also sonarr/radarr docker can't connect. Tried both wireguard and openvpn. If I disable VPN fully it works. And sonarr/radar are able to connect then. I also started a new docker from scratch with only minimal changes and it still happens. This does also happen with dyonr/jackettvpn. Other docker with vpn and similar network setting do work. Any clue what is wrong? log: https://pastebin.com/HTujsyhb

Same here. Will wait for an update Edit: Thanks, all working now

I was running the preview of v3 for some weeks without problems. Recently the preview tag got deprecated, so I removed it. Suddenly I was back to v2 and all settings gone. I changed the tag specifically to "latest" and with a force update I had v3 installed with all settings restored. Weird but it worked.

Didn't found any solution, gave up

Ohhh i totally forget that I added the post arguments and must have overlooked that.

Suddenly can't make changes to the docker configuration via UI anymore: Was running fine before. Can still start/stop. Does it have something to do with NC 19 beeing released?

I have a CSR Bluetooth dongle (Cambridge Silicon Radio Bluetooth Dongle) that I want to pass trough to a Home Assistant VM, I can select it in the VM config but hassos does not find the device there, Is that because firmware for CSR BT dongles are missing?

Thank you, I used your example and it works good. One problem I have with my script is, when the ssh connection cant get established I dont get a fail warning, it looks like everything went well. How could I fix that?

I thought I share my rsync config. I still feel like Unraid as a Storage Server should provide a build in method to backup or sync its data to an other location, but configuring rsync gives you a lot of power, and once set up, it's just great. I based my config and setup on the tutorial found here: https://lime-technology.com/forums/topic/52830-syncronize-servers-using-rsync-over-ssh-next-door-or-across-the-world/ And I made some adjustments, specially the option to watch the sync going on, and the notification that works with the build in unraid notification. So on "errors" you will get a E-Mail notification if your unraid is setup for that. The above tutorial covers the SSH setup and connect via key instead of login, and the basic rsync setup. You can continue after that guide. What you need is the NerdPack Plugin, and there install "screen". It is used to run rsync in it own screen, giving you the option to pull the progress up in a console at any time. The second one is optional but recommended, its the "User Scripts" plugin. It allows you to add own scripts and execute it via cron in your unraid GUI. I created 2 scripts for my rsync: The first one I called "rsync" and does the rsync job, and depending on its exit code, it gives the notification to the Unraid Notification Service. #!/bin/bash rsync -avu --bwlimit=4000 --numeric-ids --log-file=/mnt/user/Backup/rsync-logs/log.`date '+%Y_%m_%d__%H_%M_%S'`.log --progress --exclude 'C Sys' --timeout=600 -e "ssh -p 4222 -i /root/.ssh/DSStoDMS-key -T -o Compression=no -x " /mnt/user/Backup/Devices/ [email protected]:/volume2/Backup/Unraid_rsync if [ $? -eq 0 ] then /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup complete" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`" else /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup FAILED" -i "alert" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`" fi Of course, the rsync command would need some adjustments. If your Unraid server is setup to send you a E-Mail on errors, it will do that too if rsync fails! The second one is for calling that script in a "screen" session. #!/bin/bash export SCREENDIR=/root/.screen screen -dmS rsyncdms /boot/config/plugins/user.scripts/scripts/rsync/script You can pull it up as long as it is running with screen -r from a console. You can just use the build in one from the WebGUI. Attention, if you name the first script different than "rsync", you have to adjust this location. Now just set a schedule for the second script. Watch its progress with "rsync -r" I hope this can help somebody. Im not a rsync expert, so if anyone is around with more experience has some input, its very welcome. And I have a questions myself: I have large files to transfer, sometimes a lot of new data comes up at once. So if I have to transfer >400GB, it needs more than 24h, and the rsync backup script (which is scheduled to run daily) is started again. It starts with the files that is currently transfering in the first instance of rsync. It works, but it will transfer that big file twice. Should I check when running the script if rsync is already running? Or does running rsync with --partial do any good or bad here?