| We moved this page to our Documentation Portal. You can find the latest updates here. |
Issue
My customer ran a 'yum update' on their VM and after they rebooted the VM, it will not come back up.
Environment
All OnApp Versions
Resolution
To boot the VM, the kernel should be rolled back to the previous version:
- Boot the VM in recovery mode via the OnApp UI.
- Go the VM console, login as root and the password is recovery.
- Once logged in, run:
fdisk -l
- Find the disk for the VM (for example, /dev/sdb1 20GB)
- Once you have found the disk, you can now mount it.
mount /dev/sdb1 /mnt
- Once the disk is mounted successfully, you can then go in and edit the bootloader file.
vi /mnt/boot/grub/grub.conf
- The chances are that the default one is set to 1. If so, try to change it to 0 and boot. Otherwise, choose the number of the kernel you want to boot. Note that 0 is the top kernel in the list.
- Unmount the disk:
umount /mnt
- Disconnect from the console and shutdown the VM from the OnApp UI.
- Boot it up and the VM should boot normally now.
Cause
Usually when this happens, the updated kernel is not a XEN kernel, so the VM is unable to boot under XEN. The kernel should be rolled back to the last usable version.