Different results on two Windows machines

Help and Support
1

What is the problem you are having with rclone?

Different results on two Windows machines.
Use the node.js packaged exe to execute the rclone command to mount the disk, one of which maps normally, but the other does not map out of the disk, because it does generate the cache folder in the command.
Is there any difference between the environments of the two machines in this situation?
The manual execution of the abnormal machine can be mapped correctly, and the execution of the node development environment can also be mapped properly, but it cannot be properly mapped when packaged into exe.
I use the spawn () function of node.js to execute the rclone mount command.

Run the command 'rclone version' and share the full output of the command.

rclone v1.66.0

  • os/version: Microsoft Windows 11 Home 23H2 (64 bit)
  • os/kernel: 10.0.22631.3593 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: cmount

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

S3

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

rclone mount name:name/ X: --cache-dir ./rclone_cache --vfs-cache-mode minimal --dir-cache-time 2s --no-check-certificate

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[name]
type = s3
provider = Other
env_auth = false
endpoint = http://myserver
acl = private
storage_class = Standard
2

Another proof that the rclone command is executed correctly is that I do not kill the previous rclone process (although it is not mapped to disk). If I execute the command again, I will get an error: Fatal error: failed to mount FUSE fs: mountpoint path already exists: X:

3

hard to know what is going on, as no debug logs were posted.

then this does not look like a rclone issue.

no way for us to know that.

that should be storage_class = STANDARD

4

Thank you for your response. It's actually just a simple mount, but when I run the mount command with a node.js child process everything works fine, but after packing it into an exe the rclone process runs fine but doesn't map the disk.
This really has nothing to do with rclone as the execution works fine in all other cases, so I'm assuming that some difference before and after the packaging is causing the processes to execute in different environments, but it's causing me a lot of frustration.
I have observed a possible problem. Exe seems to execute rclone commands on the old cmd command line. I wonder if there will be any incompatibility with rclone?
Sorry for taking up your time!

5

I have the latest development. I have only one account on my computer, that is, the administrator. Everything is fine when I perform the mount manually, but I can't see the disk when I execute as an administrator, and the execution of rclone is normal.
Is there a problem with the permissions of my local account?

6

really doubt that is true.

rclone docs are clear about this:
Drives created as Administrator are not visible to other accounts

to better understand the issue, can try the following.

  1. run rclone mount name:name x:
  2. open two command prompts, one with admin privileges, one without admin privileges
  3. for each command prompt, run dir x:, are the files displayed?
  4. are the files diplayed in windows explorer?

one possible workaround, which is what i alway do, is to mount to a folder.
rclone mount name:name c:\path\to\folder

7

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