Stupifier

Very true. Recent developments on rclone-beta have greatly improved rclone. It is much quicker and more efficient. Hope to see Unraid rclone-beta see an update soon

A bunch of people here seemed to be complaining about rclone and google photos support.........Well, its supported in latest version. Dunno if/when Unraid rclone beta plugin will pick it all up. type rclone --version to figure out which version you're on.

Just typo this into Terminal on unraid to find the location of the rclone.conf file: rclone config file

You're welcome and don't worry.....your problem is WAYYY too common. Almost every other post is about something similar to this. Everyone seems to want to use rclone that way and it just doesn't work like that.

So you are doing two things wrong: You mounted an rclone remote and want to write to that mount. I'll just link you to my post dated just over a week ago for ya. Don't write to rclone mounts...instead write to the rclone remote. You are using rclone copy/sync as you should for writing into your cloud storage location....BUT.....the location you gave is where you mounted your rclone cloud storage. Instead, use your remote for the destination. For example in `rclone config` if you setup your rclone remote with the name "google_drive"....Then this would be a simple sync command: rclone sync /mnt/user/Data/Media/Bilder google_drive:Media/Bilder/ -vP -v for Verbose logs.....so you can see wtf is going on -P just to show live progress..... If you don't like doing it this way...the alternative is to use GDFS (Google FileStream).....it is more reliable for writing directly to a local filesystem location where a cloud storage is mounted onto. rclone documentation REALLY needs to make this point clear to people.....because everyone is making this mistake. Everyone just wants to mount their cloud storage, then start writing to it easily....It sort of works...but it is just NOT reliable and you'll just get a crap experience.

This is the TBW for my SSD cache drive. Is this OKAY? Samsung 850 EVO 500 GB 18 months Usage Holds all Appdata permanently Holds incoming data until 80% capacity...then mover started sudo /usr/sbin/smartctl -A /dev/sdb | awk '$0~/LBAs/{ printf "TBW %.1f\n", $10 * 512 / 1024^4 }' TBW 47.7

The general wisdom is that rclone mounts are NOT reliable for writes and should only be used for reads. That is not to say that ALL writes to an rclone mount will fail....I'm just saying you will have an inconsistent write experience. Sometimes it will work but more often than not, it will not work. If you need to put something onto cloud storage, use rclone copy/sync commands OR use Google Drive File stream aka GDFS (for Google Drive storage only of course).

Ya.....You're on the right track.....Just go down the rabbit hole with that and experiment. I glanced at it but I'm not much of a coder. Post up if you figure out an easy way to fire a command if rclone success/fail.

Mmmm... There is no option in rclone for anything like that.... But you can use an rclone flag to log output to a file.... And probably figure out a bash script to notify via webhook whatever you want when your rclone command finishes with a specific EXIT signal/code. And then just tail the last couple lines of the log file along with your webhook so you can quickly see if rclone sync succeeded or not. Here's just an example of something I quickly pulled out from github. I modified it slightly to make it easier. source #!/bin/bash ####################### #INPUT VARIABLES ####################### $source= $destination= $maxtransfer= $rcloneflags= $logfile= ####################### #INPUT VARIABLES ####################### rclone sync $source $destination\ --drive-server-side-across-configs\ --max-transfer $maxtransfer\ --fast-list --size-only -vP --stats 5s\ --tpslimit 4 --tpslimit-burst 20 --max-backlog 1000000\ --stats-file-name-length 0 $rcloneflags\ --log-file="$logfile"\ echo;echo FINISHED sync from $source to $destination;echo #Sends a Notification to my phone via Join App for Android wget -q "https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush?deviceNames=Phone&text=rclone_sync_complete&apikey=my_secret_key" > /dev/null

Nobody likes/wants to reboot their unRAID...but yes, that would work too.

Ok.....straight up. I don't experience any of these issues. My rclone beta updates on UnRAID just fine. So I'll just outline what I do: Use the rclone-beta plugin (not docker or anything else) I use rclone mount commands in scripts with userscripts plugin. You click "run in background" with these scripts. When I want to stop rclone....all I ever do is run below command.....the path is wherever your rclone mount is mounted to You can verify rclone is killed by just searching through htop on terminal Then you can update the rclone-beta plugin....and it WILL update. I've never ever had an issue with this. umount -l /mnt/disks/google I'm running the very latest rclone beta....I just did this and it worked just fine. Frankly, my rclone-beta plugin updates automatically for me along with the rest of my plugins. I have no idea why you all are having these issues.

Did you read the link the prompt recommends for Amazon? I'll include it again for you. It explains your problem up front in the "important section" https://rclone.org/amazonclouddrive/

To get log file just include this in your rclone command --log-file /path/to/logfile/log_filename.txt.... Just like the documentation says..."string" just means the path and filename of wherever you want the log to output to. And don't forget to use a -v...... AND your when you use log file flag, your command info will ONLY go to the log file and not be displayed live in terminal window. If you run any command in terminal, the command will STOP if you close the terminal window.

Look into the log output file flag in rclone documentation. Just log your output to a file and use tail -f terminal command to see what's been happening anytime you wanna check

Glad I could help.......It was frustrating me too.

Ok, I used to be able to connect to Host network with this before the update....that allowed me to be assigned an IP on my WiFi subnet, which then allowed me to access the UnRAID GUI interface. NOW, instructions make us connect to Bridge network......so how do we access the UnRAID GUI interface if we are on the bridge network? OpenVPN dished me out a 172.27.xxx.xxx address (docker subnet). Update: Figured out how to access UnRAID GUI. Did NOT figure out how to be assigned a local address on my primary WiFi subnet though. In Admin Page ----> VPN Settings go to Routing section and add a line for the subnet you want your clients to have access to (for example, I added 192.168.1.0/24 which is my primary WiFi subnet and where I can access my UnRAID GUI locally)

For whatever reason.....my 6.7.0 update Went just fine and I use Marvell SATA controller. Seems like the issue is hit or miss depending on the version/type of Marvell Controller you have.

Regarding the Marvell Controller issues: I have Marvell controller and updated from 6.6.1 ----> 6.7.0 without any issue. Boots fine, Array Starts fine, posting this message on my Win10 VM. This is the Marvell Controller I use. IOMMU group 20: [1b4b:9172] 05:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) IOMMU group 21: [1b4b:9172] 06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) IOMMU group 22: [1b4b:9172] 07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)

If both Source and Destination locations are LOCAL (not remotes/cloud locations).....then colon and stuff before it is not needed in the path. Everything before the colon is in reference to the name of the remote (as you configured in "rclone config"). With that said, re-read my previous post with examples. Sorry, but I can't explain much further on this. It's best to just run commands, observe result, and learn that way.

Examples below. I just threw these together in a couple minutes to show you. I don't use any of these. Sync will delete files on destination if they do NOT match source. If you change sync to copy.....then files in destination will NOT be deleted. This is all in the rclone documentation. I believe examples are there as well. this will sync a local folder on unraid (specifically, the share named "my_documents_share") to a remote named "gdrive" I setup using "rclone config". "gdrive" is a remote I setup that is pointing to my Google Drive account. --ignore existing just makes sure to skip over files that are already synced and -v gives verbose output so you can follow along with what's going on.. Also notice the remote: nomenclature is only required when the source or destination is an actual remote location (like cloud storage). rclone sync "/mnt/user/my_documents_share/" "gdrive:backup/my_documents_share/" --ignore-existing -v This will sync a folder in the remote "gdrive" to another remote "gdrive2". "gdrive2" is just another remote setup in "rclone config". It could point to a specific folder inside your Google Drive account, it could point to an entirely different Google Drive account altogether. Notice here, both source and destination are remotes.....This means we are just syncing data across two different cloud storage locations. In other words, nothing is being synced locally at all. Also, notice --bwlimit 5M just limits how much bandwidth this sync will consume....so you don't saturate your connection. Here I set it to 5 MB/sec. rclone sync "gdrive:backup/my_documents_share/" "gdrive2:backup/my_documents_share/" --ignore-existing -v --bwlimit 5M This is a simple command to just see the directories listed in the remote named "gdrive". Just an easy way to see what directories you have in there. You can use a depth flag (can't remember exact wording for it) if you want it to list folders deeper then the top-level. rclone lsd gdrive:

Source: and Destination: are remotes......type "rclone config" in terminal Shell to see a list of your current remotes, edit, and add new ones. You're doing good if you are reading on rclone site. Learn about rclone copy,move,lsf,lsd, and more. Also look into the the various flags (especially --ignore-existing, -v, and others)

You need to learn how to use the Terminal Shell. Again, writing to an rclone mount is NOT reliable. It does not matter if you write to the mount folder directly or via the union folder, it is NOT reliable. STOP EXPECTING IT TO BE. Instead, if you MUST write to you Google Drive, use rclone copy/sync commands via terminal shell. You're only limited to krusader because you are unwilling to LEARN. Put in the time, and learn how to use rclone properly. If you are unwilling to learn how to use Terminal Shell rclone commands, then you should just stop using rclone and seek alternatives. If you Google search, you can even find people who wrote scripts to monitor your union folder and automatically fire off terminal Shell rclone uploads for you. Cloudplow is one of those tools. But you have to be willing to learn how to use it

You are writing data to your Google drive account all wrong.....That's why! rclone mounts are HORRIBLE to write to and really should ONLY he used to read data from. Instead, if you MUST write to you Google Drive, use rclone copy/sync commands via terminal shell

Thought I'd just mention......zsh is in the unraid NerdPack plugin......that is probably the easiest way to install zsh and have it persist through reboots. If you haven't used NerdPack plugin, I'd suggest looking into it. Makes installing various tools and have them persist extremely easy Edit: Apologies.....you referring to Oh-My-Zsh.....

Posting to promote/upvote a feature-request: Would be nice to have the Appdata Backup separate the tar into individual tars for each app or primary folder instead of one gigantic tar.