Hawkins

Watch state: I don't think it does. The watch state is stored in a SQLite database. You can read more about it here. Repulling metadata: Correct, but that is simply a matter of time. Backing up Plex's entire directory takes me a little under an hour and eats many 10's of GB of disk space. That means all containers are down, there is extra wear/tear on my disks, and I am backing up data that is neither unique nor user-created. I can simply have Plex pull all that data down again should I need it. Manually or automatically? If manually: cp <destination_directory_configured_in_plugin>\<name_of_backup_file> <location_to_keep_second_backup> If automatically, create a script with all the cp commands you need and run it automatically using either cron on a script-running plugin. Hear, hear! I already offered, now I am offering again. PayPal? Venmo? Charitable donation to a cause you feel strongly about?

I can help here. Open the unRAID terminal and go to your backup Destination Share: cd <Destination_Share> Find the backup you are looking for: ls Go into the directory of the backup you want to restore from: cd <backup_directory> Find the backup file you are looking for. In my example I am looking for <any>swag<any>: ls *swag* [Used only for demo purposes, don't do this.] I created a temp directory that I'll later delete: mkdir /mnt/cache/appdata/_testing_ Extract the backup file from step 4 into your appdata directory [I used my temp directory.]: tar -zxvf <backup_filename> -C /mnt/cache/appdata/

Just type them in here, each separated by a comma: As for what to type in that field, I use QDirStat running in a Docker container to figure out where the large (in file size and in file count) directories are. I think it would be *stellar* to see that kind of visibility within the backup plugin itself. Something like this: Now you can see why I picked to exclude these directories. I second this! I've been bitten by the 'days old' setting before. If you configure it to backup every n days and you set the 'days old' setting to a number less than n, I believe it will delete your previous backups (all of them!). I think it would be great to have setting like, "keep 3 backs minimum, regardless of age, and 6 backups maximum".

Excellent work. My backups are much, much faster now that plex's and radarr's metadata are excluded: root@Rack:/mnt/user/backups/Community_Applications/Backups/Appdata_Backup# du -h --max-depth=1 && ls -lh 2022-12-05\@09.56/CA_backup_plex.tar.gz && ls -lh 2022-12-05\@11.16/CA_backup_plex.tar.gz 13G ./[email protected] 94G ./[email protected] 105G ./[email protected] 105G ./[email protected] 94G ./[email protected] 409G . -rw-r--r-- 1 root root 77G Dec 5 10:44 2022-12-05\@09.56/CA_backup_plex.tar.gz -rw-r--r-- 1 root root 3.8G Dec 5 11:25 2022-12-05\@11.16/CA_backup_plex.tar.gz root@Rack:/mnt/user/backups/Community_Applications/Backups/Appdata_Backup# The 94G and 105G backups are from me testing the (at the time) broken exclude feature both with (94G) and without (105G) compression. The archive for plex dropped from 77G compressed to just 3.8GB compressed! For anyone interested, I exclude: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Cache/, /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Media/, /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Metadata/, /mnt/user/appdata/radarr/MediaCover/

Dang it, just confirmed the same on my end. I was going off what I had read earlier in this thread. I am sure @KluthR will figure it out.

Try changing the exclude paths from /mnt/user/appdata/foo/bar/ to /mnt/cache/appdata/foo/bar/. This isn't a permanent fix in my opinion, but I believe it will work until the developer can figure it out. Speaking of that, @KluthR, you're a rockstar. Thanks for the hard work! I am having the same issue and I wanted to see what you thought about it. Also, what is the best way to buy you a few beers?

Done.

No luck with a wipe/reinstall of the container. Also killed the appdata directory, made no difference. Both containers are on the same network type (proxy network for SWAG). Interested in some live troubleshooting this week?

RE: Cachet When starting Cachet I get the following error: Initializing Cachet container ... Attempting to connect to database ... ........................................................... Could not connect to database server! Aborting... I am using MariaDB in Docker, and it is known to be working prior to Cachet. Login below uses the password via copy/paste from the Cachet Docker config screen in unRAID so there are no typos: root@0c2f1410a349:/# mysql -u cachet -p Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 70 Server version: 10.4.18-MariaDB-1:10.4.18+maria~bionic-log mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | cachet | | information_schema | +--------------------+ 2 rows in set (0.001 sec) MariaDB [(none)]> use cachet Database changed MariaDB [cachet]> show tables; Empty set (0.000 sec) MariaDB [cachet]> Here is the relevant data from the Cachet config: Proof that IP and port are correct: Error when starting Cachet: I feel like I am missing something simple here.

This might prove useful to those unable to get Big Sur downloaded and running: https://github.com/munki/macadmin-scripts/blob/main/installinstallmacos.py This script can download the Big Sur install image: Product ID Version Build Date Title 001-86606 11.1 20C69 2020-12-14 macOS Big Sur That install file is 12.22 GB when completely downloaded, and you'll need to download a copy and then convert it (the script does this for you) so you'll need about 25GB of free space.

Squid to the rescue again.

+1 I'd love to see this feature. I could make a group for Plex, game servers, metrics, books, etc.

Please be more specific. Which plugin? What are your install steps? What error are you getting?

[SOLVED] It turns out the nVidia error that the driver wasn't compatible with this version of Windows was accurate. I was running built 10240 which was the first release of WIndows 10. I really need to delete my old ISOs. Once I upgraded to Windows 10 Pro version 1909, the graphics driver installed and ran with issue. I still have a few items in my device manager that need to be fixed, but my main issue, GPU passthough, is resolved. FYI, Microsoft makes it hard to get an ISO of 1909. Easy to get around, try this Google search: https://www.google.com/search?q="index+of"+Win10_1909_English_x64.iso

Here is the functional VM XML prior to testdasi's recommend changes. Note that Windows 10 Pro boots, has video, sound works, keyboard & mouse are good, etc. It appears that only video is an issue. The screenshots at start of thread are based on this config: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Desktop-Jesse</name> <uuid>ddfe75d2-246d-6755-757f-21297e0dfafa</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>24</vcpu> <cputune> <vcpupin vcpu='0' cpuset='12'/> <vcpupin vcpu='1' cpuset='36'/> <vcpupin vcpu='2' cpuset='13'/> <vcpupin vcpu='3' cpuset='37'/> <vcpupin vcpu='4' cpuset='14'/> <vcpupin vcpu='5' cpuset='38'/> <vcpupin vcpu='6' cpuset='15'/> <vcpupin vcpu='7' cpuset='39'/> <vcpupin vcpu='8' cpuset='16'/> <vcpupin vcpu='9' cpuset='40'/> <vcpupin vcpu='10' cpuset='17'/> <vcpupin vcpu='11' cpuset='41'/> <vcpupin vcpu='12' cpuset='18'/> <vcpupin vcpu='13' cpuset='42'/> <vcpupin vcpu='14' cpuset='19'/> <vcpupin vcpu='15' cpuset='43'/> <vcpupin vcpu='16' cpuset='20'/> <vcpupin vcpu='17' cpuset='44'/> <vcpupin vcpu='18' cpuset='21'/> <vcpupin vcpu='19' cpuset='45'/> <vcpupin vcpu='20' cpuset='22'/> <vcpupin vcpu='21' cpuset='46'/> <vcpupin vcpu='22' cpuset='23'/> <vcpupin vcpu='23' cpuset='47'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='24' 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/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Desktop-Jesse/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/en_windows_10_multiple_editions_x64_dvd_6846432.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x10'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:a5:00:bd'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Desktop-Jesse/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/MSI.RTX2070Super.8192.190701-FactoryNoHeader.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I used your email signature, hope you don't mind. I took screenshots because I was short on time when I gathered all that data. I'll spend the time now to get you the data you are asking for. In the mean time I'll address the other questions. I get this from the 442.19 Windows 10 64-bit Game Ready Driver (GRD) and Studio Driver (SD) installers: If I stop at this point of the install, which is before the extracted files are deleted from C:\NVIDIA\, I can go to Device Manager and point each device with an issue to the path containing the .inf files. No success from either driver pack, or on any of the 4 devices with issues. Yes it is the only GPU in the systems. Installed in the slot closest the CPU. The BIOS came from TechPowerUp and appears to be a perfect model match based on the description from that site. I've debated dumping my own and then pulling the header off. <vendor_id state='on' value='0123456789ab'/> While I give this a try, can you tell me what this is doing?

At time of posting, the display works, and I can use Windows, but the resolution is terrible x aweful and the nVidia drivers will not install. Things I've tried that haven't yet solved the problem, however I am certain that I have not tried every one of the ~14^2 possible combinations. Q35 vs i440fx SeaBIOS vs OVMF Enable vs disable Hyper-V extension GPU passthrough without BIOS (no display output) as well as with either the same-model factory BIOS or modified BIOS, both with and without the nVidia header pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 Various combinations of BIOS settings: SR-IOV Enabled/Disabled IOMMU Auto/Enabled PCIe ARI Support Enabled/Disabled Enable AER Cap Enable/Disabled (Enabled prevented VM from starting) ACS Enable Enabled/Disabled (Requires that Enable AER Cap be Enabled) Things that I already account for: All four devices associated with my GPU are stubbed via vfio-pci.ids= All four devices (one display, one sound, and two "other") are passed through to VM VM's XML is edited to put all 4 GPU devices into one slot with multimode enabled and functions numbered to match source hardware Has anyone struggled with this before? I'm happy to provide any log files, config files, or screenshots. Thanks in advance! Device Manager 01 https://i.imgur.com/riJoNcR.jpg VM Config 02 https://i.imgur.com/CnvxQMJ.jpg 03 https://i.imgur.com/uetUDyn.jpg VM XML 04 https://i.imgur.com/cjDrYtn.jpg Kernel 05 https://i.imgur.com/27jajNP.jpg IOMMU 06 https://i.imgur.com/SVIc3sm.jpg 07 https://i.imgur.com/8anUXQS.jpg 08 https://i.imgur.com/Fm8EjJO.jpg 09 https://i.imgur.com/6VhCiuy.jpg 10 https://i.imgur.com/lQaKnyb.jpg Hardware IDs 11 https://i.imgur.com/W88cK9q.jpg

Running this container via unRAID. No issues until i upgraded unRAID to latest 6.5 stable release tonight. All docker containers are fine except Lidarr. Starts with : root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='lidarr' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8004:8686/tcp' -v '/mnt/user/incoming/complete/music/':'/data':'rw' -v '/mnt/user/media/music/':'/media':'rw' -v '/mnt/user/appdata/lidarr':'/config':'rw' 'binhex/arch-lidarr' Log: 2018-03-17 00:09:17.989262 [info] Host is running unRAID 2018-03-17 00:09:18.026926 [info] System information Linux 561862a36433 4.14.26-unRAID #1 SMP PREEMPT Mon Mar 12 16:21:20 PDT 2018 x86_64 GNU/Linux 2018-03-17 00:09:18.071579 [info] PUID defined as '99' 2018-03-17 00:09:18.118826 [info] PGID defined as '100' 2018-03-17 00:09:18.359515 [info] UMASK defined as '000' 2018-03-17 00:09:18.402730 [info] Permissions already set for volume mappings chown: cannot access '/var/lib/lidarr': No such file or directory Blew away the container twice, including the files in /mnt/user/appdata/lidarr:/config. Anyone else getting this?

[SOLVED] I couldn't get the official plex docker container or limetech's to update to beta Plex Pass builds until I did this: Please test and report back, let me know if this solves anyone's problem.

Can't seem to get around this error: Fri Jan 26 12:25:24 2018 ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2) Fri Jan 26 12:25:24 2018 Exiting due to fatal error I am running this on Ubuntu 17.10 via Docker 17.12.0-ce. I have several other docker containers running without issue, including binhex/arch-sabnzbdvpn w/ working privoxy. One thing I've done out of the ordinary is running sudo /sbin/modprobe iptable_mangle as directed in previous logs however, I don't really understand what that did, or if it persists between reboots. I added the image in question to docker via this command: docker run -d \ --cap-add=NET_ADMIN \ -p 8088:9080 \ -p 8089:9443 \ -p 8090:8118 \ -p 8091:3000 \ --name=rtorrent_vpn \ -v /opt/docker_incoming_downloads:/data \ -v /opt/docker_config_files/rtorrent_vpn:/config \ -v /etc/localtime:/etc/localtime:ro \ -e TZ=America/Los_Angeles \ -e VPN_ENABLED=yes \ -e VPN_USER=p####### \ -e VPN_PASS=shhhhhhhhhhhh_its_a_secret \ -e VPN_PROV=pia \ -e STRICT_PORT_FORWARD=yes \ -e ENABLE_PRIVOXY=yes \ -e ENABLE_FLOOD=yes \ -e ENABLE_AUTODL_IRSSI=yes \ -e LAN_NETWORK=10.0.0.0/24 \ -e NAME_SERVERS=8.8.8.8,8.8.4.4 \ -e DEBUG=true \ -e PHP_TZ=America/Los_Angeles \ -e UMASK=000 \ -e PGID=1000 -e PUID=1000 \ binhex/arch-rtorrentvpn Supervisord.log attached as directed. Thanks for your continued hard work on this and other projects. Hey binhex, might I ask what your day-to-day job is? supervisord.log UPDATE: [SOLVED] Adding the line --device=/dev/net/tun to the run command fixed the problem. Any clue why?