I filled out the fields below, but essentially I'm using an rclone mount command to create folders that show on my local C drive. The PC this is running on blue screens quite a bit (a totally different story). I have a process that will see that it has blue screened, kill power, and restart the PC. I have a batch file built that runs in Task Scheduler at System Startup (batch file pasted in the "enter your command" section). When this happens, rclone won't mount the directories that I expect because they are already there. I need to manually delete the folders that are there, then rerun the Task Scheduler task and all is good. I thought perhaps in my batch file I could add a command to delete the folders first, then mount, but I was afraid that would run and accidentally delete the actual cloud drive.
What is the problem you are having with rclone?
When my Windows 10 PC is not shutdown properly, when the PC starts, the rclone folders already exist. This means when my rclone batch file runs to mount the folders, it fails to 'replace' or overwrite the folders.
What is your rclone version (output from rclone version)
rclone v1.54.0
os/arch: windows/amd64
go version: go1.15.7
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows 10, 64 bit
Which cloud storage system are you using? (eg Google Drive)
Google Drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
the location of the mount cannot be the same as the --cache-db-path
so try this and then look for the X:, to see the files. start rclone mount --vfs-cache-mode writes --cache-db-path "C:\Drive Files\X" --cache-chunk-path "D:\Rclone Cache" --cache-dir "D:\Rclone Cache" "DFS - X - Cache:/" X:"
My mistake, I edited my post. I had the --cache-db-path wrong in my post, but my config is not like that, the db is in the parent directory to where the mounts are made, and that directory is actually on the C:\ of the PC. I was trying to get around the "new user can only post two links" thinking that perhaps all the backslashes looked like links, so I manually edited too much.
I recall reading that the cache remote was not supported, but for some reason thought I needed it over the --vfs-cache-mode full. This is the software that I'm primarily using with these files: Constant access to the same file over and over again?. I can certainly change the mount command to skip the cache mount and see what happens.
Noted, I should have run the rclone command the last time the PC blue screened to get the output, but instead I deleted the leftover folders and reran my mount batch file to get the directories back first. I have my Task Scheduler logs off, so I don't think it outputs that data anywhere automatically.
Ah, ok. I didn't realize it couldn't be a subfolder either. I can certainly make that change and then go pull the plug on the PC to see if that works better when recovering from a blue screen. I'll do that and test it out right now.
I'm hesitant to move to the --vfs-cache-mode full simply because I recall reading quite a bit about the cache when I set this up a few months ago. I must have come to the conclusion I needed the cache filesystem for some reason, but if that conclusion is totally wrong, then I will adapt that as well. Thanks!
the problem has nothing to do with the BSOD.
really, whatever you do, do not pull the plug on a running system, that is a hard crash and can permanently corrupt the file system, which can lead to never ending BSOD over and over again.
so just run the command i shared on the command line, see the files in the X: drive, then kill the command, run it again and verify there are no errors.
Yes, that command works, as does the command that I have been using. The problem comes when I have to hard reset this PC. If the rclone process is stopped gracefully or by killing the task, it removes the C:\Drive Files\X folder/shortcut correctly. Then the next time I run the rclone mount command, everything is fine.
When the PC is hard reset, the C:\Drive Files\ looks like this on boot:
C:\Drive Files>dir
Volume in drive C has no label.
Volume Serial Number is
Directory of C:\Drive Files
03/29/2021 03:09 PM <DIR> .
03/29/2021 03:09 PM <DIR> ..
03/29/2021 03:08 PM 911 mount_dfs.bat
03/29/2021 03:08 PM <JUNCTION> X [\Device\Volume{UUID}\]
8 File(s) 148,899,182 bytes
6 Dir(s) 127,885,996,032 bytes free
C:\Drive Files>cd X
The system cannot find the path specified.
C:\Drive Files>
Then when I try to run the mount command with -vv, I get this:
C:\>rclone mount --vfs-cache-mode writes --cache-db-path "C:\rclone_db_path" --cache-chunk-path "D:\Rclone Cache" --cache-dir "D:\Rclone Cache" "DFS - X - Cache:/" "C:\Drive Files\X" -vv
2021/03/29 15:19:50 DEBUG : rclone: Version "v1.54.0" starting with parameters ["rclone" "mount" "--vfs-cache-mode" "writes" "--cache-db-path" "C:\\rclone_db_path" "--cache-chunk-path" "D:\\Rclone Cache" "--cache-dir" "D:\\Rclone Cache" "DFS - X - Cache:/" "C:\\Drive Files\\X" "-vv"]
2021/03/29 15:19:50 DEBUG : Creating backend with remote "DFS - X - Cache:/"
2021/03/29 15:19:50 DEBUG : Using config file from "C:\\Users\\x\\.config\\rclone\\rclone.conf"
2021/03/29 15:19:50 DEBUG : Creating backend with remote "DFS - X:/"
2021/03/29 15:19:50 DEBUG : fs cache: renaming cache item "DFS - X:/" to be canonical "DFS - X:"
2021/03/29 15:19:50 DEBUG : DFS - X - Cache: wrapped DFS - X: at root
2021/03/29 15:19:50 INFO : DFS - X - Cache: Cache DB path: C:\ rclone_db_path\DFS - X - Cache.db
2021/03/29 15:19:50 INFO : DFS - X - Cache: Cache chunk path: D:\Rclone Cache\DFS - X - Cache
2021/03/29 15:19:50 INFO : DFS - X - Cache: Chunk Memory: true
2021/03/29 15:19:50 INFO : DFS - X - Cache: Chunk Size: 100M
2021/03/29 15:19:50 INFO : DFS - X - Cache: Chunk Total Size: 50G
2021/03/29 15:19:50 INFO : DFS - X - Cache: Chunk Clean Interval: 1m0s
2021/03/29 15:19:50 INFO : DFS - X - Cache: Workers: 4
2021/03/29 15:19:50 INFO : DFS - X - Cache: File Age: 1h0m0s
2021/03/29 15:19:50 DEBUG : Adding path "cache/expire" to remote control registry
2021/03/29 15:19:50 DEBUG : Adding path "cache/stats" to remote control registry
2021/03/29 15:19:50 DEBUG : Adding path "cache/fetch" to remote control registry
2021/03/29 15:19:50 DEBUG : fs cache: renaming cache item "DFS - X - Cache:/" to be canonical "DFS - X - Cache:"
2021/03/29 15:19:50 DEBUG : Cache remote DFS - X - Cache:: subscribing to ChangeNotify
2021/03/29 15:19:50 DEBUG : vfs cache: root is "\\\\?\\D:\\Rclone Cache\\vfs\\DFS - X - Cache"
2021/03/29 15:19:50 DEBUG : vfs cache: metadata root is "\\\\?\\D:\\Rclone Cache\\vfs\\DFS - X - Cache"
2021/03/29 15:19:50 DEBUG : Creating backend with remote "\\\\?\\D:\\Rclone Cache\\vfs\\DFS - X - Cache"
2021/03/29 15:19:50 DEBUG : fs cache: renaming cache item "\\\\?\\D:\\Rclone Cache\\vfs\\DFS - X - Cache" to be canonical "//?/D:/Rclone Cache/vfs/DFS - X - Cache"
2021/03/29 15:19:50 DEBUG : fs cache: switching user supplied name "\\\\?\\D:\\Rclone Cache\\vfs\\DFS - X - Cache" for canonical name "//?/D:/Rclone Cache/vfs/DFS - X - Cache"
2021/03/29 15:19:50 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/03/29 15:19:50 DEBUG : Network mode mounting is disabled
2021/03/29 15:19:50 DEBUG : Mounting on "C:\\Drive Files\\X" ("DFS - X - Cache")
2021/03/29 15:19:50 DEBUG : Cache remote DFS - X - Cache:: Mounting with options: ["-o" "attr_timeout=1" "-o" "uid=-1" "-o" "gid=-1" "--FileSystemName=rclone" "-o" "volname=DFS - X - Cache"]
Cannot create WinFsp-FUSE file system: mount point in use.
2021/03/29 15:19:51 ERROR : Cache remote DFS - X - Cache:: Mount failed
2021/03/29 15:19:51 Fatal error: failed to mount FUSE fs: mount stopped before calling Init: mount failed
Is your point that I should use a straight drive, instead of a path (X: vs C:\Drive Files\X)?
If that solves my issue, then that's great - I simply wasn't understanding that from your posts. I would rather have it be within the C: path because I have roughly 10 team drives to mount on this PC and using descriptive folder names is easier to keep track of vs the letter mechanism that Windows uses for drives, but I can deal with that.
I added a new partition that's 1GB in size, and created a directory in that partition named rclone. That partition is now mounted as R:\. My mount command is now this:
I ran the command, see the files in R:\rclone\x, all good. To test if this would help in the event of an ungraceful shut down, I powered off the PC by killing the power. I then started it back up but I'm in the same place (the log file is practically identical to what I posted before).
Maybe I'm not going to find a solution to this, but I imagine anyone would have this problem if the power cuts out. When a PC comes back alive, how do I make sure that the rclone mounts work without my intervention? Thanks!
I'm pulling the plug to test it. But the same exact scenario would occur in the event of an unplanned power failure. My problem is that if the PC is not gracefully shut down, the rclone mount won't come back until I manually delete the prior created folder. I want a system that will recover correctly from an ungraceful shut down (whether it's a BSOD, me pulling the plug, or a rolling brown-out).
perhaps create a virtual machine and simulate a power outage.
in that way, you can test without permanently damaging the operating system that you depend on for testing.
create a snapshot before simulating the power outage.
after reboot, if the problem persists, then revert to the snapshot, tweak the mount command.
