locked
VM becomes unresponsive or disk becomes read-only RRS feed

  • Question

  • If your Windows VM has become unresponsive or your disk becomes read-only, attempt to restart the VM through the portal or through the scripts. In many cases, this will resolve the issue and the VM will return to healthy.

    However, if restarting your VM gets stuck in "stopping" indefinately, you can workaround this issue by removing the virtual machine (hitting delete in the portal) and re-deploying it using the same VHD disk that you used. You will also need to re-attach any data disks you were using as well. This will appear like a hard "reboot" to the Virtual Machine. This re-creation of the VM can be accomplished by going through the create VM process in the portal, selecting gallery, and from there selecting "My Disks."

    Additionally, if you want to use the same DNS name, you will also need to delete the respective cloud service in the portal, along with the virtual machine, to release that previous DNS name reserved.

    You can also import/export using powershell capabilities (which also saves aside the ports added and the data disks attached). Details on this can be found here:

    Download the PowerShell Tools here:

    https://www.windowsazure.com/en-us/manage/downloads/

    Documentation on configuring PowerShell can be found here:

    http://msdn.microsoft.com/en-us/library/windowsazure/jj156055.aspx

    Import/Export:

    To export:

    Export-AzureVM -ServiceName 'ServiceName' -Name 'VMName'-Path 'c:\folder\VM.xml'

    Then, remove the VM:

    Remove-AzureVM -ServiceName 'ServiceName' -Name 'VMName'

    To import:

    Import-AzureVM -Path 'c:\folder\VM.xml' |
    >> New-AzureVM -ServiceName 'ServiceName' -Location 'loc'

    More Details on using the import/export functionality, try this blog post:

    http://michaelwasham.com/2012/06/18/importing-and-exporting-virtual-machine-settings/

    Thursday, July 26, 2012 3:26 PM

Answers

  • Hello,

    We are going to close this thread but if you have the issue still occurring please open a new thread for support.

    Thanks!

    Patrick [MSFT]

    Tuesday, February 12, 2013 5:06 PM

All replies

  • Hi, 

    We just experienced disk became read-only (We are on Centos 6.2). 

    - We weren't able to reboot it from the control panel. 
    - But we managed to reboot it from command line. 

    Why and how did this happen?!? Can't imagine this if we go live and this happens. Please advice. Thank you!

    Sunday, July 29, 2012 3:28 PM
  • Hi,

    Is this happening to CentOS only or for all Linux VMs on Azure? 

    asctag Team

    Wednesday, August 1, 2012 2:23 AM
  • Hi,

    I wanted to ask if there's an update on this issue?

    I have 2 large instances running CentOS and this is happening 3 or 4 times a day (on my small instance I don't see this problem).
    Restart do solve it but it's really not really reliable...

    Thanks,
    Zohar

    Monday, August 6, 2012 8:05 AM
  • Craig,

    Have not seen any updates on this issue for a while. 
    Created a Microsoft support ticket as advised and tried to follow up (but the email box is full).

    What is the current status of this issue?

    Wednesday, August 22, 2012 9:01 AM
  • experienced once...

    any explanation to what caused this?

    Friday, August 31, 2012 6:14 AM
  • Hello,

    We are going to close this thread but if you have the issue still occurring please open a new thread for support.

    Thanks!

    Patrick [MSFT]

    Tuesday, February 12, 2013 5:06 PM