TexasUnraid

Thanks, I looked at both the dockerhub and github pages linked from unraid and could not find that FAQ.

How do I enable wireguard? My speeds with OVPN have been really slow every since around the time the nextgen servers came online. The documentation says But I do not have a VPN_CLIENT variable in the options? It also does not tell me what I need to put into the variable if I made it manually? Nor is there a place to put the server that I can see? Is the wireguard version a different version then the normal container?

If it got a bad sector on a new drive during a pre-clear, that is an instant return for me.

No worries, sounds good!

I just updated the parity check plugin and restarted the server and now I am seeing this message in the logs every 15 minutes: Nov 14 14:13:01 NAS crond[1955]: failed parsing crontab for user root: /6 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null Nov 14 14:27:11 NAS crond[1955]: failed parsing crontab for user root: /6 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null

Yes, all my drives, array, pools and UD drives are encrypted BTRFS (except my appdata drive with is encrypted xfs). BTRFS is also the only reason I knew this drive was failing, the drive itself did not start reporting errors until well after BTRFS detected them. It still just says 8 pending sectors.

Yeah, as I am sure you saw one of my other drives is failing so having to play a game of musical hard drives to move the data around. There was a lot going on lol. I do have similar issues maybe 30% of the time with other drives that I know are formatted and work correctly, with basically the same errors. I connect them every week for backups and sometimes they will just refund to mount until I reboot. Particularly if I unmount and remount them for some reason on the same day.

I went ahead and restarted it, I also re-formatted the drive before mounting it just in case that caused an issue, there was a LOT going on with the server when I formatted it the first time and sure enough it worked this time around.

Sent. It seems that the drive is not being added to the /dev/mapper for some reason as if I manually look in there it is not there. No idea why not.

I am still having issues where I can only mount a drive in UD once, if I unmount it and try to remount it, it fails. This is the errors in the log from today: Nov 14 13:07:13 NAS unassigned.devices: Adding disk '/dev/mapper/Games-750gb'... Nov 14 13:07:14 NAS emhttpd: shcmd (438): /usr/sbin/cryptsetup luksOpen /dev/sdt1 Games-750gb Nov 14 13:07:16 NAS unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/Games-750gb' '/mnt/disks/Games-750gb' Nov 14 13:07:16 NAS kernel: /dev/mapper/Games-750gb: Can't open blockdev Nov 14 13:07:16 NAS unassigned.devices: Mount of '/dev/mapper/Games-750gb' failed. Error message: mount: /mnt/disks/Games-750gb: special device /dev/mapper/Games-750gb does not exist. Nov 14 13:07:16 NAS unassigned.devices: Partition 'Games-750gb' could not be mounted. Nov 14 13:07:16 NAS unassigned.devices: Issue spin down timer for device '/dev/sdt'. I mounted this drive, moved some stuff off it and then formatted it. When I try to remount it I get the above errors. If I restart I am sure it will work, it normally does, just really inconvenient.

So this is how it is supposed to be now? And no way to change the layout? That is silly. Anyone know what version this changed in? I had not updated in some time so not sure when the change happened. I guess I will just revert to the older version that has the other graph layout, this new setup is useless by comparison.

I just updated netdata and now my graphs are messed up. The values for each datapoint are now on the left side under the graph instead of on the right side beside the graph. Making it virtually impossible to see the actual values of the graphs at a glance. This is what I have now: This is what it used to be and should be: How can I change it back?

I finally had a little time to try out this script, had the same issues with it not being able to handle shares with spaces in the name. Oh well, I will just stick to the setup I am using now and see if someday a plugin is made. I do wish I could get the previous versions working in windows though.

lol, it has been this way for the last week at least, possibly longer. I figured it was just a temporary issue at first as well.

I tried a half dozen this morning but at best I was seeing ~10MB/s when I used to see 25-35MB/s

Yep, switched to the new network and have tried going back to the old network as well but all servers I have tried seem to be much slower then before.

Anyone else noticed significantly slower speeds with pia the last few weeks? Seeing speeds about 1/3 what they used to be across a few different dockers using PIA/OVPN

I don't use mover, My downloads either download directly to the cache and I manually do what I want with them or Sonarr/radarr etc handle the moving all automatically. For my use case mover just would not help me much and would cause a lot of excess writes to the cache (for file transfers, not downloads). It is perfectly fine and I very well might find a use for it down the road but because I have reconstruct write enabled and my drives stay spinning 24/7 at the moment, they are already enough to max out a gigabit connection without the need for the cache. Generally any of my 10GB P2P transfers are talking directly to a cache only share. I am also a believer in minimizing drive usage whenever possible, be it SSD or spinning rust. I have hand many drives last over 10 years and keep on ticking with this strategy, so might as well stick with it.

Well, I should be clear, I don't use mover, so that was not the issue for me and it did it even on my old server with windows. So it is not an unraid issue I am pretty sure in my case. It was only like 3 times to me, once was due to my download drive filling up, the second could of also been caused by the drive filling up but so much data was being shuffled around I could not know for sure. Another time 2 torrents were downloading to the same folder for some reason and caused some corruption. I think there might of been 1 more time when the server was just generally having issues that day but can't remember. In all of these cases there were outside issues that caused the corruption though.

If it is a cache enabled share, then that means mover will move files off the SSD to the disk you tell it to at night. It is conceivable that if this move happened during the download this could cause corruption of some kind. Mover is not really designed for that use case far as I know, more designed for files copied during the day and then moved at night type of thing but not an expert. I have had random corruption issues like you in the past where several torrents were said to be complete but after a recheck they were actually not complete. In every case there was other funky stuff going on at the same time that was either caused by a hardware hiccup or just general strangeness. In my case a fresh reboot and cleaning up all the torrents I could led to everything working fine. I would setup a BTRFS error watching script though, just in case. I got this from Jonnie IIRC #!/bin/bash #description=This script will check the cache pool for any errors and send a notification if any are found. You must clear any errors after fixing the issue using the command: btrfs dev stats -z /mnt/cache #backgroundOnly= #arrayStarted=true #noParity= #argumentDescription= #argumentDefault= echo echo Starting check of cache if mountpoint -q /mnt/cache; then btrfs dev stats -c /mnt/cache if [[ $? -ne 0 ]]; then /usr/local/emhttp/webGui/scripts/notify -i warning -s "ERRORS found on cache pool: /mnt/cache"; fi fi

I assume that you are downloading to the cache drive? What format is it? BTRFS? Might be a good idea to run a scrub of it if so. A corrupted file is generally going to be a drive issue of some sort. Also I found out the hard way that unraid does not monitor btrfs cache pools for errors like it does the main array. You have to do this manually. I use a script run every hour now to check for any errors.

Great, at least you narrowed down the issue! Is it possible to use the API to change the trackers and have them stick after the port change? A nice feature to have in general would be the ability to add a list of trackers that would be updated automatically anyways. This feature is available in several other torrent programs but not qbittorrent for some reason.

Interesting, very well could be a bug in qbittorrent, just a rather annoying bug. Adding extra trackers makes finding seeds for old and low traffic torrents MUCH easier. Been doing some research on this and it seems the API does support adding trackers to new torrents: add_trackers_enabled bool Enable automatic adding of trackers to new torrents add_trackers string List of trackers to add to new torrent How would I go about adding this? Is there a way to add a script on boot of the docker? (remember linux noob here) Or maybe you could add it to the script and have a variable in the docker setup settings to add the link to get the list of trackers from or remove it to disable the option? It would be nice for it to automatically update the list on boot as well, it does change over time. This is the place I get the list of trackers from: https://github.com/ngosang/trackerslist

Web GUI, it could be a bug as this was several versions ago (4.0/4.1 IIRC) but I know it worked on my old setup.

Possible but it didn't do this when I was using qbittorrent on bare metal.