Knowledgebase

Server won't boot to LVE kernel after converion from AlmaLinux

If your server is not booting into the LVE (CloudLinux) kernel after conversion from AlmaLinux, it's likely that there's an issue with the bootloader configuration. Here are steps you can take to troubleshoot and resolve this issue:

  1. Check Bootloader Configuration:

    • Ensure that the bootloader (usually GRUB) is configured to boot into the LVE kernel. You can check the GRUB configuration file (/etc/default/grub) to make sure it points to the correct kernel.
  2. Update GRUB Configuration:

    • You may need to update the GRUB configuration to reflect the changes in the kernel. Use the grub2-mkconfig command to regenerate the configuration file:

      bash

 

    • sudo grub2-mkconfig -o /boot/grub2/grub.cfg
  • Verify Kernel Installation:

    • Make sure that the LVE kernel is installed on your system. You can use the following command to list installed kernels:

      bash
    • rpm -qa | grep kernel
  • Set Default Kernel:

    • You can set the default kernel to be used during boot by modifying the GRUB configuration file. Open /etc/default/grub and set the GRUB_DEFAULT parameter to the appropriate kernel entry (e.g., GRUB_DEFAULT=0 for the first entry).
  • Check for Errors:

    • During the boot process, pay attention to any error messages or warnings that are displayed. This may provide clues as to why the system is failing to boot.
  • Reinstall the LVE Kernel:

    • If the LVE kernel is not installed or appears to be corrupted, you may need to reinstall it.
  • Reconfigure Bootloader (GRUB):

    • In some cases, you may need to reinstall the GRUB bootloader. Use the following commands to reinstall GRUB:

      bash

 

    • sudo grub2-install /dev/sdX # Replace X with the appropriate drive sudo grub2-mkconfig -o /boot/grub2/grub.cfg
  1. Verify Boot Order in BIOS/UEFI:

    • Check the boot order in your system's BIOS/UEFI settings. Ensure that the correct boot device is selected.
  2. Access Recovery Mode:

    • If available, try booting into recovery mode or a different kernel (if one is available). This can help diagnose and potentially fix the issue.
  3. Contact Support:

    • If all else fails, it may be necessary to contact technical support, especially if this is a specific issue related to AlmaLinux or CloudLinux conversion.

Remember to be cautious when making changes to bootloader configurations, as incorrect settings can prevent your system from booting. Always back up important data and configurations before making any major changes.

 
  • 0 Users Found This Useful
Was this answer helpful?