ecx

Members
  • Posts

    7
  • Joined

  • Last visited

ecx's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The other day my unRaid Sandisk USB died, and I used the MyServers plugin to restore onto a Samsung USB instead. Everything basically returned to its working state - but VM GPU passthrough. The error logs imply that the GPU is being utilized - it's not(or at the very least it shouldn't be). The only other process I use the GPU for is Tdarr, and I keep it in a off-state majority of the time. I even disabled Docker, rebooted with Docker in an Off state, and still the GPU passthrough is being "used". For whatever reason the VMs think it's being utilized? I re-enable docker, and turn on Tdarr manually to see if it'll start encoding my library - and yep, the GPU is working inside the Docker container, and it's being done by NVenc, not cpu. I also tried making a new Win10 VM. Without the GPU passthrough first, and it worked fine. I installed Splashtop. Then I shutdown the VM and tried to do passthrough. But it had same problem as my pre-existing GPU-passthrough VM. Tried changing PCIe ACS override from Downstream to Both with no appreciable difference. For the curious, this is basically the log flood: Not really putting this in the bug section in MyServers plugin, because, for all I know I'm missing something very obvious. Any help would be appreciated.
  2. I had a pair of these Sandisk USBs (UltraFit's 3.1) die on me in the past year(not going to link them, so no one accidentally buys them). The last one died yesterday was my unRAID boot. They appear to be legitimate since Sandisk honoured the RMA process. But both didn't last 2 years (to be fair, the first one I put absurd amount of write cycles on it). But trying the Samsung Bar Plus now, and Sandisk USBs have moved to the avoid category for myself going forward.
  3. Huh... no I did not. Didn’t even know the firmware Reset was a thing. I’ll give it a shot. Thanks. I’m reluctant not running unraid on my UPS; my neighbourhood has a bad history of brown outs in the summer. But it is a good suggestion to eliminate my UPS as the culprit.
  4. Not sure what is at fault. Just seems to randomly shut off. Twice last week. No power outages. 6.9.2, but I've noticed this behaviour even during 6.8.x - leading me to speculate - maybe my server power supply or my UPS. My server UPS says: POWER UPS Load: 17.0 % - 76 Watts UPS status:Online LOWBATT Battery charge:100.0 Percent Runtime left:1.4 Minutes Nominal power:450 Watts It's an old UPS, but I did change the battery in it with a new one last year. Should I be targeting a specific size when shopping UPS? Nothing obvious in the logs.
  5. Latest build for both rtorrentvpn and delugevpn have the dns issue with synology docker (though, I think that's expected because of the dig issue?). Now experiencing new issue with older build - delugevpn:1.3.15_14_gb8e5ebe82-1-11 (which works with synology), but has this one issue: One of my trackers is refusing any connections to it. Rest of my trackers are fine. It's not an IP or account issue with the tracker. I've tried the torrents on a local machine, with and without VPN (deluge local, qBitTorrent). Also tried rtorrentvpn with Flood (0.9.7-1-07 build), and it works perfectly fine. So issue is isolated to delugevpn with this one tracker. Tracker status: trackerdomain.name: Error: Operation canceled Occasionally that says "timed out", before quickly switching to operation canceled again. the deluge.log file is pretty useless. Doesn't report anything odd about these connection issues. Likewise supervisor.log looks pretty normal to me. Is there another log file I can poke at inside the container that might explain this behaviour?
  6. I've been using this container for at least a year, without issue. Then my watchtower updated to the most recent build (2 days old) Current build (latest) is giving me DNS errors with PIA servers. I swapped DNS providers (Cloudflare, Google) to no avail. I recreated the container, same problem. I tried current build of arch-rtorrentvpn with the same errors. I changed PIA servers (swiss, montreal, etc). Tried toggling with port forwarding on and off. No difference. I created a new container with the arch-rtorrentvpn container with the previous build (0.9.7-1-07) and it worked*. Just did the same with arch-delugevpn back to 1.3.15_14_gb8e5ebe82-1-11 and it also works. The latest builds seem to be causing DNS errors with Synology DSM docker. I reloaded the old docker settings without issue on the manually specified build, so it doesn't seem to matter if it's from scratch or existing, the old builds work. New ones do not. ? 2018-08-07 22:12:57,733 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2018-08-07 22:12:57,741 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2018-08-07 22:12:58,006 DEBG 'start-script' stderr output: random.c:102: fatal error: RUNTIME_CHECK(ret >= 0) failed 2018-08-07 22:12:58,018 DEBG 'start-script' stdout output: [crit] swiss.privateinternetaccess.com cannot be resolved, possible DNS issues 2018-08-07 22:12:58,018 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140398907495416 for <Subprocess at 140398907496280 with name start-script in state RUNNING> (stdout)> 2018-08-07 22:12:58,019 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140398907495056 for <Subprocess at 140398907496280 with name start-script in state RUNNING> (stderr)> 2018-08-07 22:12:58,019 INFO exited: start-script (exit status 1; not expected) 2018-08-07 22:12:58,019 DEBG received SIGCLD indicating a child quit *rutorrent has always been a problem with Synology DSM docker. I think Flood worked fine, but I needed the added functionality of full rutorrent (such as ratio groups), or Deluge and it's plugins. Regular rutorrent worked fine at first, restarting it stopped working (that or I lost patience). I figured either way, the inherent problem is the current builds for both containers. So I didn't waste any more time trying to get rutorrent to work (likely it's that DSM's AppArmor thing again), and that's outside the scope of this thread.