az vm repair repair-button --button-command 'fstab' --verbose --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_VM_NAME)

Hello @Everhartz, Stefan ,

Thank you for reaching out to Microsoft Q&A!

My apologise my message does not answer your particular question, but an error from your logs. Please follow advice provided by @Jilakara Hemalatha

The error logs indicate that the operation failed due to an Azure Policy violation, specifically:

Resource 'repair-vmlinuxpla_VNET' was disallowed by policy. Reasons: 'Please enable both Private Endpoint Network Policies'.

By default, the az vm repair create command attempts to create a new Virtual Network for the repair VM. Your environment has an Azure Policy that blocks the creation of new VNets.

Potential fixes:

To solve this issue, you should instruct the command to use an existing subnet (for example, the same subnet where your broken VM resides) instead of trying to create a new one.

You need to use the --subnet parameter with the full Resource ID of the subnet.

The Subnet Resource ID can be obtained by using PowerShell or rc.portal.azure.com and getting the id property from the subnet. An example subnet ID is

/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Network/virtualNetworks/<virtual-network-name>/subnets/<subnet-name>

Run the repair command with the Subnet ID.

If the information is helpful, please click on "Accept Answer" and "Upvote"

If you have any queries, please do let us know, we will help you.

Hello Everhartz, Stefan

Thank you for reaching out Q/A. Thank you for reaching out on Microsoft Q&A.

The failure observed while running the Azure Linux Auto Repair (ALAR) command:

az vm repair repair-button --button-command fstab

is not related to the Linux virtual machine, the /etc/fstab configuration, or the command syntax.

This issue is caused by a known bug in the Azure CLI vm-repair extension, which affects Azure CLI versions 2.77.0 and later. The issue is documented in the following GitHub report:

Reference: https://github.com/azure/azure-cli/issues/32408

Recommended Resolution:

Option 1: Use the Supported ALAR Workflow (Recommended)

The repair-button command is part of a preview implementation and is currently impacted by this bug. Instead, please use the officially supported ALAR workflow as documented by Microsoft

1. Create the repair VM

az vm repair create --resource-group <RG> --name <VM>

2. Run the ALAR repair:

az vm repair run --resource-group <RG> --name <VM> --run-on-repair --run-id linux-alar2 --parameters <name>

3.Restore the repaired OS disk:

az vm repair restore --verbose --resource-group <RG-NAME> --name <VM-NAME>

Please refer below documentations:

Use Azure Linux Auto Repair (ALAR) to fix a Linux VM

Troubleshoot Linux VM boot issues due to fstab errors

Option 2: Downgrade Azure CLI

As a workaround, you may downgrade Azure CLI to version 2.76.0 or earlier, where the repair-button command functions correctly:

Hope this helps! Please let me know if you have any queries.

Hello Everhartz, Stefan

Just checking if above response was helpful! Please let me know if you have any queries.

I can't confirm that the "az vm repair" command is suitable for making a Linux VM bootable again. "az vm repair" creates a CopyDisk, but does not start the repair mode. In addition, the repair process asks whether a "public VNET" is needed. If the answer to this question is no, an active public VNet is still required. The script aborts. My Workaround: I attached the CopyDisk created by az vm repair” as a data disk to another Linux VM, mounted the root partition, adjusted the fstab and attached it to the failed VM using SwapDisk. In my opinion, the documentation for "az vm repair” has to be validated.

You need to use the --subnet parameter with the full Resource ID of the subnet. —subnet is not a valid parameter for "az VM repair"

Workaround "az upgrade --version 2.76.0" Downgrade az-cli is not allowed. Only upgrades are allowed.