• Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About thrroow

  • Rank
  1. I can only get 2 of the 4 ports to pass through to this VM. I have tried with the ACS override on/off, and with multifunction on/off (2 groups of 2 or 4 individual devices). Any ideas? I had no special settings and all 4 devices individually assigned (no multi) to a VM in 6.8.3, but didn't work when I upgraded to 6.9.0-rc1 for some reason. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address
  2. I have upgraded to 6.9.0-rc1 and the new Nvidia drivers to keep hardware transcoding. For some reason a certain patch doesn't work, but I don't really need more than several streams at once, so no big deal. However, if I'm transcoding 3 streams, and someone goes to try and use a 4th one, it just constantly buffers / is just a black frame. Is this expected behavior? I would imagine Plex would realize that the card is at the transcode limit and fallback to CPU?
  3. Let me give a short series of events, because this is clearly something that I did. Current setup: 6 disks in array, 1 cache, 1 UD, Nvidia GPU for plex, 4 port NIC for pfSense VM Running out of room on my UD lately, so thought it was time to upgrade. Added a new one, changed the partition names (made the new drive named the same as the old one, after rsync), erased the old one. Everything still fine. Thought it was time to cleanup some other stuff, and change CPU pinnings, among other things. Why not? BTRFS disk corrupted itself around this time. Could have bee
  4. wow that careless of me. Thanks for the headsup, changed credentials.
  5. I've got a weird problem. After months of running fine and me not touching anything, rtorrent suddently stopped being able to be used by web interface. When I would click anything it would just say error. When I add a torrent it would fail. HOWEVER, sonarr/radarr/etc still could use it fine, so I never bothered fixing it. Now weeks later it won't boot at all. So I deleted the container, used a blank config folder - the only thing I kept is the wireguard folder. Both the old and new containers now just hang on "loading" and never even let me see the GUI. No response from sona
  6. It's started and stopped happening to me, at seemingly random intervals.
  7. I believe it is this: Not sure why it would start just now, though
  8. I actually used to have this problem, then it went away for months, now it's back. No significant hardware changes in that time.
  9. When I transfer files to/from the array or use something like bittorrent to download files to the array (or really the cache SSD), between 3 and 5 of my threads will peg out at 100% usage in the unRAID dashboard. Checking top and htop shows that nothing is using that much CPU, however if I look at iotop or Netdata, I am showing very high IOWAIT times. It's like something is bogging down file transfers and it's crashing the entire system. After this goes on for a few seconds, all docker containers become unresponsive, VMs, and even unRAID dashboard. Attached is a picture with all containers
  10. I was in the middle of uploading several screenshots when I saw that the container volume mapping was /data/ (as it had been), but the within qbittorrent the /data/ location had changed to /downloads/. After changing it back to /data and restarting it, it now works! When or how did those settings get changed within qbittorrent? I definitely didn't touch any of those settings.
  11. I misunderstood your question. Yes both those paths are the same in each docker, and I have all identical settings (even ports). I ran one, tried to download, stopped it, started the other, and tried the same download. And again, no paths or settings of any kind have changed in months. Another odd thing I noticed, is that sometimes public trackers work slowly (like RARBG ~400kbps). But trackers that should be faster (iptorrents, xspeeds, ubuntu, etc.) don't work at all. Also tested all of these on both docker containers and on a PC using the same VPN connection. In all cases
  12. No, both containers were changed to be exactly the same, including container mounted paths, settings, etc. Also, as others have mentioned, these setups used to work just fine. All of a sudden stopped working even though I haven't even opened up the webUI in months. I just noticed radarr/sonarr downloads were stacking up. Double checked with a manual Ubuntu torrent to make sure it wasn't a tracker or VPN issue. Is there a way to delete all container info etc. so that all of it will be re-downloaded? I can try that too.
  13. I didn't change the folders it was pointing to, however, the other qbitvpn docker I downloaded and tried were also pointed at the same folders with no problems. I also made sure to use the exact same ovpn credential file between the two instances. I get around 40 to 60MB/s on my VPN, so it's definitely not overhead or losses. The one thing I didn't try was to get rid of the torrent backup folder because I'd rather switch clients than stop seeding hundreds of torrents.
  14. Also having the same issues as everyone else with the very slow speeds that soonafter just reach 0kbps. I tried installing the other qbittorrentVPN and copied my appdata and torrents to it - same issues. I then deleted all the config/logs/etc - everything BUT the torrents I was downloading and restarted it. This worked and behaved normally. I tried to copy the same thing to binhex-qbittorrentvpn but it didn't help, still slow speeds with everything else being identical. I guess I'm switching dockers for the time being since they're basically identical, except one works
  15. In terms of featureset, this is my favorite torrent client so far. But after a few minutes of use, it becomes painfully slow. Setup with just a normal config using a VPN (PIA). Saving to download directory which is downloading to a cache drive first. Dual xeon CPU, and never high CPU usage detected. Any troubleshooting ideas?