Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,764 questions
How can we connect to grub from serial console. As we see the serial console logs
Issues connecting the the Debain VM After Migrating to Azure
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 56.00000000000001%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Srinivasa Reddy
0
Reputation points
Hello Team,
We have migrated a Debian VM from On-Prem to Azure.
The local firewalls are cleared to connect to ssh on port 22
After migration VM starts up but can't access the VM in Azure.
Below are the logs in serial console attached to the VM
Could you assist with this.
/var/ASRLinuxGA-3936390c-746c-4b10-9671-71d07ef23e26/InstallLinuxGuestAgent.sh: line 29: systemctl: command not found
systemctl is not present on the system.
Using service commands to run script.
/var/ASRLinuxGA-3936390c-746c-4b10-9671-71d07ef23e26/InstallLinuxGuestAgent.sh: line 53: python3: command not found
Python3 is not installed on the VM.
Python 2.7.3
Python version is 2
Guest agent installation folder not found.
This should be second boot of VM since migration to Azure, hence skipping guest agent installation.
[ ok ] Starting ACPI services....
[....] Starting Tomcat servlet engine: tomcat7[ 43.087494] EXT4-fs (sda2): unable to read superblock
[ 43.122794] EXT2-fs (sda2): error: unable to read superblock
[ 43.149322] EXT3-fs (sda2): error: unable to read superblock
[ 43.408123] FAT-fs (sda2): bogus number of reserved sectors
[ 43.449569] FAT-fs (sda2): bogus number of reserved sectors
[ 43.489328] NTFS-fs error (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
[ 43.496096] NTFS-fs error (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[ 43.506565] NTFS-fs error (device sda2): ntfs_fill_super(): Not an NTFS volume.
[ 43.616193] qnx4: wrong fsid in superblock.
. ok
Starting vCon service...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
{count} votes
-
Srinivasa Reddy 0 Reputation points
2023-03-24T06:13:47.8533333+00:00 The issue is that I cant connect to the VM to install tools or fix issues. Local firewalls are cleared on the source VM that is migrated. Executing command from Portal is in executing script status and wont respond. The logs are from the serial console of the VM. I was able to hit the tomcat URL on the server accessing from a AVD in same VNET but connecting to the VM via ssh is a problem.
-
vipullag-MSFT 26,211 Reputation points2023-04-04T05:02:37.52+00:00 Hello Srinivasa Reddy We noticed your have rated low on the answer as not helpful. Thank you for taking time to share feedback.
This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case. If you don't have a support plan enabled on your subscription, I request you to send an email to AzCommunity@Microsoft.com with Subject as "Attn:Vikas" referencing this thread along with your subscription ID. I can then enable your subscription with a one-time free technical support. Once the issue is resolved, request you to post the resolution here for the benefit of community.
Sign in to comment
2 answers
Sort by: Most helpful
-
Srinivasa Reddy 0 Reputation points
2023-03-26T23:29:29.7166667+00:00 -
vipullag-MSFT 26,211 Reputation points
2023-03-27T08:36:07.5333333+00:00 Hello Srinivasa Reddy,
Thanks for sharing all the details.
If you are unable to connect to the VM through SSH and the command from the Azure Portal is not responding, you can try accessing the GRUB menu from the serial console to troubleshoot the issues. Here's how:
- Go to the Azure portal and navigate to the VM that you want to troubleshoot. Click on the "Connect" button.
- In the "Connect to virtual machine" pane, select "Serial console". Wait for the console to load. You should see a login prompt.
- Log in to the VM using your credentials.
- When the GRUB menu appears during the boot process, use the arrow keys to select the Debian kernel that you want to boot into. Press the "e" key to edit the selected entry.
- Navigate to the line that starts with "linux /boot/vmlinuz-3.2.0-4-amd64" and append "init=/bin/bash" to the end of the line.
- Press "Ctrl-X" or "F10" to boot into the modified entry.
- The system will boot into a root shell prompt, where you can perform troubleshooting steps or make necessary changes.
From the root shell prompt, you can try installing the necessary tools and fixing the issues preventing you from connecting to the VM.
If you're still unable to connect to the VM after performing these steps, you may need to create a new VM based on a Debian image in Azure and then attach the disk from the problematic VM to the new VM as a data disk. Once you have attached the disk, you can mount it and perform the recommended steps to troubleshoot the issues with the VM.
Hope this helps.
- Go to the Azure portal and navigate to the VM that you want to troubleshoot. Click on the "Connect" button.
Sign in to comment -
-
vipullag-MSFT 26,211 Reputation points
2023-03-29T10:20:31.3366667+00:00 Hello Srinivasa Reddy
Welcome to Microsoft Q&A Platform, thanks for posting your query here.
Sorry to hear that you're having issues with your Debian VM after Migrating to Azure.
Based on the logs provided, there seem to be several issues with the migrated Debian VM.
- The first error message is related to the missing
systemctlcommand. Check if the Debian version being used on the VM is an older version that doesn't includesystemdby default. If it's an older version, try using theservicecommand to start or stop services instead of usingsystemctl. - The second error message indicates that Python3 is not installed on the VM. This could be an issue if any scripts or applications on the VM rely on Python3. Install Python3 on the VM using the
sudo apt-get install python3command. - Run a file system check on the root partition by running the
sudo fsck /dev/sda2command. - The last message indicates that the VM's grub configuration file has been generated successfully. However, it doesn't provide any information about the status of the VM's network configuration. Check the network interface configuration on the VM by running the
ifconfigcommand.
If you are unable to connect to the VM through SSH, you can try accessing the VM's console to perform the recommended steps.
Hope these help.
- The first error message is related to the missing