Mount Azure Blob as Network Drive

What is the problem you are having with rclone?

Not able to mount azure blob storage as network drive. No drive G or network drive showing in windows explorer

What is your rclone version (output from rclone version)

v1.53.0

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

Windows server 2016

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

Azure blob

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

rclone mount SIT_AzureBlobFS: G: --fuse-flag --VolumePrefix=\server\SIT -vv

The rclone config contents with secrets removed.

[SIT_AzureBlobFS]
type = azureblob
account = XXXXXXXXXXXXXXX
key = XXXXXXXXXXXXXXXXXXXXXXX

A log from the command with the -vv flag

F:\Tools\rclone>rclone mount SIT_AzureBlobFS: G: --fuse-flag --VolumePrefix=\server\SIT -vv
2020/09/15 11:52:38 DEBUG : rclone: Version "v1.53.0" starting with parameters ["rclone" "mount" "SIT_AzureBlobFS:" "G:" "--fuse-flag" "--VolumePrefix=\\server\\SIT" "-vv"]
2020/09/15 11:52:38 DEBUG : Creating backend with remote "SIT_AzureBlobFS:"
2020/09/15 11:52:38 DEBUG : Using config file from "C:\\Users\\XXXXXXXX\\.config\\rclone\\rclone.conf"
2020/09/15 11:52:38 INFO  : Azure root: poll-interval is not supported by this remote
2020/09/15 11:52:38 DEBUG : Azure root: Mounting on "G:"
2020/09/15 11:52:38 DEBUG : Azure root: Mounting with options: ["-o" "fsname=SIT_AzureBlobFS:" "-o" "subtype=rclone" "-o" "max_readahead=131072" "-o" "attr_timeout=1" "-o" "atomic_o_trunc" "-o" "uid=-1" "-o" "gid=-1" "--FileSystemName=rclone" "-o" "volname=SIT_AzureBlobFS" "--VolumePrefix=\\server\\SIT"]
2020/09/15 11:52:38 DEBUG : Azure root: Init:
2020/09/15 11:52:38 DEBUG : Azure root: >Init:
2020/09/15 11:52:38 DEBUG : /: Statfs:
2020/09/15 11:52:38 DEBUG : /: >Statfs: stat={Bsize:4096 Frsize:4096 Blocks:274877906944 Bfree:274877906944 Bavail:274877906944 Files:1000000000 Ffree:1000000000 Favail:0 Fsid:0 Flag:0 Namemax:255}, errc=0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Readlink:
2020/09/15 11:52:38 DEBUG : /: >Readlink: linkPath="", errc=-40
The service rclone has been started.
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Opendir:
2020/09/15 11:52:38 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2020/09/15 11:52:38 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2020/09/15 11:52:38 DEBUG : /: >Opendir: errc=0, fh=0x0
2020/09/15 11:52:38 DEBUG : /: Releasedir: fh=0x0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: >Releasedir: errc=0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Opendir:
2020/09/15 11:52:38 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2020/09/15 11:52:38 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2020/09/15 11:52:38 DEBUG : /: >Opendir: errc=0, fh=0x0
2020/09/15 11:52:38 DEBUG : /: Releasedir: fh=0x0
2020/09/15 11:52:38 DEBUG : /: >Releasedir: errc=0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF
2020/09/15 11:52:38 DEBUG : /: >Getattr: errc=0
2020/09/15 11:52:38 DEBUG : /: Opendir:
2020/09/15 11:52:38 DEBUG : /: OpenFile: flags=O_RDONLY, perm=-rwxrwxrwx
2020/09/15 11:52:38 DEBUG : /: >OpenFile: fd=/ (r), err=<nil>
2020/09/15 11:52:38 DEBUG : /: >Opendir: errc=0, fh=0x0
2020/09/15 11:52:38 DEBUG : /: Releasedir: fh=0x0
2020/09/15 11:52:38 DEBUG : /: >Releasedir: errc=0

hello and welcome to the forum,

the mount looks good.

mounting on windows can be a bit confusing due to the way windows deals with shares.
for a given windows user, there are two separate sets of shares.
one for users with elevated rights.
one for users without elevated rights.

as a test,
run the mount the rclone mount without --fuse-flag
then open two commands prompts.

  1. with admin rights
  2. without admin rights

and for each do a dir g:

Thank you! the network drive was attached without running cmd as admin. not sure why it was not working with admin

if you run rclone mount as system user, then all users can see it.

and you might find this interesting

https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command