As you probably know, GRUB2 is default boot loader for most Linux operating systems. GRUB boot loader is the first program that runs when the computer starts.
It is responsible for loading and transferring control to the operating system Kernel.
The problem can also occur alongside a BIOS or Grub update.
This article shows you how to make the startup entries again.
What is changed: - Menu entries name changed to GNU/Linux - Advanced options had returned -Plymouth splash screen from "quiet splash" seems to be changed (not certain but am seeing lines of text after selecting OS and on power off) What is not changed: - Grub menu header - Color options for grub menu What i have tried: - Going through the settings file, /etc/default/grub , /etc/grub.d/10_Linux to see if there was any changes and/or extra files in the folder.
The following example illustrates a case where after the Grub update there are missing UEFI boot images: [email protected]:~$ sudo efibootmgr -v Boot Current: 0001 Timeout: 10 seconds Boot Order: 0001,0000,0002,0003,0005 Boot0000* ubuntu HD(1,800,f3800,caff37a0-8078-4b24-956e-79eb5e33631f)File(\EFI\ubuntu\grubx64.efi) Boot0001* ubuntu2 HD(1,800,f3800,957eb480-5f2f-409e-95b8-62c38a3305c0)File(\EFI\ubuntu2\grubx64.efi) [email protected]:~$ sudo apt-get update; apt-get upgrade [...] Reading state information...
Done The following packages will be upgraded: apt apt-transport-https apt-utils grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub2-common libapt-inst1.4 libapt-pkg4.12 libcib1 libcrmcluster1 libcrmcommon2 libpe-rules2 libpe-status3 libpengine3 libstonithd1 libtransitioner1 libudev0 mdadm pacemaker udev 22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Found linux image: /boot/vmlinuz-3.2.0-51-generic Found initrd image: /boot/initrd.img-3.2.0-51-generic [...] Found memtest86 image: /boot/memtest86 No volume groups found Adding boot menu entry for EFI firmware configuration done Setting up grub-efi (1.99-21ubuntu3.10) ...
This process involved updating the Droplet's kernel on the server and then selecting the matching kernel from the Digital Ocean control panel.
This was a quick and easy process, but required users to use the control panel for the actual kernel swap.