Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About tmchow

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. does this block execution of rest of script until that is run? If not, i think I'd have to either: 1. run a sleep command instead within the script 2. create another script that uses "at now" to call my existing script
  2. I have a user script that uses `wget` to download ffmpeg for use on my system. I have it setup to run "at first start of array". In watching the bootup procedure, the script runs but complains it can't resolve the host, and I think it's due to network connectivity not being available yet. The specific command I'm running is this: wget -qO- --show-progress --progress=bar:force:noscroll https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz -O //boot/custom/ffmpeg/ffmpeg-git-amd64-static.tar.xz Why wouldn't internet connectivity be available by the time the array is started? Is the solution to just add say a multi-minute sleep to the start of the script?
  3. I'm having trouble with pip... I've installed it via nerd pack, but simply running "pip" from command line gets an error: I have Python 2.7 installed (also via nerd pack). Am I missing another dependency? SOLVED: Needed to install Python SetupTools. Did that and error went away.
  4. My second issue is an error I'm seeing in logs related to ffmpeg where I'm seeing this errror: No VA display found for device: /dev/dri/renderD128. e.g. screenshot of logs: I'm not sure if this is always been happening, but recently I added a Nvidia P2000 to my system to get HW transcoding to work (which seems to work since when I'm transcodoing, plex dashboard reports "(hw)" suffix and "watch nvidia-smi" shows the GPU is sued. I also at that time replaced my CPU to an Intel Xeon that supports QuickSync, but not because I wanted to use it for transcoding, just because the CPU was free. I'm NOT passing "--device=/dev/dri" in as extra params since I don't want to use the CPU, but i AM passing in "--runtime=nvidia" since I'm using the GPU. Admittedly I don't' know if these things are related to the error logs. Any ideas what's going on?
  5. I looked through my logs and noticed 2 issues I'd love to get help on: First, I'm noticing a permissioning error throughout logs complaining about access to some files in the appdata. e.g. If I cruise through the folders and file permissions in /Library/ I'm seeing most stuff owned by nobody:users which I thnk is correct. However, I do see some files owned by root:root with 700 permissions. eg. Inside the one of the _content directories, these are the permissions: THen in the offending posters directory, I see these weird permissions: So something seems wrong that those files are owned by root:root, but have 000? 1. How do I fix these permissions safely? 2. How did this even happen to begin with? ----- UPDATE: I ended up just brute forcing this by fixing permissions on every file and dir in appdata: chown -R nobody:users followed by find . -type f -perm 000 -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \;
  6. Thanks! I got this working with this setup using a user script daily https://github.com/Xaero252/unraid-plex-nvdec
  7. Thanks for much for the detailed reply. Very much appreciated!
  8. One question: What should I have `Tunable (enable NCQ)' set to? It's currently set to "off" but not sure if it should an alternate setting.
  9. One problem is that my config changed after I've run it since I formatted my original single cache SSD from xfs to btrfs so I could add a second cache SSD. But here's the output: [0:0:0:0] disk usb:4-1:1.0 /dev/sda 15.3GB [1:0:0:0] disk sas:0x4433221103000000 /dev/sdb 3.00TB [1:0:1:0] disk sas:0x4433221100000000 /dev/sdc 3.00TB [1:0:2:0] disk sas:0x4433221101000000 /dev/sdd 3.00TB [1:0:3:0] disk sas:0x4433221102000000 /dev/sde 3.00TB [1:0:4:0] disk sas:0x4433221104000000 /dev/sdf 6.00TB [1:0:5:0] disk sas:0x4433221105000000 /dev/sdg 6.00TB [1:0:6:0] disk sas:0x4433221106000000 /dev/sdh 6.00TB [1:0:7:0] disk sas:0x4433221107000000 /dev/sdi 6.00TB [2:0:0:0] disk sata:5707c181007ca132 /dev/sdj 512GB [3:0:0:0] disk sata:5707c1810043a27a /dev/sdk 512GB
  10. Installed an Nvidia P2000 tonight into my box and got this seemingly working after adding the --runtime=nvidia and gpu ID. I played a video through Plex app on my iphone and forced it to transcode by selecting a lower res (720p vs 1080p original movie). In the plex dashboard, I confirmed "(hw)" appears next to the transcode line, and running watch nvidia-smi on the unraid command line showed the plex transcoder process! One question I did have was that I had a pretty large spike in CPU utilization, presumably because of audio decoding. My CPU is a Xeon E3-1246 v3 3.5Ghz. In this screenshot, you'll see the first 40% spike when it was playing one 1080p movie (hw transcoding video to 720p) and audio was transcoding. The second spike to approx 80% was when I played a second 1080p movie on another device (again, hw transcoding video to 720p) and audio was also transcoding. After about 30s of each, the CPU utilization dropped back down to what appears to be ~5-10%. This was what the dashboard was showing while I was playing both movies: Is this CPU utilization spike expected? Is this because of the audio transcoding? If so, why does it spike then drop back down? I would've expected it to stay high if it was due to audio transcoding. Given it went as high as 80%, will this impact my ability to transcode more than 2 movies at once? My CPU supports QuickSync. Does enabling the flag --device=/dev/dri help audio decoding in any way or is that strictly for using the CPU's onboard GPU for video encoding (and won't help with my audio transcoding)? Lastly, unrelated, can someone explain why I see a mention of an NVDEC script? What does that actually do that is not already being done with the work I've done? (To be clear, I'm not asking to troubleshoot or get help with that script. Just trying to understand what is it).
  11. Just ran v4.0 on my array. Latest Unraid 6.7.2 with a 27TB array: Parity: 6TB WD Red Array: 3 x 6TB WD Red 2 x 3TB Seagate 1 x 3TB WD Red Test took 17 Hrs 45 Min 25 Sec to run. Attached the reports in case anyone was interested, including @Pauven LongSyncTestReport_2019_08_06_0008.csv LongSyncTestReport_2019_08_06_0008.txt
  12. I think this is a better plan than disabling mover. I could see how this could get hairy later, Eg. In event of a bug where the original mover script is not replaced
  13. Can you just run a find command for all files and folders on the cache disk directly?
  14. If it was said not to discuss it here, why not create a new topic?