Skip to main content

My Grub Nightmare with UEFI boot on my lovely OVH server (set default Kernel)



  • Alexandre Parubochyi

    You may find useful the following article:
  • Alexandre Parubochyi

    The issue is related to EFI configuration of OVH servers. Start by performing the steps from the following article:

    After that, execute:

    yum install grub2* shim

    Set GRUB_DISABLE_LINUX_UUID=false in /etc/default/grub (This is a file change, not a command.)

    cp /boot/grub2/grubenv /boot/efi/EFI/centos/grubenv
    grub2-mkconfig -o /etc/grub2.cfg
    grub2-mkconfig -o /etc/grub2-efi.cfg
    yum reinstall kernel-3.10.0-962.3.2.lve1.5.38.el7.x86_64

    Then you need to make sure that the CloudLinux OS kernel persists in the configuration:


    grubby --default-kernel
  • Nicolas
    Hello Alexandre !

    And thanks a lot for these interesting command lines (second part) !

    For the first advice (first link), I have one regret…

    I cannot find the purpose of this additional configuration…

    The article is just saying :

    Running CloudLinux 7 with OVH server. Servers from OVH can require additional configurations after converting to CloudLinux 7.

    (my level on sysadmin is the culprit)

    There, on the article, some operations are marked as optional and some not, but with not much details about the reason…

    I confess… I am scared about doing configuration I don't fully understand on a production server.

    I've chosen cPanel & CloudLinux as my long term champions to keep things easy for me, and crystal clear about the command lines I allow me to run with root privileges. I believe it is so easy to dirty a server installation with only single mistake.

    The configuration in the article seems to affect network, and/or partitions… But, now, it seems my server works with that since I use it for 5 months now ? (my thoughts)

    Anyway, thank you for the second part (/etc/grub2-efi.cfg, yum reinstall kernel).

    It is so much helpful ! I will keep it in mind and it will help me a lot in the futur. I plan to reboot my server by myself each week at night time to check everything still works fine, then, I will use your command lines for the next troubleshooting.

    What do you think about that…

    Regarding my long post, do you think I was able to fix my issue by modifying


    And selecting there :

    instead of GRUB_DEFAULT=saved


    grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

    Is it looks clean for you to do that ? Or why ? And, is it enough now since, I think… the kernel will update on the slot number 1 and stay at number 1 forever ?

    Thanks again for your precious help ! So much appreciate to not feel alone in this jungle and to know we can rely on CloudLinux Community and support.

Please sign in to leave a comment.