Merge pull request #9725 from ryanberg-aquent/CI-7286-linux-specific-updates

ryanberg-aquent · web-flow · commit 55ac09f1df99 · 2025-09-16T10:37:53.000-10:00
AB#7286 - Linux-specific updates
diff --git a/support/azure/virtual-machines/linux/boot-error-troubleshoot-linux.md b/support/azure/virtual-machines/linux/boot-error-troubleshoot-linux.md
@@ -11,7 +11,7 @@ ms.topic: troubleshooting
 ms.tgt_pltfrm: vm-linux
 ms.custom: sap:My VM is not booting, linux-related-content
 ms.workload: infrastructure
-ms.date: 03/10/2023
+ms.date: 09/15/2025
 ms.author: divargas
 ---
 # Troubleshoot Azure Linux virtual machine boot errors
diff --git a/support/azure/virtual-machines/linux/chroot-logical-volume-manager.md b/support/azure/virtual-machines/linux/chroot-logical-volume-manager.md
@@ -11,7 +11,7 @@ ms.collection: linux
 ms.topic: troubleshooting
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 03/10/2023
+ms.date: 09/15/2025
 ms.author: divargas
 ---
 # Troubleshoot Azure Linux VM when there's no access to Azure Serial Console and the disk layout uses Logical Volume Manager
diff --git a/support/azure/virtual-machines/linux/cloud-init-deployment-delay.md b/support/azure/virtual-machines/linux/cloud-init-deployment-delay.md
@@ -3,7 +3,7 @@ title: Cloud-init-enabled VM takes a long time to start up
 description: Troubleshoot a cloud-init-enabled Azure Virtual Machine deployment that takes more than 120 seconds to start up.
 editor: v-jsitser
 ms.service: azure-virtual-machines
-ms.date: 02/03/2022
+ms.date: 09/15/2025
 ms.reviewer: srijangupta, v-leedennis
 ms.custom: sap:Cannot create a VM
 ---
diff --git a/support/azure/virtual-machines/linux/cloud-init-support-linux-vms.md b/support/azure/virtual-machines/linux/cloud-init-support-linux-vms.md
@@ -1,7 +1,7 @@
 ---
 title: Azure cloud-init support for Linux VMs
 description: This article explains the support scenario for cloud-init in Azure. 
-ms.date: 10/10/2020
+ms.date: 09/15/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Extensions not operating correctly, linux-related-content
 ms.collection: linux
diff --git a/support/azure/virtual-machines/linux/create-swap-file-linux-vm.md b/support/azure/virtual-machines/linux/create-swap-file-linux-vm.md
@@ -1,7 +1,7 @@
 ---
 title: Create a SWAP file for an Azure Linux VM
 description: Describes how to create a SWAP file for an Azure Linux VM.
-ms.date: 10/12/2023
+ms.date: 09/15/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
 ms.collection: linux
diff --git a/support/azure/virtual-machines/linux/linux-fulldisk-boot-error.md b/support/azure/virtual-machines/linux/linux-fulldisk-boot-error.md
@@ -5,7 +5,7 @@ author: pagienge
 ms.author: pagienge
 ms.reviewer: v-leedennis
 ms.topic: troubleshooting
-ms.date: 09/01/2023
+ms.date: 09/15/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:My VM is not booting, linux-related-content
 ms.collection: linux
diff --git a/support/azure/virtual-machines/linux/linux-hyperv-issue.md b/support/azure/virtual-machines/linux/linux-hyperv-issue.md
@@ -5,7 +5,7 @@ author: saimsh-msft
 ms.author: saimsh
 ms.reviewer: divargas
 ms.topic: troubleshooting
-ms.date: 10/11/2022
+ms.date: 09/15/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:My VM is not booting, linux-related-content
 ms.collection: linux
@@ -29,7 +29,7 @@ To identify if your VM fails to boot due to missing Hyper-V drivers, use [Azure
 
 ## Before you troubleshoot
 
-To troubleshoot [Scenario 1: Network Hyper-V driver is disabled](#network-hyperv-disabled) and [Scenario 2: NIC mac address is changed or doesn't match](#macaddress-issue), you need [serial console](./serial-console-linux.md) access for your Linux VM.
+To troubleshoot [Scenario 1: Network Hyper-V driver is disabled](#network-hyperv-disabled) and [Scenario 2: NIC media access control (MAC) address is changed or doesn't match](#macaddress-issue), you need [serial console](./serial-console-linux.md) access for your Linux VM.
 
 If you don't have serial console access, follow the [offline approach](./repair-linux-vm-using-azure-virtual-machine-repair-commands.md) to access the contents of the problematic OS disk from a rescue virtual machine. Access to Azure CLI or [Azure Cloud Shell](https://shell.azure.com) is required for the offline approach.
 
@@ -131,7 +131,7 @@ Always take a backup of the original initial RAMdisk image to facilitate the rol
 
 4. Once the changes are applied, perform an automatic OS disk swap with the original VM and reboot the system by using the `az vm repair restore` command.
 
-## <a id="macaddress-issue"></a>Scenario 2: NIC MAC address is changed or doesn't match
+## <a id="macaddress-issue"></a>Scenario 2: NIC media access control (MAC) address is changed or doesn't match
 
 If the Network Interface Card MAC address is changed or doesn't match within the OS configuration, you won't be able to SSH to the VM because the networking services are unavailable. You're still able to sign in via [serial console](../windows/serial-console-overview.md) from the Azure portal. Errors that are similar to the ones in [Scenario 1: Network Hyper-V driver is disabled](#network-hyperv-disabled) are displayed.
 
diff --git a/support/azure/virtual-machines/linux/linux-image-provisioning-agent-update-awareness.md b/support/azure/virtual-machines/linux/linux-image-provisioning-agent-update-awareness.md
@@ -1,7 +1,7 @@
 ---
 title: Linux Image Provisioning Agent update awareness
 description: Provides the update awareness and frequently asked questions about Linux Image Provisioning Agent.
-ms.date: 10/10/2020
+ms.date: 09/15/2025
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Extensions not operating correctly, linux-related-content
 ms.collection: linux
diff --git a/support/azure/virtual-machines/linux/linux-recovery-cannot-start-file-system-errors.md b/support/azure/virtual-machines/linux/linux-recovery-cannot-start-file-system-errors.md
@@ -13,7 +13,7 @@ ms.topic: troubleshooting
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: azurecli
-ms.date: 05/20/2025
+ms.date: 09/15/2025
 ms.author: jarrettr
 ms.reviewer: maries, v-weizhu
 ---
@@ -41,7 +41,7 @@ EXT4-fs warning (device sda1): ext4_clear_journal_err:4531: Filesystem error rec
 EXT4-fs warning (device sda1): ext4_clear_journal_err:4532: Marking fs in need of filesystem check.
 ```
 
-### Example 2: Fail to mount ext Logical Volume Manager (LVM) device
+### Example 2: Fail to mount ext4 Logical Volume Manager (LVM) device
 
 ```output
 [   14.382472] EXT4-fs error (device dm-0): ext4_iget:4398: inode #8: comm mount: bad extra_isize 4060 (inode size 256)
diff --git a/support/azure/virtual-machines/linux/oom-swap-file-linux-vm.md b/support/azure/virtual-machines/linux/oom-swap-file-linux-vm.md
@@ -1,7 +1,7 @@
 ---
 title: Out of memory error occurs in Linux Azure virtual machine
 description: This article helps you understand how to fix out of memory errors by adding swap space in Linux Azure virtual machines.
-ms.date: 10/27/2023
+ms.date: 09/15/2025
 ms.reviewer: azurevmlnxcic, v-denlee
 ms.service: azure-virtual-machines
 ms.custom: sap:VM Admin - Windows (Guest OS), linux-related-content
diff --git a/support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md b/support/azure/virtual-machines/linux/repair-linux-vm-using-azure-virtual-machine-repair-commands.md
@@ -13,7 +13,7 @@ ms.topic: troubleshooting
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: azurecli
-ms.date: 04/29/2025
+ms.date: 09/15/2025
 ms.author: jarrettr
 ---
 
@@ -30,7 +30,7 @@ If your Linux virtual machine (VM) in Azure encounters a boot or disk error, you
 > * Only one script may run at a time.
 > * A running script cannot be canceled.
 > * The maximum time a script can run is 90 minutes, after which it will time out.
-> * Do not modify the tags that are created on the repair VM. The tags are neccessary for the restore command to function correctly.
+> * Do not modify the tags that are created on the repair VM. The tags are necessary for the restore command to function correctly.
 > * For VMs using Azure Disk Encryption, only managed disks encrypted with single pass encryption (with or without KEK) are supported.
 > * The VM Contributor role doesn't provide enough permissions to run the scripts, as they require permissions to read, write, and delete resources in the resource group that includes the target VM. Therefore roles such as Contributor or Owner at that resource group level is required.
 
diff --git a/support/azure/virtual-machines/linux/reset-password.md b/support/azure/virtual-machines/linux/reset-password.md
@@ -12,7 +12,7 @@ ms.collection: linux
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 09/15/2025
 ms.reviewer: msaenzbo, divargas, v-six
 ---
 
@@ -55,7 +55,7 @@ You can use the [serial console](serial-console-linux.md) to reset the `admin us
 
 2. Make sure that password authentication is enabled on the OpenSSH server if you try to log in to the server by using the SSH and password authentication.
 
-    1. Check whether the `PasswordAuthentitcation` value is set to `yes` or `no` in `/etc/ssh/sshd_config` by running the following command:
+    1. Check whether the `PasswordAuthentication` value is set to `yes` or `no` in `/etc/ssh/sshd_config` by running the following command:
 
         ```bash
         egrep "^PasswordAuthentication" /etc/ssh/sshd_config
@@ -116,7 +116,7 @@ You can run the [vm repair](/cli/azure/vm/repair) commands to create a repair VM
 
 3. Make sure that password authentication is enabled on the OpenSSH server if you try to log in to the server by using the SSH and password authentication.
 
-    1. Check whether the `PasswordAuthentitcation` value is set to `yes` or `no` in `/etc/ssh/sshd_config` by running the following command:
+    1. Check whether the `PasswordAuthentication` value is set to `yes` or `no` in `/etc/ssh/sshd_config` by running the following command:
 
         ```bash
         egrep "^PasswordAuthentication" /etc/ssh/sshd_config
diff --git a/support/azure/virtual-machines/linux/resolve-failed-start-switch-root-azure-linux-vm.md b/support/azure/virtual-machines/linux/resolve-failed-start-switch-root-azure-linux-vm.md
@@ -9,7 +9,7 @@ tags: top-support-issue
 ms.custom: sap:My VM is not booting, linux-related-content
 ms.service: azure-virtual-machines
 ms.topic: troubleshooting
-ms.date: 08/19/2021
+ms.date: 09/15/2025
 ms.author: tibasham
 ---
 # Resolve "Failed to start Switch Root" for an Azure Linux VM
@@ -42,13 +42,13 @@ If you're unable to use the Azure Serial Console section, proceed to the [Offlin
 
 2. Select the entry for the rescue kernel.
 
-3. Copy the `kernelopts` value from the `grubenv` file. The path of the `grubenv` file in Linux can vary depending on the distribution and configuration of the system. It is commonly located at `/boot/efi/EFI/redhat/grubenv` or `/boot/grub2/gubenv`.
+3. Copy the `kernelopts` value from the `grubenv` file. The path of the `grubenv` file in Linux can vary depending on the distribution and configuration of the system. It is commonly located at `/boot/efi/EFI/redhat/grubenv` or `/boot/grub2/grubenv`.
 
 
    Example:
 
    ```console
-   cat /boot/grub2/gubenv
+   cat /boot/grub2/grubenv
    ```
 
 4. Edit the desired boot entry from `/boot/loader/entries`:  
@@ -86,7 +86,7 @@ If you're unable to access the VM using the Azure Serial Console, then the repai
 
    `mount /dev/sdc15 /repair/efi/`
 
-7. Copy the `kernelopts` value from the `grubenv` file. The path of the `grubenv` file in Linux can vary depending on the distribution and configuration of the system. It is commonly located at `/boot/efi/EFI/redhat/grubenv` or `/boot/grub2/gubenv`.
+7. Copy the `kernelopts` value from the `grubenv` file. The path of the `grubenv` file in Linux can vary depending on the distribution and configuration of the system. It is commonly located at `/boot/efi/EFI/redhat/grubenv` or `/boot/grub2/grubenv`.
 
    Example:
 
diff --git a/support/azure/virtual-machines/linux/troubleshoot-recovery-disks-linux.md b/support/azure/virtual-machines/linux/troubleshoot-recovery-disks-linux.md
@@ -12,7 +12,7 @@ ms.custom: sap:VM Admin - Linux (Guest OS), devx-track-azurecli, linux-related-c
 ms.topic: troubleshooting
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 10/11/2021
+ms.date: 09/15/2025
 ms.author: jarrettr
 ---
 
diff --git a/support/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux.md b/support/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux.md
@@ -12,7 +12,7 @@ ms.topic: troubleshooting
 ms.tgt_pltfrm: vm-linux
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
 ms.workload: infrastructure
-ms.date: 10/11/2021
+ms.date: 09/15/2025
 ms.author: jarrettr
 ---
 
@@ -43,7 +43,7 @@ Examine the boot diagnostics and VM screenshot to determine why your VM is not a
 
 Select your VM in the portal and then scroll down to the **Support + Troubleshooting** section. Click **Boot diagnostics** to view the console messages streamed from your VM. Review the console logs to see if you can determine why the VM is encountering an issue. The following example shows a VM stuck in maintenance mode that requires manual interaction:
 
-:::image type="content" source="media/troubleshoot-recovery-disks-portal-linux/boot-diagnostics-console-logs.png" alt-text="Screenshot of viewing the V M boot diagnostics console logs.":::
+:::image type="content" source="media/troubleshoot-recovery-disks-portal-linux/boot-diagnostics-console-logs.png" alt-text="Screenshot of viewing the VM boot diagnostics console logs.":::
 
 You can also click **Screenshot** across the top of the boot diagnostics log to download a capture of the VM screenshot.
 
@@ -87,7 +87,7 @@ To create a disk from the snapshot, follow these steps:
     #Provide the name of the snapshot that will be used to create Managed Disks
     $snapshotName = 'mySnapshot' 
     
-    #Provide the name of theManaged Disk
+    #Provide the name of the Managed Disk
     $diskName = 'newOSDisk'
     
     #Provide the size of the disks in GB. It should be greater than the VHD file size. In this sample, the size of the snapshot is 127 GB. So we set the disk size to 128 GB.
@@ -127,7 +127,7 @@ For the next few steps, you use another VM for troubleshooting purposes. After y
 > [!NOTE]
 > The following examples detail the steps required on an Ubuntu VM. If you are using a different Linux distro, such as Red Hat Enterprise Linux or SUSE, the log file locations and `mount` commands may be a little different. Refer to the documentation for your specific distro for the appropriate changes in commands.
 
-1. SSH to your troubleshooting VM using the appropriate credentials. If this disk is the first data disk attached to your troubleshooting VM, it is likely connected to `/dev/sdc`. Use `dmseg` to list attached disks:
+1. SSH to your troubleshooting VM using the appropriate credentials. If this disk is the first data disk attached to your troubleshooting VM, it is likely connected to `/dev/sdc`. Use `dmesg` to list attached disks:
 
     ```bash
     dmesg | grep SCSI
@@ -182,15 +182,15 @@ Once your errors are resolved, detach the existing virtual hard disk from your t
 
 2. Now detach the virtual hard disk from the VM. Select your VM in the portal and click **Disks**. Select your existing virtual hard disk and then click **Detach**:
 
-    :::image type="content" source="media/troubleshoot-recovery-disks-portal-linux/detach-disk.png" alt-text="Screenshot to detach the virtual hard disk from the V M.":::
+    :::image type="content" source="media/troubleshoot-recovery-disks-portal-linux/detach-disk.png" alt-text="Screenshot to detach the virtual hard disk from the VM.":::
 
     Wait until the VM has successfully detached the data disk before continuing.
 
 ## Swap the OS disk for the VM
 
 Azure portal now supports change the OS disk of the VM. To do this, follow these steps:
 
-1. Go to [Azure portal](https://portal.azure.com). Select **Virtual machines** from the sidebar, and then select the VM that has problem.
+1. Go to [Azure portal](https://portal.azure.com). Select **Virtual machines** from the sidebar, and then select the VM that has a problem.
 1. On the left pane, select **Disks**, and then select **Swap OS disk**.
 
     :::image type="content" source="media/troubleshoot-recovery-disks-portal-linux/swap-os-disk.png" alt-text="Screenshot of the Swap O S Disk option in the Azure portal.":::
diff --git a/support/azure/virtual-machines/linux/troubleshoot-ssh-permissions-too-open.md b/support/azure/virtual-machines/linux/troubleshoot-ssh-permissions-too-open.md
@@ -11,7 +11,7 @@ ms.collection: linux
 ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.topic: troubleshooting
-ms.date: 12/30/2021
+ms.date: 09/15/2025
 ms.author: jarrettr
 ---
 # Can't SSH to Azure Linux VM because permissions are too open
@@ -26,7 +26,7 @@ You can't connect to your Microsoft Azure Linux virtual machine (VM) by using Se
 >sshd: error: It is required that your private key files are NOT accessible by others.</br>
 >sshd: error: This private key will be ignored.</br>
 >sshd: error: key_load_private: bad permissions</br>
->shd: error: Could not load host key: /etc/ssh/sshKeyName
+>sshd: error: Could not load host key: /etc/ssh/sshKeyName
 
 ## Cause
 
