For more information, see How to restore Azure VM data in Azure portal.īoot system on older kernel version Use Azure serial console If there are important kernel-related contents, the entire /boot partition, or other important contents are missing, and they can't be recovered, we recommend restoring the VM from a backup.
Validate if the VM is able to boot up by taking a look at the Azure serial console or by trying to connect to the VM. For more information, see Step 5 in Repair a Linux VM by using the Azure Virtual Machine repair commands. Run the az vm repair restore command to swap the repaired OS disk with the original OS disk of the VM. Unmount the copy of the file systems from the rescue/repair VM. For more information, see Troubleshoot a Linux VM by attaching the OS disk to a recovery VM using the Azure portal.Īfter the kernel-related boot issue is resolved, perform the following actions: Kernel panic - not syncing: Attempted to kill init!Īfter the kernel-related boot issue is resolved, restart the VM so it can boot over the latest kernel version.Īlternatively, you can create a rescue VM manually by using the Azure portal. Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0). Go to the corresponding section to resolve the specific kernel-related boot issue: For more information, see Boot system on older kernel version. Use the Azure serial console to interrupt your VM at the GRUB menu and select any previous kernel to boot it up. Identify the specific kernel-related boot issue. 
For more information, see Virtual machine serial console for Linux. Make sure you meet the necessary prerequisites for your distribution.
It allows you to directly fix the issue without having to present the system disk to a recovery VM. The serial console is the fastest method to resolve the boot issue. If you have a recent backup of the VM, restore the VM from the backup to fix the boot issue.
0 kommentar(er)
