Managed disks not visible in VM Disk Management

Question

_{Saturday, May 18, 2019 9:20 AM}

I added one SSD in one VM (B2s size with only one OS disk) but I can't find the attached drive in Disk Management (I did a Rescan few times) and in Server Manager/Storage Pools (I did a Rescan Storage few times).  I tried to attach that drive in other VMs but in any of them I can't see the disk. I already tried even with fdisk and diskpart. I tried to detach and attach again and I checked on Event Viewer and I found an entry it shows that as following "Disk 2 has been surprise removed" so I think a disk it seems to me is attached to the VM.

Thank you to all in advance.

All replies (3)

_{Monday, May 20, 2019 6:14 AM ✅Answered}

Hello Enrico,

Thanks for posting your query here. I have tried reproducing the issue, but I don't find any issues with attaching managed disks and from OS I was prompted for initializing the newly added disk.

I have tried below scenarios (OS used was Windows Server 2016):

• Attach managed disk while launching VM from portal.
• Attach extra managed disk after the VM was launched with only OS disk.
• Attach disk from a snapshot for both above mentioned cases, and it worked without any issues.

In all the above cases, the managed disk was visible in disk management. Try to follow this document and give it a try.

Also, found similar issue posted in forum, here the solution was to Redeploy task under Support + troubleshooting in the Azure portal.

Requesting you to mark this reply as answer if it solved your query or vote as helpful if it helped so that community members can find it helpful.

Thanks.

_{Tuesday, May 21, 2019 8:15 AM}

Hello VikasPullagura,

thank you for your reply, I tried just now and it works but I think I found where the problem was. First of all, for example if you add a disk it isn't immediately available, you have to wait until it is deployed. Another thing, but I'm not sure because I didn't test thoroughly. If a VM is in updating you have to wait until is finished, maybe because I didn't refresh the blade of the VM and I didn't wait enough.

Thanks.

_{Wednesday, May 22, 2019 4:28 AM}

Hello Enrico,

Thanks for responding back with your findings. Yes, it is always a good practice to wait till the deployment is complete before performing any further actions. Also refreshing the blades confirm the status so that next actions can be performed.

Requesting you to mark the reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.

Thanks.