ClunkClunk

Members
  • Posts

    275
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1447 profile views

ClunkClunk's Achievements

Contributor

Contributor (5/14)

5

Reputation

  1. I also had a similar result. Upgrade, reboot via WebGUI with no issues, and when it came back up it started a parity check. Dec 11 09:55:36 Tower emhttpd: unclean shutdown detected That's the only entry I can find relating to it. No errors on my cache drive.
  2. Suggestion - have this default to "No" rather than "Yes." Reason - grumpy text message from wife asking why Plex wasn't working I do like the feature though! I just had to tweak some settings.
  3. In case it helps, I think this is how to get the On Deck from Plex using the API: wget -q -O- http://$PLEXURL:32400/library/onDeck?X-Plex-Token=$PLEXTOKEN Set $PLEXURL to your PMS's ip address, and $PLEXTOKEN to your Plex Auth Token, and it'll return with XML. You'll then need to parse out the 'file=' entries to get the filename and path, and replace the returned filepath with whatever the Docker container is mapped to (for example, I pass /tv to my Plex docker container and it maps to /mnt/user/TV on my unRAID).
  4. ca-vancouver.privateinternetaccess.com is working for me right now.
  5. I basically did what the example shell script has in it, but I put it all in my go script, and it works just fine in 6.8.3 since it doesn't execute anything directly (just copies and changes permissions). 6.8.0 tightened the security of the go script to not execute things directly from the boot flash drive. My go script contains this: mkdir /root/.ssh chmod 700 /root/.ssh cp /boot/config/ssh/authorized_keys /root/.ssh/ chmod 600 /root/.ssh/authorized_keys And I just make sure that /boot/config/ssh/authorized_keys contains the public key I want to use. Alternately, you could use the go script to copy the example shell script to /tmp, set the permissions, then execute it. I've not tested it but it would be something like this in the go script (with the setup_ssh_client.sh unaltered and in the recommended location): cp /boot/config/ssh/setup_ssh_client.sh /tmp/setup_ssh_client.sh chmod +x /tmp/setup_ssh_client.sh bash /tmp/setup_ssh_client.sh
  6. I seem to have fixed this, but I'm not sure how. I have been experimenting with CPU pinning with my docker containers, and have restricted some dockers to only a handful of cores, and given others a bunch of cores. After doing this, the WebUI has been behaving itself as expected! I have no idea exactly why changing the CPU core assignments would affect this issue, but I'll take it.
  7. Looks OK to me - 'dec' (the decoder) is showing a percent or two of utilization, and 'enc' (the encoder) is showing a percent or two of utilization. A GTX 1050 4GB has enough horsepower to handle about 14 simultaneous 1080p transcodes though it's software locked to 2 transcodes, so if this was doing just one stream, and it filled Plex's buffer already, only a percent or two would be needed to maintain said buffer. A couple more things I've noticed from my Quadro P400 (I don't have a GTX 1050 to test so I'm just guessing): Pwr:Usage doesn't necessarily populate even when the card is running; P0 is almost always on; and fan speeds may drop to 0 if the card is totally unused. To really push your card, try setting Plex's buffer to something huge - like 3600 seconds, so it tries to encode an entire hour at a time. Then launch two transcodes and see how your card reacts.
  8. Could you try `nvidia-smi dmon` while you're transcoding, and post a few second of output?
  9. A GTX 1050 is fairly recent, supports NVENC/NVDEC, and should work with this plugin (though I don't have one to try - spec wise it seems totally fine).
  10. You are correct. It won't. The GTX 460 is a Fermi architecture, which predates NVENC and NVDEC so even if there were drivers, it can't be utilized for transcoding.
  11. Hi everyone, I've been having an odd problem lately that I haven't been able to pin down. Upon the initial load of Main or Docker, my browser takes 30-60 seconds to load the page. However subsequent loading of those pages, or other pages in the WebUI open quickly as expected. After a few hours, the issue returns and a load of Main or Docker is slow again for the initial load, then after that it's normal. I can replicate this issue in other browsers with no cached site data or browser add-ons. I've tried changing DNS on my server, disabled the Docker system, and tried booting unRAID in safe mode. I've also browsed the forum here looking for similar reports - the issue with Avahi isn't happening. I believe this issue started somewhere in the 6.8 betas, but I can't be certain. I'm running 6.8.1, and will try 6.8.2 later today. Anyone have any ideas?
  12. I love how for the past decade, unRAID has made management, expansion, and dealing with a random assortment of hard drives an easy task for me. I'd like to see multiple arrays and pools, so I could make some optimizations between speed and number of drives for primary/secondary use.
  13. August 2009 is when I first started using unRAID so that's a decade! Not bad.
  14. I believe I'm experiencing this too. While on 6.7.2, when the mover runs, I had some big performance issues - notably with streaming things from an array drive on my LAN with Plex, but I also saw slowdowns with things like rsync. I am not sure what version this behavior started, because my mover generally only runs at 2am, however I transferred a bunch of data to my cache drive during the day recently, and manually started the mover and I noticed the issue (and so did my wife - "what's wrong with Plex?!"). I've not done any formal troubleshooting, but I did revert back to 6.6.7 and haven't experienced the problem again. I might have some time this week to experiment a bit more formally.
  15. If you have a Quadro 4000, a circa 2010 card, then it seems like it's a non-issue as that card doesn't support NVENC or NVDEC for hardware transcoding according to NVIDIA's NVENC and NVDEC support matrix. If you have a Quadro P4000, K4000, M4000, or RTX 4000, this NVIDIA plugin should be fine, since all these cards are supported by the 418.43 drivers. It sounds like you have a Quadro 4000 based on your description and needing older drivers. Is that right?