Leaderboard

Popular Content

Showing content with the highest reputation on 05/08/18 in all areas

  1. Application Name: SABnzbd Application Site: http://sabnzbd.org/ Docker Hub: https://hub.docker.com/r/linuxserver/sabnzbd/ Github: https://github.com/linuxserver/docker-sabnzbd Tags You can choose, by using a tag, to use the unstable branch. Stable is the default and requires no tag (at times both branches may have the same version, but the stable/latest branch should never contain an alpha/beta/rc version) Add the tag, if required, to the linuxserver/sabnzbd line of the run/create command in the following format:- linuxserver/sabnzbd:unstable Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
    1 point
  2. Update your Docker and try the benchmark again and let me know if it worked - you don't need to purge again. I moved the temp files from the exported "DiskSpeed" directory to one internal inside the Docker (which gets cleaned up whenever you update the Docker) but missed a path reference. It should have only happened if you previously aborted a benchmark prior to updating the Docker app.
    1 point
  3. I've had it working on Ubuntu as a client.
    1 point
  4. Nobody else has these problems and many have much less memory than you already have. I think this below is the most likely cause of your problems. You have something using an incorrect path and it is filling up memory. You shouldn't be using any path that isn't in /mnt/user (or possibly /mnt/disk#, /mnt/cache, or /boot if you know why you're doing it). And depending on how you have your FTP server and clients setup, they might be mapping things in some way you don't understand if you don't understand mapping.
    1 point
  5. That's actually the recommendation of pretty much every BIOS update I've ever seen. The docs usually tell you to manually apply factory defaults, save, then make any changes you want. I suspect it's because of situations precisely like yours, where the BIOS changes make some settings act differently. Similar to limetech telling people to be sure their reported problem exists in safe mode, to eliminate as many variables as possible when testing new things.
    1 point
  6. IPv6 is only 1452 bytes due to the bigger header.
    1 point
  7. You have too many options on the menu bar. No matter, you can get the 'Help' for each entry by hovering over the each item (like "Folder caching function" until the cursor changes to a '?' mark and left-clicking the mouse.
    1 point
  8. I have similar issue, if using HDMI in GTX1050 display card, local GUI resolution would be 1024x768 (not remember BIOS screen resolution correct or not). But if connect use DVI, then a normal 1080 could be output. The display card have 3 output, DVI, HDMI, DP. I suggest you try a DVI connect first, i.e. DVI to HDMI cable.
    1 point
  9. The epyc cpus I’ve seen are high core low freq, coupled with ecc which runs at stock speeds I’m not surprised it gets dusted by TR. For what it’s worth, my TR setup has been flawless... I just timed my purchase after the major issues had been resolved.
    1 point
  10. For those keeping score at home, I just seen there is a new BIOS revision for the motherboard Version 0601 - 2018/05/02 Update AGESA 1.0.0.5 recommend to keep C-State [enabled] Woot now that's a bios revision I'll jump on, I know what I'm going to do tonight! Any issues, I'll update this post with more data. EDIT: There was one issue on flash. I don't know if this was from version level, or the fact that I skipped a bios generation, but all settings in the bios were reset to factory defaults. So, be sure to take note of any custom changes you make in your BIOS, prior to flashing. Also, worth noting, per the website's recommendation, I kept C-states enabled (again, didn't seem to be an issue before), and deleted the line out of my go file - syslinux and go are basically stock at this point.
    1 point
  11. Can also confirm that Plex is working fine in 6.5.1 but that it was also working fine all the way through 6.4.x and 6.5.x As with @BetaQuasi I too am using Linuxserver's version.
    1 point
  12. I had no issues with Plex all the way through the 6.5 series, and it is again working fine with this update. Perhaps it's something specific with your config? (I'm using linuxserver.io's docker as it is kept up to date, not an issue to be seen.)
    1 point
  13. Don't know how you searched. This comes up immediately when using your three keywords: https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/ https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/
    1 point
  14. After adding this to the syslinux confi now it works label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream,multifunction iommu=pt vfio-pci.ids=8086:1521 initrd=/bzroot IOMMU group 14: [8086:1521] 05:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) IOMMU group 15: [8086:1521] 05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) But both NICS are being blacklisted and passthrough to the VM and I only want the second, it is possible? any other workaround to try?
    1 point
  15. @tillkrueger @jenskolson @trurl @unrateable @jonathanm @1812 @Squid since all of you were active in this thread. I found a way to get the file transfer back. Bring up the Guacamole left panel menu (CTRL ALT SHIFT) Input Method = On Screen Keyboard In the On Screen Keyboard, use ALT (it'll stay on, 'pressed') then TAB, select it using TAB, then ALT again (to turn off) A tip I found too, is that anytime doing a copy or move, always best to use the 'queue' button in the pop-up confirmation dialog so that multiple transfers are sequentially handled. It's easy to get to the queue, I found using this it often mitigates much of my need to see the file transfer progress window. The 'Queue Manager' is easy to get back on the screen by using the top menu, Tools > Queue Manager
    1 point