scottpk

I came here because I got this message... but... 1. I'm not actually using the plugin version of Plex anymore, and 2. I see nothing wrong in this file. File contents: #[PMS Settings] #START_CONFIGURATION #Set autostart with array ENABLED="false" RUNAS="unraid-plex" #Set home of Plex Media Server PLEX_MEDIA_SERVER_HOME="/usr/local/plexmediaserver" #Set home for Plex metadata PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR="/mnt/user/plex/Library" #the number of plugins that can run at the same time PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=6 #ulimit -s PLEX_MEDIA_SERVER_MAX_STACK_SIZE=10000 #ulimit -l #PLEX_MEDIA_SERVER_MAX_LOCK_MEM=3000 #ulimit -n PLEX_MEDIA_SERVER_MAX_OPEN_FILES=4096 #where the mediaserver should store the transcodes PLEX_MEDIA_SERVER_TMPDIR="/tmp/plex" #STOP_CONFIGURATION

It's purely cosmetic, but I noticed, on the CA page the blue "i" is a different shade of blue. Other pages: #486dba; Apps page: #00b8d6; I think you're overriding the main theme's color somehow?

If you are wanting to see this while your VM is running, the nature of hardware passthrough makes it most likely impossible, at least on most GPUs. The host is not able to communicate with the device during the time that it's passed through to the VM, otherwise this could cause serious issues. I would guess this is the reason they don't have such a feature - if you're passing through hardware it can't read it anyway, and vanilla UnRAID doesn't make use of any features that would cause your GPU to warm up.

If I'm not mistaken that just means it wasn't able to retrieve a unit of work. You might just need to wait, their infrastructure is under heavier load with the spike in interest from COVID-19.

An FYI for anyone else who didn't know, and is afraid this is going to turn their CPU into a toaster... you can limit CPU usage using --cpus=x in the "extra parameters" (found in advanced). x is a number correlated to CPU usage (honestly the exact correlation is not entirely clear to me, you can use decimals or integers - all I know is higher = more CPU, lower = less CPU). Either way toying with this seems to help greatly with keeping down the temperature and fans... https://docs.docker.com/config/containers/resource_constraints/#cpu

In general things have been pretty solid, but recently I've been having the system lock up every couple days, where the only apparent way to break through is to hard reset. (Or at least, the web UI will not respond... since the video card is setup for passthrough I don't know whether it spit a message on-screen.) I can't think of anything that would've coincided with this starting to happen... I enabled the option to persist the syslog through reboots, attached is the syslog I captured today after having to hard reset again... I see that from 2:45 PM until I reboot there is a trace message from the Linux RCU thread, about every three minutes... Aug 14 14:51:36 Raiden kernel: rcu: INFO: rcu_sched self-detected stall on CPU Aug 14 14:51:36 Raiden kernel: rcu: 1-....: (420005 ticks this GP) idle=1be/1/0x4000000000000002 softirq=1700269094/1700269094 fqs=102699 Aug 14 14:51:36 Raiden kernel: rcu: (t=420006 jiffies g=217067417 q=25007350) Aug 14 14:51:36 Raiden kernel: NMI backtrace for cpu 1 Aug 14 14:51:36 Raiden kernel: CPU: 1 PID: 19660 Comm: kworker/u64:2 Tainted: G W 4.19.56-Unraid #1 Aug 14 14:51:36 Raiden kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Pro4, BIOS P3.10 03/07/2019 Aug 14 14:51:36 Raiden kernel: Workqueue: events_power_efficient gc_worker Aug 14 14:51:36 Raiden kernel: Call Trace: Aug 14 14:51:36 Raiden kernel: <IRQ> Aug 14 14:51:36 Raiden kernel: dump_stack+0x5d/0x79 Aug 14 14:51:36 Raiden kernel: nmi_cpu_backtrace+0x71/0x83 Aug 14 14:51:36 Raiden kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Aug 14 14:51:36 Raiden kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7 Aug 14 14:51:36 Raiden kernel: rcu_dump_cpu_stacks+0x91/0xbb Aug 14 14:51:36 Raiden kernel: rcu_check_callbacks+0x28f/0x58e Aug 14 14:51:36 Raiden kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Aug 14 14:51:36 Raiden kernel: update_process_times+0x23/0x45 Aug 14 14:51:36 Raiden kernel: tick_sched_timer+0x36/0x64 Aug 14 14:51:36 Raiden kernel: __hrtimer_run_queues+0xb1/0x105 Aug 14 14:51:36 Raiden kernel: hrtimer_interrupt+0xf4/0x20d Aug 14 14:51:36 Raiden kernel: smp_apic_timer_interrupt+0x79/0x91 Aug 14 14:51:36 Raiden kernel: apic_timer_interrupt+0xf/0x20 Aug 14 14:51:36 Raiden kernel: </IRQ> Aug 14 14:51:36 Raiden kernel: RIP: 0010:gc_worker+0xf6/0x258 Aug 14 14:51:36 Raiden kernel: Code: 02 0f 8f ec 00 00 00 48 8b 05 00 ea 8b 00 05 00 5c 26 05 41 89 87 88 00 00 00 e9 d4 00 00 00 48 8b 15 e8 e9 8b 00 29 d0 85 c0 <7f> 11 4c 89 ff e8 da e9 ff ff ff 44 24 08 e9 b6 00 00 00 85 ed 0f Aug 14 14:51:36 Raiden kernel: RSP: 0018:ffffc90008af7e68 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13 Aug 14 14:51:36 Raiden kernel: RAX: 000000001742ae36 RBX: ffffffff8228e440 RCX: ffffffffffffffb8 Aug 14 14:51:36 Raiden kernel: RDX: 00000001174f929c RSI: 0000000000000135 RDI: ffffffff8228e440 Aug 14 14:51:36 Raiden kernel: RBP: 0000000000000000 R08: 0000000000000018 R09: 0000746e65696369 Aug 14 14:51:36 Raiden kernel: R10: 8080808080808080 R11: fefefefefefefeff R12: 0000000000002f36 Aug 14 14:51:36 Raiden kernel: R13: 0000000064ac2ff9 R14: ffff8882e3b18f48 R15: ffff8882e3b18f00 Aug 14 14:51:36 Raiden kernel: ? gc_worker+0x1cc/0x258 Aug 14 14:51:36 Raiden kernel: process_one_work+0x16e/0x24f Aug 14 14:51:36 Raiden kernel: ? pwq_unbound_release_workfn+0xb7/0xb7 Aug 14 14:51:36 Raiden kernel: worker_thread+0x1dc/0x2ac Aug 14 14:51:36 Raiden kernel: kthread+0x10b/0x113 Aug 14 14:51:36 Raiden kernel: ? kthread_park+0x71/0x71 Aug 14 14:51:36 Raiden kernel: ret_from_fork+0x22/0x40 Aug 14 14:54:36 Raiden kernel: rcu: INFO: rcu_sched self-detected stall on CPU Aug 14 14:54:36 Raiden kernel: rcu: 1-....: (600008 ticks this GP) idle=1be/1/0x4000000000000002 softirq=1700269094/1700269094 fqs=146764 Aug 14 14:54:36 Raiden kernel: rcu: (t=600009 jiffies g=217067417 q=35280857) Aug 14 14:54:36 Raiden kernel: NMI backtrace for cpu 1 Aug 14 14:54:36 Raiden kernel: CPU: 1 PID: 19660 Comm: kworker/u64:2 Tainted: G W 4.19.56-Unraid #1 Aug 14 14:54:36 Raiden kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Pro4, BIOS P3.10 03/07/2019 Aug 14 14:54:36 Raiden kernel: Workqueue: events_power_efficient gc_worker Aug 14 14:54:36 Raiden kernel: Call Trace: Aug 14 14:54:36 Raiden kernel: <IRQ> Aug 14 14:54:36 Raiden kernel: dump_stack+0x5d/0x79 Aug 14 14:54:36 Raiden kernel: nmi_cpu_backtrace+0x71/0x83 Aug 14 14:54:36 Raiden kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Aug 14 14:54:36 Raiden kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7 Aug 14 14:54:36 Raiden kernel: rcu_dump_cpu_stacks+0x91/0xbb Aug 14 14:54:36 Raiden kernel: rcu_check_callbacks+0x28f/0x58e Aug 14 14:54:36 Raiden kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Aug 14 14:54:36 Raiden kernel: update_process_times+0x23/0x45 Aug 14 14:54:36 Raiden kernel: tick_sched_timer+0x36/0x64 Aug 14 14:54:36 Raiden kernel: __hrtimer_run_queues+0xb1/0x105 Aug 14 14:54:36 Raiden kernel: hrtimer_interrupt+0xf4/0x20d Aug 14 14:54:36 Raiden kernel: smp_apic_timer_interrupt+0x79/0x91 Aug 14 14:54:36 Raiden kernel: apic_timer_interrupt+0xf/0x20 Aug 14 14:54:36 Raiden kernel: </IRQ> Aug 14 14:54:36 Raiden kernel: RIP: 0010:gc_worker+0xa7/0x258 Aug 14 14:54:36 Raiden kernel: Code: 44 89 e0 48 8d 04 c2 4c 8b 30 41 f6 c6 01 0f 85 36 01 00 00 41 0f b6 46 37 48 c7 c1 f0 ff ff ff 41 ff c5 48 6b c0 38 48 29 c1 <4d> 8d 3c 0e 49 8b 97 80 00 00 00 41 8b 87 88 00 00 00 0f ba e2 0e Aug 14 14:54:36 Raiden kernel: RSP: 0018:ffffc90008af7e68 EFLAGS: 00000296 ORIG_RAX: ffffffffffffff13 Aug 14 14:54:36 Raiden kernel: RAX: 0000000000000038 RBX: ffffffff8228e440 RCX: ffffffffffffffb8 Aug 14 14:54:36 Raiden kernel: RDX: 00000001175251bf RSI: 0000000000000135 RDI: ffffffff8228e440 Aug 14 14:54:36 Raiden kernel: RBP: 0000000000000000 R08: 0000000000000018 R09: 0000746e65696369 Aug 14 14:54:36 Raiden kernel: R10: 8080808080808080 R11: fefefefefefefeff R12: 0000000000002f36 Aug 14 14:54:36 Raiden kernel: R13: 00000000dc4f32b4 R14: ffff8882e3b18f48 R15: ffff8882e3b18f00 Aug 14 14:54:36 Raiden kernel: ? gc_worker+0x1cc/0x258 Aug 14 14:54:36 Raiden kernel: process_one_work+0x16e/0x24f Aug 14 14:54:36 Raiden kernel: ? pwq_unbound_release_workfn+0xb7/0xb7 Aug 14 14:54:36 Raiden kernel: worker_thread+0x1dc/0x2ac Aug 14 14:54:36 Raiden kernel: kthread+0x10b/0x113 Aug 14 14:54:36 Raiden kernel: ? kthread_park+0x71/0x71 Aug 14 14:54:36 Raiden kernel: ret_from_fork+0x22/0x40 does anyone understand how to tell what it is saying is stalled and/or how I can work backward to find the culprit? syslog

This can be ignored now - I've ended up picking up a low-profile GeForce GTX 1050 Ti which is letting me do just this.

I've figured out how to extract the video BIOS, but still this is not working for me.

I've tinkered with this a bit more - I have changed the BIOS so that now unRAID is booted through UEFI. Now I do not get a solid screen, rather I get a flash of the pattern from before followed by a black screen (not no signal, the display uses blue for no signal). I have noticed the following gets repeated all over the system log: Apr 3 21:22:06 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:06 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844afa0] Apr 3 21:22:07 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:07 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844afd0] Apr 3 21:22:08 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:08 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b000] Apr 3 21:22:09 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:09 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b030] Apr 3 21:22:10 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:10 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b060] Apr 3 21:22:11 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:11 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b090] Apr 3 21:22:12 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:12 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b0c0] Apr 3 21:22:13 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:13 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b0f0] Apr 3 21:22:14 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:14 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b120] Apr 3 21:22:15 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:15 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b150] Apr 3 21:22:16 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:16 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b180] Apr 3 21:22:17 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:17 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b1b0] Apr 3 21:22:18 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:18 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b1e0] Apr 3 21:22:19 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:19 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b210] Apr 3 21:22:20 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:20 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b240] Apr 3 21:22:21 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:21 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b270] Apr 3 21:22:22 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:22 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b2a0] Apr 3 21:22:23 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:23 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b2d0] Apr 3 21:22:24 Raiden kernel: iommu ivhd0: AMD-Vi: Event logged [ Apr 3 21:22:24 Raiden kernel: iommu ivhd0: IOTLB_INV_TIMEOUT device=38:00.0 address=0x000000021844b300] Has anyone had any luck getting passthrough to work on the Ryzen APUs?

Hello, I am new to unRAID but I have gotten through setting up an array and creating a share, which I am able to access from my laptop. The case is HTPC size and fits in the entertainment center, so I am trying to set up a VM with passthrough so that I can watch movies - I've made some headway in that I've gone from complaints about IOMMU group, to the video blanking out and then the TV not detecting a signal when the VM starts, to getting a signal that indicates a problem (it is green or teal with some vertical lines). But I have not been able to get it to fully work experimenting with different BIOS options. So far choosing the OVMF BIOS option got me no signal, and the SeaBIOS option got me these vertical bars. I have to reboot to get rid of them, the VM refuses to stop through the UI. Here's the info that shows in the corner: M/B: ASRock - B450M Pro4 CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3500 HVM: Enabled IOMMU: Enabled Cache: 384 kB, 2048 kB, 4096 kB Memory: 8 GB (max. installable capacity 256 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a I see there is a field where I can provide a copy of the video BIOS, but I don't know how to extract this or if it's even something I should do... Is there something I am missing that I will need to do? If possible I would like to avoid installing a video card, the case is compact and the Vega graphics should be fine for movies and TV anyway.