bmdegraaf

Thanks for this plugin! If i have this installed on my x9scm board, can i remove the dynamix auto fan control?

I am mounting two SSD's with unassigned devices. Do i need to setup a trim script or does the plugin take care of this as well?

Thanks for the quick heads up... Also reverted back to 0.9.12.19 and all is well again... Any pinpoint whether plex will fix it any time soon?

I am having a problem transcoding. It seems i am running out of space according to the log. Some bigger mkv will not even start because of this, whereas some time ago they worked. I am transcoding in ram, /transcode => /tmp Still have plenty of ram to go about, this did not change. I did see in the log that the docker chowns /transcode from root:root to abc:abc during startup. Could this be the evil? I am on the latest plexpass version.

Luckily enough only the openvpn was affected.

Happened unintentionally, not knowing that when you run the script for all disks, that it also runs for disks that are mounted via unassigned devices. These as not mentioned in the dropdown list, but are apparently called upon.

Deleted not only the docker but also the files outside the docker and reinstalled. All working again. Things must have gone sour when in ran the unraid permissions script on my appdata disk.

Got everything working since a couple of days, however this morning i restarted and it would not start anymore. I think it has to do with initial ubuntu it downloads during startup. It takes place, but once download finishes the docker stops.... After reading package list... Tried reinstalling, but the same issue....

Moved the data to cache only and everything is working as expected. I guess plugins work better with data residing on cache.

Peter, many thanks for this excellent plugin!! I have been using the server a lot. However, when rebooting the server it does not start automatically. Although I have checked the box within the application. When starting the openvpn server manually, it starts. The appdata is not residing on the cachedrive, but on a SSD mounted by unassigned devices, where all my docker apps are residing as well. Could this be causing the issue? Does the appdata need to reside on the cache drive? Or could i build in a delay for the plugin to start to ensure the SSD is mounted? I have a feeling this is the underlying problem.

Installed the docker... I can reach the admin page when using bridge mode, however not in host mode. In bridge mode the connection test states my server is not reachable. Running VM's was well with Br0 enabled. Not sure if this has anything to do with it.

Managed to get it going with 1) ssh: docker exec -ti owncloud /bin/bash 2) sudo -u nobody php /var/www/owncloud/console.php files:scan <userid>

Owncloud is not syncing properly and i would like to provoke a rescan of all the files on the server. On the owncloud website i found it can be done by using one of the following commands: php console.php files:scan <user_id> #For rescanning a users file php console.php files:scan --all #For rescanning the files of all users Can anyone point me in the right direction on how to execute this in docker via ssh?

Spoke to soon... Patience is a virtue.. Now the entries are created

I have tried getting this to run with no avail. My config folder in my appdata folder remains empty. No entries are made during the install except creating a MariaDB folder. Tried connecting to the database with mysql workbench, but this also did workout for me.

Attached the log from the plex docker.... First log is the automatic start. Second log is when I stop the docker and start it again. No idea why it is logging Invalid response packet from host 192.168.1.100. This is my Windows 10 VM and has no interaction with Plex whatsoever. Log.txt Log_after_stop_start.txt

The problem was indeed having both vnc with an additional GPU. Removed VNC and all is working. As for the original post, i am still having the Uefi boot problem. But hey, got everything working with Seabios.

Sure no problem: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows_Test</name> <uuid>68577d45-f921-15a7-ccdc-f7583935e647</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/vmdata/Windows_Test/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:38:60:b2'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows_Test.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.0,multifunction=on'/> </qemu:commandline> </domain>

Re installed and the issue persist. Only when i manual restart the docker plex will start. This is only needed after unraid is rebooted. Once plex is up and running (after a manual plex restart)i can start stop without issues.

Yup.. A week ago or so. Kept the config directory

The docker image location is /mnt/disks/appdata/docker.img Config location is /mnt/disks/appdata/plexmediaserver

Did not have this problem when using needo's plex... And my other dockers startup normal

When UNRAID is rebooted Plex will not start. Only once I manually reset Plex it start up properly. The log shows: setuser: cannot execute /usr/sbin/start_pms: [Errno 2] No such file or directory The config directory is located on a separate share outside the array using unassigned devices. Maybe it has a correlation. I am using plexpass...

Got a step further... in addition to my GPU, also a generic display adapter shows up under the device manager, although I am not passing anything through besides my GTX. When I disable the generic display adapter and reboot, the GPU goes from an error 43 to error 12: this device can find enough free resources ?! Anyone a clue how to resolve this? I disables as much as I can under hardware. The only options I had was to disable the cd-roms... Problem status is reporting: Conflicting Address Range. The specified address range conflicts with the address space.

OK I'll probably also have a better bed staying with SEABIOS for now.... As JONP suggested I put the Hyper-V back on and at least it is booting again into window using SEABIOS. One step closer ;-) But I am back to square one on the 43 error of the video card, which now has the latest drivers.