Thank you for your response. Sorry, those are both my mistakes in posting. I had to type that out by hand because VNC wouldn’t copy/paste and then I copied my first typed lines and didn’t change them. They are correct now and were already set as you suggested.
I’ll try the -v option to see if it sheds any light on what’s going on.
Here is the output:
mount.nfs: timeout set for Thu Sep 24 11:59:58 2020
mount.nfs: trying text-based options 'vers=4.2,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=172.16.0.250'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 172.16.0.250 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 172.16.0.250 prog 100005 vers 3 prot UDP port 55268
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/Movies/
mount.nfs: timeout set for Thu Sep 24 11:59:58 2020
mount.nfs: trying text-based options 'vers=4.2,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=172.16.0.250,clientaddr=172.16.0.200'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=172.16.0.250'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 172.16.0.250 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 172.16.0.250 prog 100005 vers 3 prot UDP port 55268
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting 172.16.0.250:/mnt/user/files/TV Shows/
I tried adding vers=3 to the mount points but that didn’t work either.
Ok I think I spotted the error, I missed it the first time when I read through your message. Assuming you typed the lines exactly as written in VNC, capitalization and all, it’s a case error. Your unraid server is exporting /mnt/user/Files (uppercase F), where your mounts are listed with a lowercase f.
Also, your export parameters aren’t configured correctly. If you need the share to be mounted in read/write mode, change it to 172.16.0.0/24(rw). Note there are no spaces between the IP range and the parameters either. Otherwise, just clear the line completely and it will be exported in read-only mode for all hosts. The sec=sys is redundant since it’s already the default option, and UID isn’t a valid option at all.
I changed the NFS rule on the share and changed the lower case f to F and it worked! Thank you!!
Hey I am having some issue with my HP 290 server
dmesg output
[ 6964.806502] NFS: server 192.168.1.16 error: fileid changed
fsid 0:54: expected fileid 0x90100020cdaf602, got 0x27000001073d68
[11429.970514] NFS: server 192.168.1.16 error: fileid changed
fsid 0:54: expected fileid 0x901000205eace4a, got 0x27000001074b4c
[11429.972082] NFS: server 192.168.1.16 error: fileid changed
fsid 0:54: expected fileid 0x90200038024eb61, got 0x27000001074df1
[11429.973352] NFS: server 192.168.1.16 error: fileid changed
fsid 0:54: expected fileid 0x9020000800cb958, got 0x2700000107509c
[14384.783322] perf: interrupt took too long (2564 > 2500), lowering kernel.perf_event_max_sample_rate to 78000
[14995.881394] perf: interrupt took too long (3214 > 3205), lowering kernel.perf_event_max_sample_rate to 62000
[15401.910582] perf: interrupt took too long (4079 > 4017), lowering kernel.perf_event_max_sample_rate to 49000
[16030.657985] perf: interrupt took too long (5193 > 5098), lowering kernel.perf_event_max_sample_rate to 38500
[21312.849897] systemd-journald[405]: File /var/log/journal/e148bebc59ef4552a44ebe03bba7f7d7/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[28030.043686] nvme nvme0: I/O 512 QID 1 timeout, aborting
[28030.043701] nvme nvme0: I/O 513 QID 1 timeout, aborting
[28030.043706] nvme nvme0: I/O 514 QID 1 timeout, aborting
[28030.043710] nvme nvme0: I/O 515 QID 1 timeout, aborting
[28030.043714] nvme nvme0: I/O 516 QID 1 timeout, aborting
[28060.251529] nvme nvme0: I/O 512 QID 1 timeout, reset controller
[28091.483263] nvme nvme0: I/O 24 QID 0 timeout, reset controller
[28154.971176] INFO: task jbd2/dm-0-8:328 blocked for more than 120 seconds.
[28154.971221] Not tainted 5.4.0-48-generic #52-Ubuntu
[28154.971249] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[28154.971292] jbd2/dm-0-8 D 0 328 2 0x80004000
[28154.971296] Call Trace:
[28154.971304] __schedule+0x2e3/0x740
[28154.971308] ? __wake_up_common_lock+0x8a/0xc0
[28154.971311] schedule+0x42/0xb0
[28154.971314] jbd2_journal_commit_transaction+0x258/0x17e8
[28154.971317] ? __switch_to_asm+0x40/0x70
[28154.971319] ? __switch_to_asm+0x34/0x70
[28154.971321] ? __switch_to_asm+0x40/0x70
[28154.971324] ? __switch_to_asm+0x34/0x70
[28154.971326] ? __switch_to_asm+0x40/0x70
[28154.971328] ? __switch_to_asm+0x34/0x70
[28154.971331] ? __switch_to_asm+0x40/0x70
[28154.971333] ? __switch_to_asm+0x40/0x70
[28154.971335] ? __switch_to_asm+0x34/0x70
[28154.971338] ? __switch_to_asm+0x34/0x70
[28154.971340] ? wait_woken+0x80/0x80
[28154.971345] ? try_to_del_timer_sync+0x54/0x80
[28154.971348] kjournald2+0xb6/0x280
[28154.971350] ? wait_woken+0x80/0x80
[28154.971353] kthread+0x104/0x140
[28154.971355] ? commit_timeout+0x20/0x20
[28154.971357] ? kthread_park+0x90/0x90
[28154.971360] ret_from_fork+0x35/0x40
[28154.971370] INFO: task rs:main Q:Reg:848 blocked for more than 120 seconds.
[28154.971406] Not tainted 5.4.0-48-generic #52-Ubuntu
[28154.971434] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[28154.971474] rs:main Q:Reg D 0 848 1 0x00000000
If anyone could take a look I would appreciate it 
Ends up being unresponsive and halting the plex server from any interaction via ssh or physically, need to hard reboot and it works fine again for a couple hours.
I’ve recently snatched up a HP Prodesk 600 G2 Mini and want to make it a stand-alone Plex server.
Will I need a DisplayPort Dummy Plug to take full advantage of QuickSync or is this only if I want to access headless at a high resolution?
Thanks in advance!
It is required.
Egawd… how did I miss that 
Thanks for helping and not scolding me 
My Intel i3-8100 with UHD630 is able to transcode 4x (from HDD) and even 5x (from NVMe) concurrent 4K streams:
1080p would be much more. I do not have enough Clients / CPU Power to test this scenario as well, but should be ~20x as shown through others multiple times.
@antigravity83
You wondered about high IOwait compared to Nvidia. I think this isn’t really an IOwait as there is no IOwait on the disks. This is only related to the fully utilized iGPU which is not able to answer fast enough. I think this simply means its overloaded and you reached the maximum video processing limit. You can check this by installing Intel’s GPU Tools. I posted some screenshots in the Unraid forums.
Great to know this. Thank you.
What’s the point of transcoding 4K? HDR is stripped and not tone mapped properly.
The point of having* 4K is to watch it in 4K.
Will be maybe with the 11th / 12th gen Intel or if Plex adds H265 transcoding output.
I never said I want to use it, its only a benchmark. I principally create rips of 1080p and 4K discs, so I don’t need to use the 4K version as transcoding source.
I expressly dissociate myself from those actions. I prefer buying discs.
It’s actually already supported on the iGPU side, Plex does not support it.
It’s not a valid benchmark if there’s no reason to do it.
Do you know if any results for Plex transcoding on the new Tiger Lake? Thanks.
What do you mean?
How does it work compared to earlier models. It is supposed to be able to handle a lot of new formats.
For anyone familiar with the details: when considering 8th-gen QuickSync processors, is there a substantial difference in overhead for transcoding h.264 vs. h.265 (source files are all 1080p)? Much of my library is 10-bit h.265.
A bit, a faster processor would help. However, I’d start cheap and work your way up.
Makes sense. Thank you!
Check out the HP 290 if you haven’t already, they are still < $200 and cover 95% of people’s needs.