What is the definition of a resource disk in Microsoft Azure? I see the term used in the response to my REST call to get the available Virtual Machine sizes. The documentation says that "ResourceDiskSizeInMB" specifies the size in MB of the temporary or resource disk. However I don't see the term resource disk being used anywhere else.
Does this mean that resource disks are the same as temporary disks?
Does this mean that resource disks are the same as temporary disks?
You are right, when we list all available virtual machine sizes for a subscription in a location, we will get the information about "resourceDiskSizeInMb", it is Local SSD(temporary disk), we can find it in this page.
{
"maxDataDiskCount": 2,
"memoryInMb": 3584,
"name": "Standard_D1_v2",
"numberOfCores": 1,
"osDiskSizeInMb": 1047552,
"resourceDiskSizeInMb": 51200
},
The term Resource Disk is used in /etc/waagent.conf. You can specify a mount point along with filesystem type and a few other options.
Related
i need to change my azure kubernetes pod disk type from premium ssd to standard ssd, but the disk contains some data, can i directly change the type or need to migrate the data first?. thanks
disk type changed with old data still exists
To change pod disk type from Premium to Standard, you can create new pod with standard disk type and then migrate/transfer the data. Finally, delete the old premium ssd pod.
See more details regarding Azure volume disk in :
https://learn.microsoft.com/en-us/azure/aks/concepts-storage#persistent-volumes
I am not able to extend azure SQL vm data disk size from 4TB to 8TB using Terraform
It's giving error me the error
Error updating managed disk.disks can not be resized beyond 4TB when attached to vm
Note: this happens although the VM is in stopped (deallocated state)
As per official documentation, You can now resize your managed disks without deallocating your VM.
To register for the feature, use the following command:
Register-AzProviderFeature -FeatureName "LiveResize" -ProviderNamespace "Microsoft.Compute"
It may take a few minutes for registration to take complete. To confirm that you've registered, use the following command:
Register-AzProviderFeature -FeatureName "LiveResize" -ProviderNamespace "Microsoft.Compute"
Note - The new size should be greater than the existing disk size. The
maximum allowed is 4,095 GB for OS disks. (It's possible to expand the
VHD blob beyond that size, but the OS works only with the first 4,095
GB of space.)
I have Azure VM (Windows Server 2012R2 with SQL Server).
Since I was changed the size I cannot start the VM, When I'm trying to start I got the following failed error:
Provisioning state Provisioning failed. One or more errors occurred while preparing VM disks. See disk instance view for details.. DiskProcessingError
DISKS
MyVM_OsDisk_1_47aaea403b8948fb8d0e3ba0e81e2fas Provisioning failed. Requested operation cannot be performed because storage account type 'Premium_LRS' is not supported for VM size 'Standard_D2_v3'.. VMSizeDoesntSupportPremiumStorage
MyVM_disk2_ccc04be996a5471688d357bf6f955fab Provisioning failed. Requested operation cannot be performed because storage account type 'Premium_LRS' is not supported for VM size 'Standard_D2_v3'.. VMSizeDoesntSupportPremiumStorage
What Is the problem and how can I solve it please?
Thanks!
As the error details shows, this is because Premium disk is not supported for D2_V3 VM Size.
Solution :
If you want to use SSD premium Disk for your VM , you can Resize your VM size to DS-series, DSv2-series, GS-series, Ls-series, and Fs-series VMs.
If you don't mind using Standard HDD disk, but want to use D2_V3 VMsize. You can Change the Disk type to Standard (If your disks are managed).
Deallocate your VM > Disk > Choose the disk > Change the Account type to standard > save
Additional, I assume that your disks are managed. If not, you'd better resize your VM rather than change back to standard disk.
I'm trying to attach an existing VHD disk from a Storage Account to VM during Azure Resource manager provisioning with a template.
My dataDisk resource is:
"dataDisks": [
{
"name": "jmdisk",
"diskSizeGB": "100",
"lun": 0,
"vhd": {
"uri": "https://jmje.blob.core.windows.net/vhds/jenkinshome.vhd"
},
"createOption": "attach"
}
]
But during deploy - I have an error from Azure:
STATUSMESSAGE{
"error": {
"code": "OperationNotAllowed",
"target": "dataDisk",
"message": "Addition of a blob based disk to VM with managed disks is not supported."
}
}
Unfortunately can't google anything related, i.e. - a correct way to attach an existing disk.
UPD Solved this by just creating new Managed disk and copy data there.
You can create a managed disk from an existing blob -- you can see a sample of that here: https://github.com/chagarw/MDPP/blob/master/101-create-image-availabilityset-2vm-from-blob/azuredeploy.json
It uses existing blobs for both OS and data, you don't have to do it that way... In your case it sounds like you want an implicit OS disk and then an explicit data disk? Which you could also do, just use different images for each.
Well, the error gives it up, you are probably not familiar with Managed Disks yet. So you are creating a VM with OS disk as managed, in that case you cannot use existing disks to attach to a VM, just create a VM with regular disk (just like you do with data disk).
When I attempt to delete a blob from my storage account container, I get an error message, "There is currently a lease on the blob and no lease ID was specified in the request."
I have 4 virtual machine instances. I also have 8 virtual machine disks, 4 of which are in use (one by each of the virtual machine instances). Strangely, I have 10 blobs listed in my single storage account's lone container, called vhds. Here is a screenshot of the 10 blobs, highlighting the two that I cannot delete.
Can anyone give me guidance on how to delete these blobs? I have no use for them and I'd like to cut down on my storage costs for my subscription.
You need to delete the disks from the Virtual Machines section of the portal.
Navigate to Virtual Machines -> Disks
Delete the disks
Check this MSDN blog post for the complete instructions:
http://blogs.msdn.com/b/windows_azure_technical_support_wats_team/archive/2013/02/05/iaas-unable-to-delete-vhd-there-is-currently-a-lease-on-the-blob.aspx
Alternatively, you can just kill the lease on the Blobs with PowerShell:
(Get-AzureRmStorageAccount -Name "STORAGE_ACCOUNT_NAME" | Get-AzureStorageBlob -name "CONTAINER_NAME").ICloudBlob.BreakLease()
Just realize when you do this, the VM's that use this storage will not be able to turn on. (And you should turn them off if they aren't already before you do this.
However, if you might use the VM's again in the future this technique allows you to:
Stop the VM in question.
Download a copy of the VHD.
Release the lease on the VHD
Delete the VHD in the storage account.
Insert arbitrary time period where you don't need the VM
Upload the VHD to the same storage account with the same container and same file name.
Start the VM back up and have it work :-).
There is an alternate (easier) way to break a lease if you use (or download) Microsoft Azure Storage Explorer (a really cool tool to manage Azure Storage).
You can browse to the Storage Account and find the relevant file (vhd) and then select the Break Lease option.
The same CAUTIONS above apply and the Explorer tool makes these clear.
You should have images associated to your VMs. Even if you have deleted your VMs, the images have to be explicitly deleted.
Once the images are deleted, you should see VHD getting cleared as well