Skip to content

Commit 8e5cb0b

Browse files
authored
Merge pull request #9281 from naman-msft/docs-editor/linux-virtual-machine-cannot-s-1751922023
AB#6543: Update linux-virtual-machine-cannot-start-fstab-errors.md
2 parents 6ecad95 + e4db4ef commit 8e5cb0b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

support/azure/virtual-machines/linux/linux-virtual-machine-cannot-start-fstab-errors.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.topic: troubleshooting
1515
ms.workload: infrastructure-services
1616
ms.tgt_pltfrm: vm-linux
1717
ms.devlang: azurecli
18-
ms.date: 02/26/2025
18+
ms.date: 07/08/2025
1919
---
2020

2121
# Troubleshoot Linux VM boot issues due to fstab errors
@@ -108,6 +108,9 @@ If the VM serial console access isn't available, an alternative solution is to r
108108

109109
#### Use Azure Linux Auto Repair (ALAR)
110110

111+
> [!div class="nextstepaction"]
112+
> [Run in Linux](https://go.microsoft.com/fwlink/?linkid=2321930)
113+
111114
Azure Linux Auto Repair (ALAR) scripts are part of the VM repair extension described in [Use Azure Linux Auto Repair (ALAR) to fix a Linux VM](./repair-linux-vm-using-alar.md). ALAR covers the automation of multiple repair scenarios, including `/etc/fstab` issues.
112115

113116
The ALAR scripts use the repair extension `repair-button` to fix fstab issues by specifying `--button-command fstab`. This parameter triggers the automated recovery. Implement the following steps to automate fstab errors via the offline ALAR approach:

0 commit comments

Comments
 (0)