Azure Linux VM agent unresponsive

Question

Azure Linux VM agent unresponsive

Tika Syahfitri 20

We are having issues connecting to our Linux VM via SSH. In the portal, it is saying that the agent is unresponsive and unhealthy.
What we have done so far:

Resetting the config by resetting the password. Did not work.
Tried to stop the VM but it is not able to.

The last log showed this:

"submissionTimestamp": "2025-05-31T23:43:52.087Z", "subscriptionId": "xxx", "tenantId": "", "properties": { "title": "Migration scheduled due to degraded hardware", "details": "", "currentHealthStatus": "Degraded", "previousHealthStatus": "Available", "type": "Downtime", "cause": "PlatformInitiated" },

Please let us know how we can troubleshoot this issue. Thanks

TP 124.7K Reputation points Volunteer Moderator

2025-06-05T03:59:40.3666667+00:00

Hi Tika,

Have you tried Redeploy? This is under Help - Redeploy + reapply - Redeploy

From the error you posted it appears there was a hardware issue and your VM should've been automatically moved to new physical host, but perhaps something went wrong.

If the above does not work you may need to open support case so that engineer can fix it on backend. Which Azure support plan do you have? You may use link below to check which plan you have:

https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/supportPlans

-TP
Tika Syahfitri 20 Reputation points

2025-06-05T04:13:00.78+00:00

Thanks but it fails to redeploy
Tika Syahfitri 20 Reputation points

2025-06-05T04:14:14.3+00:00

I have Developer tier support plan
TP 124.7K Reputation points Volunteer Moderator

2025-06-05T04:18:29.2366667+00:00

I have Developer tier support plan

Okay, you are in the right place. An External Staff Member will respond and if necessary open a support ticket on your behalf to resolve the issue with your VM.

Priority community support (PCS) for Azure developer support plan customers

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/priority-community-support
Tika Syahfitri 20 Reputation points

2025-06-05T04:20:51.6566667+00:00

Thank you. Please get back to me as soon as possible as this is affecting our production use.

Accepted answer

0 additional answers

Your answer

TP 124.7K Reputation points Volunteer Moderator

2025-06-05T03:59:40.3666667+00:00

Hi Tika,

Have you tried Redeploy? This is under Help - Redeploy + reapply - Redeploy

From the error you posted it appears there was a hardware issue and your VM should've been automatically moved to new physical host, but perhaps something went wrong.

If the above does not work you may need to open support case so that engineer can fix it on backend. Which Azure support plan do you have? You may use link below to check which plan you have:

https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/supportPlans

-TP
Tika Syahfitri 20 Reputation points

2025-06-05T04:13:00.78+00:00

Thanks but it fails to redeploy
Tika Syahfitri 20 Reputation points

2025-06-05T04:14:14.3+00:00

I have Developer tier support plan
TP 124.7K Reputation points Volunteer Moderator

2025-06-05T04:18:29.2366667+00:00

I have Developer tier support plan

Okay, you are in the right place. An External Staff Member will respond and if necessary open a support ticket on your behalf to resolve the issue with your VM.

Priority community support (PCS) for Azure developer support plan customers

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/priority-community-support
Tika Syahfitri 20 Reputation points

2025-06-05T04:20:51.6566667+00:00

Thank you. Please get back to me as soon as possible as this is affecting our production use.

Answer 1

TP 124.7K Volunteer Moderator

UPDATE: from Tika in regards to fix:

I managed to fix it by changing the fstab file once I created a new disk from the snapshot of the affected VM. There were some mount points that were failing which caused it to not boot up correctly.

Tika Syahfitri wrote:

Thank you. Please get back to me as soon as possible as this is affecting our production use.

If you have backup you could restore it to a new VM instead of waiting for support. Another option would be to take snapshot of your disk(s) and then create new VM from snapshot.

Basic steps to create new VM from existing VM using snapshot are:

Create snapshot from existing OS disk by navigating to disk and clicking Create snapshot and filling out details. If you have data disk(s) you can create snapshots of those as well.
Navigate to OS snapshot, click Create Disk, fill out details. Create disk(s) from snapshot(s) of your data disk(s), if applicable.
Navigate to new Disk, click Create VM, attach data disk(s) on Disks tab if applicable, set VNet/subnet to match original VM, fill out details.
Test new VM to make sure everything is okay

Above is summary of steps. If you have questions and/or need me to elaborate on specific areas please let me know.

Once you verified that new VM is working fine you could wait say a week or so and delete old VM.

They are supposed to respond within 8 business hours for Developer support plan. If you upgraded to Standard plan you could open Severity A case which has <1 hour response time.

I'm not saying you should upgrade, just letting you know potential options.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Tika Syahfitri 20 Reputation points

2025-06-05T04:32:16.2366667+00:00

I have tried to detach the disk so that I can troubleshoot it on another VM - both through the CLI and the portal. This did not work as the disk refused to be disconnected to the VM.

I have created a snapshot and a new disk which is now attached to another VM.

If this doesn't work I will create a new VM and then delete the previous one as you mentioned. Note that the original VM is on a reservation plan. Would this affect it?
TP 124.7K Reputation points Volunteer Moderator

2025-06-05T04:37:35.25+00:00

If this doesn't work I will create a new VM and then delete the previous one as you mentioned. Note that the original VM is on a reservation plan. Would this affect it?

No, reservation will not affect it. It is strictly for applying discount to running VM.

If the bad VM is still showing as Running, it may be using up a reservation for discount purposes, and thus when you create new VM the new VM may not receive discounted price if there are no other applicable reservations available.

After you get everything fixed you could open separate Billing support case (free of charge) and ask to be credited if you were overcharged.

And if applicable you can request Service Level Agreement refund via billing support case as well.
TP 124.7K Reputation points Volunteer Moderator

2025-06-05T07:11:39.53+00:00

@Tika Syahfitri Any update? I converted my earlier comment to an answer and added summary steps for creating new VM from existing VM using snapshot method.
Tika Syahfitri 20 Reputation points

2025-06-05T07:16:16.5533333+00:00

I managed to fix it by changing the fstab file once I created a new disk from the snapshot of the affected VM. There were some mount points that were failing which caused it to not boot up correctly.
TP 124.7K Reputation points Volunteer Moderator

2025-06-05T07:19:01.86+00:00

Great. I will update my answer with note on how you fixed it. Please click Accept Answer to close up this thread.

Thank you.

Share via

Azure Linux VM agent unresponsive

0 additional answers

Your answer