I cannot see the Z:-drive or I:-drive
The problem
It can happen for some reasons you don't have access to your Z:-drive or I:-drive.
The main reason for this issue is that many applications have shifted to using TLS 1.2 for security. Because of this, please follow the instructions in Z:/ Drive Not Visible.
If your TLS is already updated to the latest version, please follow the instructions below:
Windows virtual machine
The solutions
There are two solutions you can try:
- Solution 1 - Easiest
- Solution 2 - Create a support ticket and provide information for troubleshooting if still needed
- which workspace is affected: e.g. dws-123-XXX
- which virtual machine is affected: e.g. dws123XXXserver1
- which users are affected (if applicable)
- what changed? Were you able to see the drives before?
- Provide information and eventual errors that occurred during solution 1
Solution 1 - Easiest
In most cases the following will work:
- Log into the Windows VM
- Open File Explorer
- Go to c:\Scripts
- Right click the file Mount... and press Run with PowerShell
For a brief moment a window opens and then closes. Check if you have now access to the z:-drive and i:-drive again.
If you don't see the folder in step 3 or the script, create a suppor ticket with: Workspace, VM, Can't access Z:-drive - no c:\Script
Solution 2: Elaborate with information for troubleshooting if needed
- Log into the Windows VM
- Click Windows
- Type powershell
- Right click Windows Powershell ISE, run as administrator
- Press Yes
- File, Open
- Navigate to c:\scripts\mountstorage...
- Press Run Button
- Something similar like this should appear, if not,
- Create a ticket: Workspace, VM, screenshot of the output
Linux virtual machine
The solutions
There are two solutions you can try:
- Solution 1 - Easiest
- Solution 2 - Create a support ticket and provide information for troubleshooting if still needed
- which workspace is affected: e.g. dws-123-XXX
- which virtual machine is affected: e.g. dws123XXXserver1
- which users are affected (if applicable)
- what changed? Were you able to see the drives before?
- Provide information and eventual errors that occurred during solution 1
Solution 1:
1. Log in to your Linux VM
2. If you're not able to go the Z-drive with ls /mnt/workspace, use /usr/bin/mountWorkspace.sh. This path contains a script that re-mounts the Z-drive.
Solution 2:
If your Linux VM does not contain this script, then you might have an old version of a virtual machine. The easiest and quickest way would then be to create a new Linux VM.
Related Articles
Z:-drive not available in newly created VM from image
Bug description A VM based on an image does not mount the Z-drive for those who were part of the VM from which the image was created. However this is visible: Related to: Generalize a VM for your Workspace Creating VM images for Shared storage Cause ...Accessing snapshots of files stored on Z-drive
Introduction Data in your workspace is recommended to be stored on the data/Z-drive. The Z-drive is an Azure Fileshare that can store up to 5 TiB by default. Moreover, every evening at 23:00 (UTC+01:00, Amsterdam Time Zone) a snapshot is created from ...How to recover data from the C-drive when the VM is inaccessible (Windows)
Introduction There are several reasons why a VM would become inaccessible. While we always suggest storing data on the Z-drive (because it is snapshotted and accessible from every VM within the same workspace), users still might have data on the ...I cannot see my workspaces
When logged into DRE, you should see an overview of your workspaces. Do you get the message 'Workspaces loading'? The most common reason for this is that necessary cookies are blocked. DRE only runs on certain browsers with cookies enabled. Cookies ...Storage types in the workspace
Disclaimer: you are yourself responsible for managing your research budget and keeping track of workspace costs! While we try to keep the article update, the listed information is dependent on policies and tariffs that may change over time. No rights ...