Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, November 30, 2017 11:38 AM
I have two VM's; both have this problem. They are running Standard_DS2_V2, which should support 8 data disks. I created two identical Premium-LRS Managed disks from the Disk blade on the VM. Upon RDP to the VM, disks do not appear in diskmgmt.msc nor in diskpart. I have recreated both VM's but the problem persists.
All replies (11)
Thursday, November 30, 2017 6:27 PM
Are you able to view in the portal?
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members Are you able to view in portal?
Thursday, November 30, 2017 8:04 PM
Yes. They always appear in the portal under the VM==>Disks blade, as well as in the ResourceGroup. I noticed that changing the size caused the size not to appear in the VM==>Disk blade. I recreated with the default size of 1023GB and the size now appears again, but the disks still do not appear in the VM. I tried to create them one at a time and see if that would help them appear in diskpart in the VM, but that also did not work.
Friday, December 1, 2017 4:22 PM
Can you try the suggestion mentioned in this link and let me know the outcome.
Hope this may help you
Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members
Saturday, December 2, 2017 3:27 AM
Please refer to the my previous comments. I have mentioned several times that the disks do not appear in diskpart. Therefore none of the recommendations in your link can be followed. (chkdsk cannot be used if the disks do not yet have a drive letter, so appearing in diskpart is a prerequisite to chkdsk.)
BVelow the first screenshot shows only drive C: and the Azure supplied temporary drive D: which is used for virtual memory by Windows. The two attached drives do not appear. This IS the problem, so suggesting I use diskpart to resolve the problem, when the disks do not appear there, is not going to work.
The second screenshot is of the disk details in the portal showing the disk is attached to this VM. Please help.
Saturday, December 2, 2017 2:31 PM
Create a Technical Support Ticket as our engineers would need to work with you on the issue and would require more details on the issue to find the root cause of the issue.
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
Saturday, December 2, 2017 11:52 PM
OK, I have created a Support Request and sent the screenshots with it. Wish me luck...
Tuesday, September 4, 2018 9:22 AM
You must Initialize Disk
follow https://docs.microsoft.com/en-gb/azure/virtual-machines/windows/attach-managed-disk-portal
Friday, May 10, 2019 8:43 PM
Alex71938 and CHEEKATLAPRADEEP-MSFT: This is not a solution. The disk does not appear in diskmgmt, so we cannot initialize it with that tool.
FWIW, I now have exactly the same problem. 2 Az premium data disks, used to be visible inside the VM, now they're not. I can still see them in the Az portal, here they look same as ever. Within the VM they are not visible to diskpart or diskmgmt. Rebooted, rescanned, they're not visible.
No solution in sight, reckon I'm going to burn down and recreate my VMs.
Tuesday, May 14, 2019 7:00 AM
I had the same problem and I solved it by using the Redeploy task under Support + troubleshooting in the Azure portal.
Wednesday, October 23, 2019 3:20 PM
This is not a sufficient answer - redeploying may wipe out existing configurations that we took hours to set up. There needs to be an actual fix detailed and documented.
Wednesday, October 23, 2019 4:36 PM
@PrometheusRising May I know what exactly are you trying to perform? For better understanding please elaborate the issue more?