Alibaba OSS mounted but not showing in the Windows Disk Management

What is the problem you are having with rclone?

I'm trying to mount Alibaba OSS on Windows Server 2019, it's successfully mounted but the Z drive doesn't show in the Windows Disk Management

it's successfully mounted to drive Z

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

rclone --version
rclone v1.69.1

  • os/version: Microsoft Windows Server 2019 Datacenter 1809 (64 bit)
  • os/kernel: 10.0.17763.7009 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.24.0
  • go/linking: static
  • go/tags: cmount
yes

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

Alibaba OSS

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

Paste command here

rclone mount oss-disk:/media Z: --cache-dir D:\disk-cache --vfs-cache-mode writes --no-console

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

Paste config here

A log from the command that you were trying to run with the -vv flag

Paste  log here

C:\Users\Administrator>rclone mount oss-disk:/vss-media Z: --cache-dir D:\disk-cache --vfs-cache-mode writes -vv
2025/03/20 08:06:11 DEBUG : rclone: Version "v1.69.1" starting with parameters ["rclone" "mount" "oss-disk:/vss-media" "Z:" "--cache-dir" "D:\disk-cache" "--vfs-cache-mode" "writes" "-vv"]
2025/03/20 08:06:11 DEBUG : Creating backend with remote "oss-disk:/vss-media"
2025/03/20 08:06:11 DEBUG : Using RCLONE_CONFIG_PASS password.
2025/03/20 08:06:11 DEBUG : Using config file from "C:\Users\Administrator\AppData\Roaming\rclone\rclone.conf"
2025/03/20 08:06:11 DEBUG : fs cache: renaming cache item "oss-disk:/vss-media" to be canonical "oss-disk:vss-media"
2025/03/20 08:06:11 INFO : S3 bucket vss-media: poll-interval is not supported by this remote
2025/03/20 08:06:11 DEBUG : S3 bucket vss-media: vfs cache: root is "D:\disk-cache"
2025/03/20 08:06:11 DEBUG : S3 bucket vss-media: vfs cache: data root is "\\?\D:\disk-cache\vfs\oss-disk\vss-media"
2025/03/20 08:06:11 DEBUG : S3 bucket vss-media: vfs cache: metadata root is "\\?\D:\disk-cache\vfsMeta\oss-disk\vss-media"
2025/03/20 08:06:11 DEBUG : Creating backend with remote ":local,encoding='Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot',links=false:D:/disk-cache/vfs/oss-disk/vss-media"
2025/03/20 08:06:11 DEBUG : :local: detected overridden config - adding "{R5KD5}" suffix to name
2025/03/20 08:06:11 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot',links=false:D:/disk-cache/vfs/oss-disk/vss-media" to be canonical ":local{R5KD5}://?/D:/disk-cache/vfs/oss-disk/vss-media"
2025/03/20 08:06:11 DEBUG : Creating backend with remote ":local,encoding='Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot',links=false:D:/disk-cache/vfsMeta/oss-disk/vss-media"
2025/03/20 08:06:11 DEBUG : :local: detected overridden config - adding "{R5KD5}" suffix to name
2025/03/20 08:06:11 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot',links=false:D:/disk-cache/vfsMeta/oss-disk/vss-media" to be canonical ":local{R5KD5}://?/D:/disk-cache/vfsMeta/oss-disk/vss-media"
2025/03/20 08:06:11 INFO : S3 bucket vss-media: vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2025/03/20 08:06:11 DEBUG : Network mode mounting is disabled
2025/03/20 08:06:11 CRITICAL: Fatal error: failed to mount FUSE fs: mountpoint path already exists: Z:

welcome to the forum,

correct. the rclone mount is a virtual file system, not a virtual drive.
the mountpoint will not show

And what exactly is the problem you are trying to resolve? Maybe there are other ways than using Windows Disk Management.

Or is it only curiosity?

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