jude

I've switched it back to not cache only shares and its working well again. Sometimes its good to take the win rather than breaking it and dealing with the wrath of the family. I've also noticed that sometimes my dockers are not seeing the mount points properly and disabling the dockers from the main docker settings page and then re-enabling brings it back to where Plex and Sonarr can access the unionfs mount. This isn't specifically related to these scripts or the unionfs mount as I was starting to have this issue prior to this. Not sure if its an issue with the current rclone beta or the unraid RC or a combination.

Just wanted to thank @DZMM for all of you work putting this together. I was using a different setup but yours fixes some of the issues I was having (upload speed) and generally seems to work better. I haven't read all of the thread but I'm wondering if you have been able to set this up or switch it over to being cache only shares? I have it working properly following your guide but when I switched it over to cache only shares it didn't work. The mounting script would complete but there was nothing in the rclone or union mounts. I have a large fast SSD cache and wanted to limit activity to this. Any obvious reason why this doesn't work? Thanks

Looking at trying this versus the Plugin. When I run rclone version from the console it shows version 1.45 I have version v1.47.0-073-gcff85f0b-beta running using the Plugin. How do I pull the most recent beta from the Rclone-mount docker? I tried curl https://rclone.org/install.sh | sudo bash -s beta from within the Rclone docker console but it won't run as the container throws errors / # curl https://rclone.org/install.sh | sudo bash -s beta sh: curl: not found sh: sudo: not found

Thanks for that. Just in case someone else has this issue and to expand upon what @dmacias said. I had to go into Nerdtools and set it to download and install the pip package. Once that was done everything worked again. Thank you!

Thanks for the great tutorial and for all of the others you make. They really make it easy to get the most out of our unRaid boxes. I have a question regarding an error that I am getting when trying to back up photos/videos from my daughters iPhone to my server using NextCloud. Everything works well except for larger video files which wont upload and give a 413 error (request entity too large). I did some Googling and found this page https://github.com/nextcloud/docker/issues/261 which has a final post by @bhansley stating; "For anyone else who run across this issue, in addition to setting upload size in the Nextcloud UI, I had to tweak my upstream Nginx proxy to allow bigger uploads." client_max_body_size 10G; client_body_buffer_size 400M; Could someone direct me to where this upstream Nginx proxy config setting should go?

I'm having a basic setup issue. I was following the youtube setup guide made for this plugin https://www.youtube.com/watch?v=-b9Ow2iX2DQ and everything appears to work fine until I run the command to check if the encrypted folder has been created on the Amazon drive. The encrypted folder in this case named secure shows up in rclone (if I type in rclone config it shows the following) root@Tower:/# rclone config Current remotes: Name Type ==== ==== EncryptedACD crypt amazon amazon cloud drive secure crypt testfolder crypt (all of the crypt folders are me attempting to create a remote that actually includes a folder in the amazon drive) However if I type in rclone lsd amazon: I get the following root@Tower:/# rclone lsd amazon: -1 2016-11-19 09:46:59 -1 Plex Cloud Sync -1 2016-11-12 02:04:12 -1 Pictures -1 2016-11-12 02:04:12 -1 Videos -1 2016-11-12 02:04:12 -1 Documents -1 2017-05-03 18:50:10 -1 new I checked to see if rclone was able to create folders on amazon: by typing rclone mkdir amazon:new as you can see above this was successful. Not sure what I'm doing wrong here. Edit: by manually creating the encrypted folder using rclone and then mounting it, I was able to confirm that everything is working as it should.

Any chance you can point me to an up to date tutorial on how to set up ACD and rclone to work with your docker. Pretty basic requirements just want to use ACD as an archive drive for older media using a local Plex server. Thanks

OK that works thanks.

Having trouble getting your template to show up. I'm adding https://github.com/tynor88/docker-templates to the Docker repositories template section. After saving, I try to add a new container from the templates and yours don't show up. Not sure what I'm missing.

if you are using the ssd exclusively for the vm, i should passthrough the disk then install the os directly to the disk rather than use a vdisk I am also trying to get the best performance I can from a Win10 gaming VM on an SSD, accessed using Unassigned Devices. Currently I am using a vdisk but if the performance gains are significant then I would pass through the entire SSD. Are the gains significant? And what is the best practice for passing through the entire disk?

Thanks for all the hard work. Donated

If you do a search for plexpy in Community Apps, this does show up Thanks, found it! https://github.com/linuxserver/docker-templates

I am having some trouble getting this to install. I can handle installing Docker containers from templates. But as this doesn't have a template I am stuck. What are the required steps to add this container? Thanks

Thanks for the excellent guide. [sOLVED] Having a few problems passing through the controller however. I mapped out the ports as suggested. The ports I wish to pass through are all on Bus 4. The output of readlink # readlink /sys/bus/usb/devices/usb4 is ../../../devices/pci0000:00/0000:00:12.0/usb4 I have updated the XML and vfio bind. Connected usb keyboard (did not get power) and confirmed that it did not show up in lsusb. Using virsh to start the domain I get the following error. virsh # start windows81 error: Failed to start domain windows81 error: internal error: early end of file from monitor: possible problem: 2014-12-22T16:45:59.153076Z qemu-system-x86_64: -device vfio-pci,host=00:12.0,bus=root.1,addr=00.1: vfio: error, group 6 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2014-12-22T16:45:59.153139Z qemu-system-x86_64: -device vfio-pci,host=00:12.0,bus=root.1,addr=00.1: vfio: failed to get group 6 2014-12-22T16:45:59.153172Z qemu-system-x86_64: -device vfio-pci,host=00:12.0,bus=root.1,addr=00.1: Device initialization failed. 2014-12-22T16:45:59.153206Z qemu-system-x86_64: -device vfio-pci,host=00:12.0,bus=root.1,addr=00.1: Device 'vfio-pci' could not be initialized going back and entering lspci | grep USB I see 00:12.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.5 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:16.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:16.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 02:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01) 07:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01) I am guessing that I also have to vfio-bind 00:12.2 as well as 00:12.0 but when I do this by editing the XML file and vfio-bind I get the following virsh # start windows81 error: Failed to start domain windows81 error: internal error: early end of file from monitor: possible problem: 2014-12-22T16:57:26.634081Z qemu-system-x86_64: -device vfio-pci,host=00:12.2,bus=root.1,addr=00.1: PCI: slot 0 function 1 not available for vfio-pci, in use by vfio-pci 2014-12-22T16:57:26.634143Z qemu-system-x86_64: -device vfio-pci,host=00:12.2,bus=root.1,addr=00.1: Device initialization failed. 2014-12-22T16:57:26.634199Z qemu-system-x86_64: -device vfio-pci,host=00:12.2,bus=root.1,addr=00.1: Device 'vfio-pci' could not be initialized currently my XML file qemu section looks like this <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:12.0,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:12.2,bus=root.1,addr=00.1'/> </qemu:commandline> Not sure what I am doing wrong here. Help and thanks [sOLVED] Removed <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:12.2,bus=root.1,addr=00.1'/> from XML but left the Go file looking like this /usr/local/sbin/vfio-bind 0000:04:00.0 0000:04:00.1 0000:00:12.0 0000:00:12.2 The VM starts and the Microsoft all-in-one keyboard trackpad that would not work for more than a minute or so without stopping now works great and is not having any instability issues. I can plug other USB devices into any of the ports that belong to the USB controller and they work hot plug style. Thanks

+1 request for Logmein Hamachi