JibbsIsMe

You were exactly right! Subvolume is not a familiar term for me, if it said subfolder I might have understood better. I simply changed my path from /mnt/working to /mnt/working/swapfolder, and it worked!

Saving works now, but now I get the error: swapfile must not be copy-on-write I am trying to put it on a "Pool Device" named "working" by using /mnt/working. It is a single disk. I am thinking that this might break one of the limitations mentioned in the first post, but I'm not sure.

I have the same problem. Don't see anything useful in the logs, as far as I can tell. Clicking save just resets everything. Swap file is never marked in use, no matter what I do. Unraid 6.9.2. All I get in logs is: Jun 8 21:04:30 Tower emhttpd: cmd: /usr/local/emhttp/plugins/swapfile/scripts/rc.swapfile start Jun 8 21:04:30 Tower rc.swapfile[48338]: Creating swap file / please wait ... Jun 8 21:04:30 Tower rc.swapfile[48344]: Swap file / created and started

I love the flexibility. The ability to use any drive size, do add or remove whenever, to extend with plugins and docker containers, and so on. A feature I'd love is high availability, mentioned above. Basically when a docker container is down (as defined by a custom rule), restart it. Another great feature would be multiple cache pools.

I had the same issue. Lost access after the 6.8.0 RC1 update I did on Oct 12, and finally noticed it today. I had this error in my Unifi log file, and nothing else, for the past 18 days: [2019-10-12 13:46:15,023] <db-server> ERROR system - [exec] error, rc=134 Container logs showed nothing interesting. I was using the "Bridge" network mode. I ended up fixing it, but I'm not sure exactly what did it. I did a few things: Since the log was showing a db error, I did a MongoDB database repair with these instructions. This seemed to have no effect. Change network type from Bridge to Host, didn't work. Lots of container restarts and force updates. Following something I read here when investigating the big "sqlite corruption" issue a while back, I changed the config folder mapping from /mnt/user/appdata/unifi-controller to /mnt/cache/appdata/unifi-controller. I think this may have done it, but I don't want to break it again to check. I also changed from Host to br0, then back to Bridge. I don't think this did anything, but I did it at the same time as the previous. I don't have Wireguard set up, so it's probably not that.

I was having troubles installing this. I got this error: plugin: installing: https://raw.githubusercontent.com/Waseh/rclone-unraid/beta/plugin/rclone.plg plugin: downloading https://raw.githubusercontent.com/Waseh/rclone-unraid/beta/plugin/rclone.plg plugin: downloading: https://raw.githubusercontent.com/Waseh/rclone-unraid/beta/plugin/rclone.plg ... done +============================================================================== | Installing new package /boot/config/plugins/rclone-beta/install/rclone-2018.08.25-bundle.txz +============================================================================== Verifying package rclone-2018.08.25-bundle.txz. Installing package rclone-2018.08.25-bundle.txz: PACKAGE DESCRIPTION: Package rclone-2018.08.25-bundle.txz installed. Downloading rclone Downloading certs Download failed - No existing archive found - Try again later plugin: run failed: /bin/bash retval: 1 Updating Support Links Looking at the plugin script, the failing line was this: curl --connect-timeout 5 --retry 3 --retry-delay 2 --retry-max-time 30 -o /boot/config/plugins/&name;/install/rclone-&rcloneversion;.zip &rcloneurl; Which translates to this: curl --connect-timeout 5 --retry 3 --retry-delay 2 --retry-max-time 30 -o /boot/config/plugins/rclone-beta/install/rclone-beta-latest.zip https://beta.rclone.org/rclone-beta-latest-linux-amd64.zip Running that gave me a resolve timeout error: root@Tower:/boot/config/plugins/rclone-beta/install$ curl --connect-timeout 5 --retry 3 --retry-delay 2 --retry-max-time 30 -o rclone-beta-latest.zip https://beta.rclone.org/rclone-beta-latest-linux-amd64.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 Warning: Transient problem: timeout Will retry in 2 seconds. 3 retries left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 Warning: Transient problem: timeout Will retry in 2 seconds. 2 retries left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 Warning: Transient problem: timeout Will retry in 2 seconds. 1 retries left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0 curl: (28) Resolving timed out after 5000 milliseconds So I just bumped the timeout to 15 and the command ran fine: root@Tower:/boot/config/plugins/rclone-beta/install$ curl --connect-timeout 15 --retry 3 --retry-delay 2 --retry-max-time 30 -o rclone-beta-latest.zip https://beta.rclone.org/rclone-beta-latest-linux-amd64.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 9758k 100 9758k 0 0 1409k 0 0:00:06 0:00:06 --:--:-- 2184k root@Tower:/boot/config/plugins/rclone-beta/install$ ls rclone-2018.08.25-bundle.txz* rclone-beta-latest.zip* After that I was able to do the normal plugin install no problem. @Waseh - I think this would be good to update in the plugin script.

Is it possible to add an option that creates links within the "Tools" tab?