Azure VM with VHD image , not showing the extra added disk

Question

I used a .VHD file to create an azure image. Using this Azure Image , created an azure VM.

While creating this Azure VM from the portal, i selected the option to add extra disk with 1 TB capacity and set option to Read/Write.

When i login inside this newly created Azure VM , and check the drive capacity. none of the drives shows the 1 TB provisioned capacity.

Why is it not showing the 1 TB image , which i had provisioned and it shows in azure portal , that there is extra data disk with 1 Tb , but inside Azure VM , when i go to my computer and select This PC , it does not show 1 TB . What can i do to solve this ?

Answer 1

Hello MS Techie

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Ensure that the size of the Azure VM you are using supports attaching the additional 1 TB disk. Some VM sizes have limitations on the number and size of data disks that can be attached. Check the documentation or specifications for your specific VM size.

Please try to restart the VM and check if the disk is visible inside OS.

If you are not able to see the added data disk in the Server Management Console, you can try the following steps to initialize and format the disk:

1. Connect to your Azure VM using Remote Desktop Connection.
2. Open the Disk Management console by right-clicking on the Start button and selecting Disk Management.
3. In the Disk Management console, you should see the added disk listed as "Unknown" and "Not Initialized". Right-click on the disk and select Initialize Disk.
4. In the Initialize Disk dialog box, select the disk(s) you want to initialize and choose the partition style. Click OK.
5. After initializing the disk, right-click on the unallocated space and select New Simple Volume.
6. Follow the New Simple Volume Wizard to format the disk and assign a drive letter.

Once you have completed these steps, you should be able to see the added data disk with 1 TB capacity in the Server Management Console.

If the issue persists, you can try attaching the data disk to another VM to see if it is working properly.

Hope this helps.