SOLVED

Azure Cloud Shell error

Iron Contributor

I am getting this error messagem when connecting to the bash:

 

"Warning: Failed to mount the Azure file share. Your cloud drive won't be available.                                                                                                  

Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session."

 

Anyone with the same problem? 

22 Replies
@Sander van de Velde, you`ve been playing with the Cloud Shell. Have you seen this error?

Seems the storage is already deleted but the cloud drive is still connected.

 

Try in the shell: "clouddrive unmount" and then refresh.

 

See my blog for more details.

best response confirmed by Daniel Martins (Microsoft)
Solution

Sorry you hit this bug Miguel! We're tracking this issue and should have a fix for this very soon! By chance did you delete the storage resource that was created for you when first launching Cloud Shell?

 

Sander is correct in troubleshooting, could you:

1. Run "clouddrive unmount"

2. Restart Cloud Shell via restart icon or exit and relaunch

3. You should be prompted with the storage creation dialog again

 

Let me know if this works or not for you!

This had solved it! thank you very much!
Glad it`s working now, Miguel 🙂 Looking forward to see your use cases and how you`re using Cloud Shell on your next posts!

Hello Justin!

 

I am having a bit of an issue with such when I run  " Clouddrive unmount ", I receive the error: 

 

Get-CloudDrive : A positional parameter cannot be found that accepts argument 'unmount'.
At line:1 char:1
+ clouddrive unmoint
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-CloudDrive], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Get-CloudDrive

 

And I do to receive the same error here :

 

Warning: Failed to mount the Azure file share. Your cloud drive won't be available.
Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session.
VERBOSE: Authenticating to Azure ...
WARNING: Azure Authentication failed.

 

So I am unable to use correctly The Azure Cloud Shell, 

 

Any help is greatly recieved

Hey, sorry for the trouble could you provide some more info:

 

1. Could you confirm if you are using Bash or PowerShell in Cloud Shell?

 

Currently PowerShell in Cloud Shell uses a different syntax so instead of `clouddrive unmount` run `Dismount-clouddrive`

 

https://docs.microsoft.com/en-us/azure/cloud-shell/persisting-shell-storage-powershell#unmount-cloud...

Hello Yeah my bad, I am using PowerShell Cloud Shell,

That solved the issue! Thank you so much!!

that worked for me thanks

Thanks! clouddrive unmount did trick

The Azure files must reside in the same region as the Cloud Shell machine that you're mounting them to

Hello @Sander van de Velde,

 

I also have issue with Cloud Shell. I deleted the storage account. The only thing I see is a black screen which you can not type anything when I tried to open cloud shell. I capture the network traffic with developer toolbar. And I got the following errors in Network capture;

 

tMxf3Smml7AJ.js:301 Version: 5.0.302.19201 (production#b424e9216a.190425-0702) Signed
Session: be97699f211b4ac9bf608af25212b017
dd918b7a-b105-48dc-8f2b-681f043d2327:1 Extension: HubsExtension
jquery-3.1.1.min.js:4 GET https://management.azure.com/providers/Microsoft.Portal/userSettings/cloudconsole?api-version=2018-1... 404
send @ jquery-3.1.1.min.js:4
ajax @ jquery-3.1.1.min.js:4
loadUserSettings @ main.js:1372
getUserSettings @ main.js:525
checkUserSettings @ main.js:443
provisionConsole @ main.js:1621
createTerminal @ main.js:1488
createOrUpdateTerminal @ main.js:310
handleToken @ main.js:222
postMessageHandler @ main.js:294
postMessage (async)
(anonymous) @ cTUoubnCk39Q.js:2
o @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
Promise.then (async)
i.then @ jUFrF_6FnicM.js:4
t.addEventListener._postMessageHandler @ cTUoubnCk39Q.js:2
postMessage (async)
postMessageHelper @ main.js:1730
getTokens @ main.js:1735
setupParentMessage @ main.js:305
(anonymous) @ main.js:3062
j @ jquery-3.1.1.min.js:2
k @ jquery-3.1.1.min.js:2
setTimeout (async)
(anonymous) @ jquery-3.1.1.min.js:2
i @ jquery-3.1.1.min.js:2
fireWith @ jquery-3.1.1.min.js:2
fire @ jquery-3.1.1.min.js:2
i @ jquery-3.1.1.min.js:2
fireWith @ jquery-3.1.1.min.js:2
ready @ jquery-3.1.1.min.js:2
R @ jquery-3.1.1.min.js:3
main.js:649 Uncaught TypeError: Cannot read property 'quotaId' of undefined
at validateStorageSupport (main.js:649)
at HTMLSelectElement.<anonymous> (main.js:432)
at HTMLSelectElement.dispatch (jquery-3.1.1.min.js:3)
at HTMLSelectElement.q.handle (jquery-3.1.1.min.js:3)
at Object.trigger (jquery-3.1.1.min.js:4)
at HTMLSelectElement.<anonymous> (jquery-3.1.1.min.js:4)
at Function.each (jquery-3.1.1.min.js:2)
at r.fn.init.each (jquery-3.1.1.min.js:2)
at r.fn.init.trigger (jquery-3.1.1.min.js:4)
at r.fn.init.r.fn.<computed> [as change] (jquery-3.1.1.min.js:4)
validateStorageSupport @ main.js:649
(anonymous) @ main.js:432
dispatch @ jquery-3.1.1.min.js:3
q.handle @ jquery-3.1.1.min.js:3
trigger @ jquery-3.1.1.min.js:4
(anonymous) @ jquery-3.1.1.min.js:4
each @ jquery-3.1.1.min.js:2
each @ jquery-3.1.1.min.js:2
trigger @ jquery-3.1.1.min.js:4
r.fn.<computed> @ jquery-3.1.1.min.js:4
populateSubscriptions @ main.js:892
(anonymous) @ main.js:632
i @ jquery-3.1.1.min.js:2
fireWith @ jquery-3.1.1.min.js:2
A @ jquery-3.1.1.min.js:4
(anonymous) @ jquery-3.1.1.min.js:4
load (async)
send @ jquery-3.1.1.min.js:4
ajax @ jquery-3.1.1.min.js:4
getSubscriptions @ main.js:604
(anonymous) @ main.js:531
(anonymous) @ main.js:465
dispatch @ jquery-3.1.1.min.js:3
q.handle @ jquery-3.1.1.min.js:3
main.js:2584 GET https://az416426.vo.msecnd.net/scripts/a/ai.0.js net::ERR_TIMED_OUT
(anonymous) @ main.js:2584
(anonymous) @ main.js:2585
j @ jquery-3.1.1.min.js:2
k @ jquery-3.1.1.min.js:2
setTimeout (async)
(anonymous) @ jquery-3.1.1.min.js:2
i @ jquery-3.1.1.min.js:2
fireWith @ jquery-3.1.1.min.js:2
fire @ jquery-3.1.1.min.js:2
i @ jquery-3.1.1.min.js:2
fireWith @ jquery-3.1.1.min.js:2
ready @ jquery-3.1.1.min.js:2
R @ jquery-3.1.1.min.js:3
jUFrF_6FnicM.js:4
Uncaught (in promise) {errorMessage: null, alternateBladeSelection: {…}, isOldCreate: false, errorType: 6, logLevel: 0}
r @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
i @ jUFrF_6FnicM.js:4
ht @ jUFrF_6FnicM.js:4
(anonymous) @ y4lOzJCwV4Dg.js:48
o @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
Promise.then (async)
i.then @ jUFrF_6FnicM.js:4
c.checkForAlternateInformationalBlade @ y4lOzJCwV4Dg.js:48
o @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
Promise.then (async)
i.then @ jUFrF_6FnicM.js:4
c.getCreateFlow @ y4lOzJCwV4Dg.js:48
(anonymous) @ oXemOwQVUcBf.js:7
o @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
Promise.then (async)
i.then @ jUFrF_6FnicM.js:4
(anonymous) @ oXemOwQVUcBf.js:7
o @ jUFrF_6FnicM.js:4
(anonymous) @ jUFrF_6FnicM.js:4
Promise.then (async)
i.then @ jUFrF_6FnicM.js:4
t @ oXemOwQVUcBf.js:7
n._submitSearchString @ oXemOwQVUcBf.js:7
(anonymous) @ oXemOwQVUcBf.js:7
n._submitSearchStringHelper @ oXemOwQVUcBf.js:1
submit @ oXemOwQVUcBf.js:1
n.invoke @ -BO3lVo_n2M3.js:36
(anonymous) @ -BO3lVo_n2M3.js:38
n.handleMessage @ -BO3lVo_n2M3.js:38
n.handle @ -BO3lVo_n2M3.js:38
(anonymous) @ -BO3lVo_n2M3.js:38
n.handleMessage @ -BO3lVo_n2M3.js:38
(anonymous) @ -BO3lVo_n2M3.js:38
b @ -BO3lVo_n2M3.js:38
n.handleMessage @ -BO3lVo_n2M3.js:38
(anonymous) @ -BO3lVo_n2M3.js:38
n._processInnerList @ -BO3lVo_n2M3.js:38
n.addItem @ -BO3lVo_n2M3.js:38
_handleMessage @ -BO3lVo_n2M3.js:38
dd918b7a-b105-48dc-8f2b-681f043d2327:1 Extension: Microsoft_Azure_Storage

@Justin Luk - In my case, the warning was due to the firewall settings. I had removed public access to the storage account. I kept getting only the warning (no error message) - "Your Cloud Shell session will be ephemeral so no files or system changes will persist beyond your current session". Tried the unmount command which prompted to reload/recreate the file share, but would not create the file share in the storage account and I kept getting the same warning. Removed the firewall restrictions and it fixed the issue, but now I have to dig deep to find out what is the source IP/subnet for the built-in shell before re-enabling the firewall.

 

 

@vasun76 did you have any luck?  The Firewall is my issue as well.  I tried adding my own IP and the IP when running 'curl http://ifconfig.me/ip' from the shell.  I still get that warning.  However, my session seems to persist and I don't lose any files, so maybe it is warning that isn't breaking anything.

@vasun76 Azure storage firewall is not supported for cloud shell storage accounts. See the note on this page: https://docs.microsoft.com/en-us/azure/cloud-shell/persisting-shell-storage

@falk0069, see my reply to@vasun76, might be helpful.

@Justin Luk, works for me. Thanks!

I wasn't able to Resolve the error Warning: Failed to mount the Azure file share. Your cloud drive won't be available. even though I run the clouddrive unmount command on CLI. Please provide some support.

Hi Miguel,
I am having error while running commands on Azure Cloud Shell from Microsoft Learn website.
I deleted and recreated resource group but the same error since 1 week. can you please help? Thnx in advance.
https://docs.microsoft.com/en-us/learn/modules/secure-and-isolate-with-nsg-and-service-endpoints/3-e...
Command:
rg=<resource group name>
az group create --name $rg --location <location>

Error:
rg=<resource: The term 'rg=<resource' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

1 best response

Accepted Solutions
best response confirmed by Daniel Martins (Microsoft)
Solution

Sorry you hit this bug Miguel! We're tracking this issue and should have a fix for this very soon! By chance did you delete the storage resource that was created for you when first launching Cloud Shell?

 

Sander is correct in troubleshooting, could you:

1. Run "clouddrive unmount"

2. Restart Cloud Shell via restart icon or exit and relaunch

3. You should be prompted with the storage creation dialog again

 

Let me know if this works or not for you!

View solution in original post