From 1cf78007b70c006ab39ea3476d0992eb4e762407 Mon Sep 17 00:00:00 2001 From: maries-msft <23018545+mries@users.noreply.github.com> Date: Sun, 18 May 2025 12:48:26 -0700 Subject: [PATCH 1/4] Update cloud-init-troubleshooting.md Removed chroot from "Step3: Collect & review VM logs". Chroot isn't a requirement to access an oskdisk filesystem on a rescue VM. Using such could make troubleshooting more complicated if you intend on pulling off the logs in the advent of a support case requirement. Added simply mount to the section providing a link to the instruction for collecting and/or examining logs both LVM and Raw. Added cloud-init.log and cloud.init-output.log as these are part of the initial investigation. Added to "deeper dive" section serial logs as they are very important to look at for provisioning failures. Provided link how to access boot diagnostics (serial log) in the portal. --- .../linux/cloud-init-troubleshooting.md | 23 ++++++++++--------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/articles/virtual-machines/linux/cloud-init-troubleshooting.md b/articles/virtual-machines/linux/cloud-init-troubleshooting.md index bde4bed8770..8b01538a5bd 100644 --- a/articles/virtual-machines/linux/cloud-init-troubleshooting.md +++ b/articles/virtual-machines/linux/cloud-init-troubleshooting.md @@ -88,27 +88,28 @@ While the VM is running, you will need the logs from the VM to understand why pr - [Serial Console](/troubleshoot/azure/virtual-machines/serial-console-grub-single-user-mode) -- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk using [chroot](/troubleshoot/azure/virtual-machines/chroot-environment-linux), which will allow you to collect these logs: +- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: ```bash -sudo cat /rescue/var/log/cloud-init* -sudo cat /rescue/var/log/waagent* -sudo cat /rescue/var/log/syslog* -sudo cat /rescue/var/log/rsyslog* -sudo cat /rescue/var/log/messages* -sudo cat /rescue/var/log/kern* -sudo cat /rescue/var/log/dmesg* -sudo cat /rescue/var/log/boot* +/rescue/var/log/waagent* +/rescue/var/log/syslog* +/rescue/var/log/rsyslog* +/rescue/var/log/messages* +/rescue/var/log/kern* +/rescue/var/log/dmesg* +/rescue/var/log/boot* +/rescue/ /var/log/cloud-init.log +/rescue//var/log/cloud-init-output.log ``` > [!NOTE] > Alternatively, you can create a rescue VM manually by using the Azure portal. For more information, see [Troubleshoot a Linux VM by attaching the OS disk to a recovery VM using the Azure portal](/troubleshoot/azure/virtual-machines/troubleshoot-recovery-disks-portal-linux). -To start initial troubleshooting, start with the cloud-init logs, and understand where the failure occurred, then use the other logs to deep dive, and provide additional insights. +To start initial troubleshooting, begin with the serial logs and cloud-init logs to understand where the failure occurred. Then use the other logs for a deeper dive to help provide additional insights. * /var/log/cloud-init.log * /var/log/cloud-init-output.log -* Serial/boot logs +* [Serial/boot logs](https://learn.microsoft.com/en-us/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) In all logs, start searching for "Failed", "WARNING", "WARN", "err", "error", "ERROR". Setting configuration to ignore case-sensitive searches is recommended. From dff11dab2866b318391f29ad7651a1f3bacd99d2 Mon Sep 17 00:00:00 2001 From: maries-msft <23018545+mries@users.noreply.github.com> Date: Sun, 18 May 2025 13:06:24 -0700 Subject: [PATCH 2/4] Update cloud-init-troubleshooting.md Removed Localization from links (en-us) --- articles/virtual-machines/linux/cloud-init-troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/virtual-machines/linux/cloud-init-troubleshooting.md b/articles/virtual-machines/linux/cloud-init-troubleshooting.md index 8b01538a5bd..e9bc4863a2e 100644 --- a/articles/virtual-machines/linux/cloud-init-troubleshooting.md +++ b/articles/virtual-machines/linux/cloud-init-troubleshooting.md @@ -88,7 +88,7 @@ While the VM is running, you will need the logs from the VM to understand why pr - [Serial Console](/troubleshoot/azure/virtual-machines/serial-console-grub-single-user-mode) -- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: +- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: ```bash /rescue/var/log/waagent* @@ -109,7 +109,7 @@ To start initial troubleshooting, begin with the serial logs and cloud-init logs * /var/log/cloud-init.log * /var/log/cloud-init-output.log -* [Serial/boot logs](https://learn.microsoft.com/en-us/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) +* [Serial/boot logs](https://learn.microsoft.com/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) In all logs, start searching for "Failed", "WARNING", "WARN", "err", "error", "ERROR". Setting configuration to ignore case-sensitive searches is recommended. From c3f83077bbfe7a4774009045f7b940427d1ccc9c Mon Sep 17 00:00:00 2001 From: Regan Downer Date: Thu, 19 Jun 2025 10:57:54 -0400 Subject: [PATCH 3/4] Apply suggestions from code review Co-authored-by: iamwilliew <109236489+iamwilliew@users.noreply.github.com> --- articles/virtual-machines/linux/cloud-init-troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/virtual-machines/linux/cloud-init-troubleshooting.md b/articles/virtual-machines/linux/cloud-init-troubleshooting.md index e9bc4863a2e..ae3861913be 100644 --- a/articles/virtual-machines/linux/cloud-init-troubleshooting.md +++ b/articles/virtual-machines/linux/cloud-init-troubleshooting.md @@ -88,7 +88,7 @@ While the VM is running, you will need the logs from the VM to understand why pr - [Serial Console](/troubleshoot/azure/virtual-machines/serial-console-grub-single-user-mode) -- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](https://learn.microsoft.com/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: +- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: ```bash /rescue/var/log/waagent* @@ -109,7 +109,7 @@ To start initial troubleshooting, begin with the serial logs and cloud-init logs * /var/log/cloud-init.log * /var/log/cloud-init-output.log -* [Serial/boot logs](https://learn.microsoft.com/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) +* [Serial/boot logs](azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) In all logs, start searching for "Failed", "WARNING", "WARN", "err", "error", "ERROR". Setting configuration to ignore case-sensitive searches is recommended. From f5935b8103350386ba7d72c351c153ecc626756c Mon Sep 17 00:00:00 2001 From: Regan Downer Date: Thu, 19 Jun 2025 11:05:27 -0400 Subject: [PATCH 4/4] Fix links --- articles/virtual-machines/linux/cloud-init-troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/virtual-machines/linux/cloud-init-troubleshooting.md b/articles/virtual-machines/linux/cloud-init-troubleshooting.md index ae3861913be..5d182bb19f5 100644 --- a/articles/virtual-machines/linux/cloud-init-troubleshooting.md +++ b/articles/virtual-machines/linux/cloud-init-troubleshooting.md @@ -88,7 +88,7 @@ While the VM is running, you will need the logs from the VM to understand why pr - [Serial Console](/troubleshoot/azure/virtual-machines/serial-console-grub-single-user-mode) -- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: +- [Run AZ VM Repair](/troubleshoot/azure/virtual-machines/repair-linux-vm-using-azure-virtual-machine-repair-commands) to attach and mount the OS disk ([*lvm*](/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk), [*no lvm*](/troubleshoot/azure/virtual-machines/linux/troubleshoot-recovery-disks-portal-linux#mount-the-attached-data-disk)), which will allow you to collect and examine these logs: ```bash /rescue/var/log/waagent* @@ -109,7 +109,7 @@ To start initial troubleshooting, begin with the serial logs and cloud-init logs * /var/log/cloud-init.log * /var/log/cloud-init-output.log -* [Serial/boot logs](azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) +* [Serial/boot logs](/azure/virtual-machines/boot-diagnostics#boot-diagnostics-view) In all logs, start searching for "Failed", "WARNING", "WARN", "err", "error", "ERROR". Setting configuration to ignore case-sensitive searches is recommended.