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.
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
My Azure VMSS is deployed successfully and operating as expected. It uses an Azure Compute Gallery reference image (which includes both an OS disk, and 1x Data Disk).
We are now changing all our Compute Gallery reference images to single OS disk-only (since the Terraform Windows VM resource does not support deploying from an image version that has a data disk included, even though Terraform Windows VMSS resource does support it), but when changing the VMSS from dual-disk image, to the single-disk image, Terraform fails with:
Code="PropertyChangeNotAllowed" Message="Changing property 'dataDisks' is not allowed." Target="dataDisks"
NOTE: I have successfully tested the change from the other way around: ie. Updating a VMSS that runs from a single disk image, to pointing to an image that uses 2 disks. This completed fine. It only fails when trying to go from 2 disks down to 1 disk.
(Using: Terraform v1.0.0; AzureRm Provider v3.0.2)
SOLUTION/WORKAROUND:
So, doing it via Terraform fails, however, with a little help from the portal, we can achieve the desired result. In the portal, on the VMSS, under Settings, select Disks. Detach the data disk from the VMSS. Takes a few seconds. Once that is detached, now run the Terraform again to update the image reference to an image with single disk. This time it completes successfully.
Hope this helps someone out there
In the process of Nuntanix Virtual Machine migration to Azure, I had copied ral-rdmbuild-02 copy.ova file into a windows machine and extracted to get .vmdk and .mf. From the extracted file the .vhd file was created, later it was resized on a ubuntu to meet 1MB requirement.
Subsequently, the .vhd was copied to azure and attempted to create a vm to face the following error. Could someone can help me to overcome this issue.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"OSProvisioningTimedOut","message":"OS Provisioning for VM '' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\r\n * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ \r\n * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ \r\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same."}]}
• Please check whether the Nutanix VM hard disk is configured as a dynamic disk or not because dynamic disks don’t work with Azure, and they can’t be migrated. Also, the image of the Nutanix VM may not be prepared correctly, thus would suggest you recreate the image of the Nutanix VM and try migrating it to Azure once again.
• To convert the dynamic disk to fixed type of virtual disk, kindly refer to the below documentation link that guides to use the appropriate command for converting the same: -
Convert-VHD -Path c:\test\child1vhdx.vhdx -DestinationPath c:\test\child1vhd.vhd -VHDType Fixed
https://learn.microsoft.com/en-us/powershell/module/hyper-v/convert-vhd?view=windowsserver2019-ps
• Also, based on the error message that you are encountering, the OS deployment might have also failed from the Portal side as it was unable to pass on some of the required parameters which is why you got ‘TimeOut’ message. The VM also didn’t finish the deployment correctly. I would recommend trying stop(deallocate) and start the VM and see if that resolves the issue.
I would recommend you delete the VM and its related resources if created and take a snapshot of the OS disk, create a disk from the snapshot and then create the machine from that disk. Please refer to the link below for creating a VM from a ‘VHD’ by using the Azure portal: -
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-centos
• Finally, to generalize the VM and execute ‘sysprep’ on a VM to take its correct reference image such that it can be successfully migrated to another environment, please refer to the below link that explains the correct steps to perform for generalizing the VM: -
https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_1:wc-windows-vm-customize-with-sysprep-clone-vm-wc-t.html
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 an Ubuntu Server 17.10 VM in vCenter that I exported using Export-VApp, then used Microsoft's Virtual Machine Converter to create a VHD. Created an Azure RM Disk Image from that and spun up a VM, all of which seemed to go fine. My problem is that the New-AzureRMVM gets stuck in creating, and when I go to the boot diagnostics from the screenshot it is stuck on a "Please unlock disk sda5_crypt:". First, from what I gather is there really no way to get console access to my VM so that I can enter this? It won't get past creating so connect is greyed out and I can't SSH into it. Is my only option here to go back to the VM on vCenter and migrate the entire partition to a new partition without disk encryption, then redeploy? Is there any sort of startup file Azure accepts that could input this for me?