Google Drive, Plex, Windows 10

VBB command uses flag --timeout 10m

if you look at your command's timestamps, the command timed-out after 10 minutes - 23:58 to 00:08

change the flag to --timeout=0 to disable a timeout period.
run the command again.

Hmm, that is odd, unless he has even more data than I have. I recently started using the timeout flag, because my priming started taking longer than the default would allow. You could remove the flag entirely and see if it makes a difference. Just to be sure, your mount is up while you're running the prime.bat?

yes, i noticed that you added that flag, as i do not remember it from your posts.

i would not remove the flag, as The default is 5m. Set to 0 to disable.

I started having an issue after updating to the latest beta one day, and Nick recommended using the timeout flag. That fixed my problem. You could set it to an hour even, and it wouldn't make a difference, if your prime command connected properly. But in OP's case it's not connecting, so it simply times out after 10 minutes.

good point but based on docs, not sure that is correct.
If a transfer has started but then becomes idle for this long it is considered broken and disconnected

so the transfer/process can start, but if the command does not finish in x minutes, then it is considered a failed command.

to know, the OP should make sure the mount command is working.
then run the command with --timeout=0, wait and see what happens.

if the mount is not running or the refresh command cannot connect, it fails immediately .
Failed to rc: connection failed: Post "http://localhost:5572/vfs/refresh": dial tcp connectex: No connection could be made because the target machine actively refused it

Right, that's why I was wondering if he had even more data, so the command would take even longer to finish. Disabling the timeout or setting it to a really high number should take care of it, but of course only if RC is working properly. We'll have to wait for OP to respond :slight_smile:


yep mount is running whilst i do this, i have about 400tb plus of data so could probably take some time i have now set it off so with --timeout 0m we shall see if it finishes

it completed just took 32mins

so now stream start takes between 11 and 19 seconds to start is there a way to speed this up?

32 minutes is way too long for priming, even with 400TB. To give you an idea, I prime 700TB (200,000 files and 36,000 folders) in roughly 3 minutes. Do you by any chance have considerably more files and folders? And like I mentioned before, my media starts in about 3 to 5 seconds.

I can't think of anything to make a Windows mount faster at this point, to be honest. Are you running all this locally? I run Plex on a dedicated server far away from where I live, and I use a mount and Windows Explorer combo for media playback at home.

Yep all this is running locally and no I don't have anymore than that

And Google drive filestream
All start within a couple of seconds

This all seems an rclone issue just gotta figure it out

can you do a and post the results.

not as fast as it should be at the minute as plex is currently scanning stuff in

can run this command
netsh interface tcp show global

Any conclusion to this thread? I'm having some stuttering issues with Gdrive, Plex, Windows 10 and was looking at this thread for inspiration.

you have not provided any information.
if you had started a new post you would have been asked for

What is the problem you are having with rclone?

What is your rclone version (output from rclone version)

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Which cloud storage system are you using? (eg Google Drive)

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Paste command here

The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Paste  log here

I didn't want to hijack the thread with my issue. Just trying to do my own research and troubleshooting before starting a new thread.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.