DZMM

Can you post your mount script (haven't seen yet) and your upload script. Somewhere there's a path difference, or it doesn't like the dash in Plex-Media and you need to use an underscore.

Dunno - I was going to say after reading your logs that everything was 'working', so try a reboot. Sometimes when people are repeatedly mounting to debug the system seems to go a bit loopy.

LocalFilesShare="ignore" - looking at your unionfs script, shouldn't this be LocalFilesShare="/mnt/user/rclone_upload/google_vfs"?? Otherwise, looks fine and your files from gdrive_media_vfs: should be showing in the mergerfs mount. If still not working, post the logs

post your script logs

all looks fine - it even says it's overwritten the existing mountcheck file which is a good sign. When you say 'no files' - what are you using to look? post your mount scripts for both unionfs and mergerfs as there's something different in there.

You need to run the unmount script or manually delete the /mnt/cache/appdata/other/rclone/remotes/$RcloneRemoteName/dockers_started file - somehow you've got the scripts running slightly out of sync

For clarity, here's my flow: 1. Mount Tdrive_1, tdrive_2, tdrive_3 etc - do not create a mergerfs mount for tdrive_2 and upwards 2. Create a single mergerfs mount with local folder and the Tdrive_1 mount, tdrive_2 mount, tdrive_3 mount etc 3. Point plex, sonarr etc at the mergerfs mount 4. new files get added to the mergerfs mount's local folder 5. upload script moves ALL files from the local folder to tdrive_1 6. I looked at tdrive_1 and worked what the encrypted name was e.g. for TV_Shows adasfghertdfghthgdf 7. TV_shows should be in tdrive_2, so extra script runs overnight to move tdrive_1/crypt/adasfghertdfghthgdf to tdrive_2/crypt/adasfghertdfghthgdf 8. The move is done by rclone so it adjusts the tdrive_1 and tdrive_2 mounts in real-time, so in mergerfs mount files haven't 'moved' from /TV_Shows and everyone is happy

No, because rclone is moving the files - server side from tdrive_x-->tdrive_y, so it is aware of the change of location. Because both tdrive_x and tdrive_y are included in my expanded mergerfs mount, plex, sonarr etc aren't aware that the real location has moved - it's the same approach as for when files move from local to gdrive. Yes, and then use my extra script or similar to 'sort' the files server side into the right tdrives.

Have you installed the rclone plugin?

All looks good. The reason I do a tdrive-->tdrive transfer as an extra step, is because I only have one mergerfs mount that combines all my tdrives and local files. The upload script for the associated local folder uploads all the files to a single tdrive, so behind the scenes I move the files to their correct tdrive. You could run an upload script for each tdrive, but for my setup that be a pain to traffic manage and the tdrive-->tdrive transfers are mega fast as they are done server side.

When you say any docker, do you mean Krusader? Best practice is to start dockers after mounting.

lol I'd literally just grabbed the laptop to research seedboxes as I'd just had that idea!

Thanks I'll look again as I couldn't see any with HDDs and SSDs, just one or the other. I'm worried browsing will be slow from a HDD - but I guess you can't have it all.

Can anyone recommend a good, cheap dedicated server provider? I'm probably going to be moving home again and it's looking like I'll only get 110 upload at best, which will make running my Plex server on my machine very hard unless I do a lot of transcoding. I've looked at Hetzner's auctions, but most of their boxes are SSD only and I need a HDD to hold torrents that are seeding.

No - just make sure that the mount is running before starting dockers - in the docker settings set any docker that could add files to the mount, or go haywire if the mount files aren't available (e.g. plex) to not auto start.

Something is in the folder that is stopping mergerfs creating a mount Whatever docker you are using is creating a file(s) in the mount location - don't start dockers that add files to the mount outside the script!

Why did you delete the logs from your post? It's hard to help you without logs. Luckily, the logs are in the email alert I got. If you look at the logs it says, error mergerfs mountpoint not empty. Look at the mergerfs file location and delete or move whatever files are there and then run the script again.

you can use any rclone mount command - https://rclone.org/commands/rclone_mount/

Exactly - new remotes using different SAs

it's best to create new rclone remotes for the server side move i.e. don't use the ones you use for daily usage to avoid any API/transfer 24hr bans Edit: Another way is to use teamdrives and just move within gdrive on the web. Quick but any changes made might take a time to be seen by rclone, whereas the method above captures the new paths straightaway

No need for a script as long as your mounts have server_side_across_configs = true: [gdrive] type = drive client_id = xxxxxxxxxxxx client_secret = xxxxxxx scope = drive server_side_across_configs = true Actual command: rclone move gdrive1:Path_to_source_folder gdrive2:Path_to_destination_folder You can pick and choose some typical arguments: rclone move gdrive1:Path_to_source_folder gdrive2:Path_to_destination_folder --user-agent="transfer" \ -vv \ --buffer-size 512M \ --drive-chunk-size 512M \ --tpslimit 8 \ --checkers 8 \ --transfers 4 \ --order-by modtime,ascending \ --exclude *fuse_hidden* \ --exclude *_HIDDEN \ --exclude .recycle** \ --exclude .Recycle.Bin/** \ --exclude *.backup~* \ --exclude *.partial~* \ --drive-stop-on-upload-limit \ --delete-empty-src-dirs It all happens server side so mega fast. If you hit the 750GB/day limit, just run daily or create a service account rotation if you can't wait.

easiest way is to look at the upload script logs

Back then I was in a Gigaclear area and I was loving my 1000/1000 service. Now I only get 360/180, which is adequate. Now if you're really lucky, there are some providers in the UK who are offering 10000/10000 - one day we'll all get speeds like that!

It's all explained on my github

If you're using SAs you don't need APIs. If you're not, then unique client IDs is recommended