Jump to content

tucansam

Members
  • Content Count

    857
  • Joined

  • Last visited

Community Reputation

12 Good

About tucansam

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Question. I have noticed a lot of dupe movies in Plex, turns out Radarr is downloading copies of movies if the filenames don't have "1080p" or "720" or "bluray" in the name. So if I rip a BluRay from my collection with MakeMKV and get "Star Wars.mkv" as the filename, or "\movies\star wars\title01.mkv" as the filename, Radarr seeks a version from the internet with something in the filename that makes it believe its in a high-res format. I have been playing with the various search parameters, ie, standard def, high def, etc., and can't seem to make this stop. Advice? Thanks.
  2. Hi. In the description it says, "It also includes Privoxy to allow unfiltered access to index sites, to use Privoxy please point your application at "host ip:8118" Can anyone tell me what that means? I have been using it with PIA VPN (am getting ready to change so I went back to see if there were updates and noticed that description) and didn't know I could (should?) be using a proxy?
  3. Disk 10 has errors as of this morning. Array has run perfectly for years now. Few days ago I pulled the chassis panels and drives (three 5-in-1 cages) and blasted everything with compressed air. Probably an mis-seated cable or just need to re-seat the disk in the cage, right? Diags attached just in case. ffs2-diagnostics-20200516-1450.zip
  4. tucansam

    RTL8111E

    "Mostly?" Hahahaha. OK, that is making me nervous.
  5. tucansam

    RTL8111E

    LOL no one, then?
  6. How can I prevent Radarr from sending files with ISO and m2ts content to sab? I don't want to download anything except mkv, avi, and mpeg. Thanks.
  7. Exactly what I was looking for, and understood on the final point. Thank you. Additional reading shows that the nvidia GPU remains active and drawing considerable power after transcodes are done, and that there is a new driver coming, with no ETA. Perhaps I will hold off for a few weeks.
  8. tucansam

    RTL8111E

    When I built my current server, the Realtek RTL8111E was still on the naughty list. Or at least the "not suggested" list. I have an Intel PCIe gig NIC in a slot, but now I need the slot. If I go back to the onboard RTL8111E, will a plague of locusts and frogs falling from the sky be visited upon me? (I'm on 6.8.3)
  9. I did some reading, and it seems as though I've opened a can of worms. Do any of the Plex dockers for unraid support passing the GPU hardware on to Plex? * Moderator Removed Comment *
  10. Thank you for your reply, that is quite useful information indeed. Given that the i7-2600 is on the list for hardware-based encoding ala the integrated GPU, is this a situation where I would need a MB that passed hardware on, like in a virtual machine? Or will the Plex docker automatically use the GPU if available? Same question for a discreet video card.... If I can simply add a modern GPU to my unraid server, then theoretically I don't have to upgrade at all, I can just let Plex use whatever GPU I add, correct? Are there additional configurations that need to be done in that case? Thanks again.
  11. Currently running an i7-2600 with 32GB RAM that almost never sees more than 8GB in use, along with a ton of dockers, including Plex. When the system was built, the i7-2600 was only a few years old. So its been that long since I've upgraded anything. But everything is running well. But.... I am giving many of my family members access to Plex because of all the stay at home stuff. Everything I do is through a VPN. I'm usually around 90-120Mbps down and 10-20 up, but right now I'm seeing 20-30 down and 8-10 up, probably because 99999 people are on the internet in my neighborhood. I have also started to see a lot of 2160p content, and I don't think my i7 can handle transcoding that (I think I tried once), so I have been limiting everything to 1080. I think it might be time to look at upgrading, and future-proofing, my unraid server. I recall numerous AMD vs Intel discussions in the past, specifically mentioning one particular benchmark number as the gospel to follow with regard to CPU selection, but I can't remember now. And now there is hardware acceleration, or something, using a video card? Not very smart or up to speed on that. Anyway, my goals, in no particular order, would be: low heat, low power consumption, new-ish hardware able to handle the next 5+ years without me upgrading again, able to handle 1080p+ streams for two local plus four or five remote users, possibly simultaneously. I usually buy hardware used, and a generation or two behind what is current, but I don't have to do that in this case. I want to be able to use my existing PCIe controller and gig-e card, so this would be a CPU/MB/RAM upgrade only, and whatever I buy would have to have slots for my LSI etc. Comments welcome. Thanks.
  12. I've used SMR drives for years, had one as my parity disk for a long time, then replaced with two WD Reds (thought they were not SMR, oh well, whatever). I haven't run a cache disk ever. No performance issues that I can't attribute to my network.
  13. Docker and Plug-ins take about 5 mins to "check for updates" and then cannot establish comms with any host to grab software. Second time this has happened (first time resolved on its own, no idea). While troubleshooting I see this: -- root@ffs2:~# traceroute google.com traceroute to google.com (172.217.3.46), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 0.397 ms 0.382 ms 0.373 ms 2 10.81.10.1 (10.81.10.1) 46.047 ms 43.021 ms 43.093 ms 3 104.200.151.1 (104.200.151.1) 43.355 ms 53.200 ms 43.501 ms 4 107.152.99.93 (107.152.99.93) 42.933 ms 43.095 ms 38.097 ms 5 ae1-205.cr0-phx1.ip4.gtt.net (216.221.157.145) 46.129 ms 52.688 ms 43.414 ms 6 ae11.cr4-lax2.ip4.gtt.net (89.149.140.77) 52.568 ms 54.918 ms 50.865 ms 7 as15169.cr4-lax2.ip4.gtt.net (216.221.156.186) 83.724 ms 87.279 ms 72.14.194.163 (72.14.194.163) 85.408 ms 8 108.170.247.243 (108.170.247.243) 83.773 ms 87.483 ms 88.058 ms 9 108.170.234.124 (108.170.234.124) 87.096 ms 108.170.230.135 (108.170.230.135) 82.408 ms 108.170.234.124 (108.170.234.124) 86.866 ms 10 172.253.71.26 (172.253.71.26) 75.172 ms 74.978 ms^C root@ffs2:~# nslookup google.com nslookup: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory root@ffs2:~# nslookup nslookup: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory root@ffs2:~# -- What the heck? Checking for updates to the OS doesn't work anymore either. But all of my dockers can do whatever they need to do, as far as dns and what-not goes.