Grub did not detect second operating system

I installed 19.10 alongside 18.04.03 When I restarted after the installation, and again after a second restart, the 1804 installation. This is a UEFI installation.

Under Budgie what is the best way to update grub?


The 18.04 partition is still there.

Its the same for all ubuntu flavours


Thanks for the reply.

I ran it and it found 18.04 but the computer rebooted into 19.04 without giving me a choice of operating systems.

Should I try boot repair?

sudo update-grub
[sudo] password for gary19:
Sourcing file /etc/default/grub' Sourcing file /etc/default/grub.d/init-select.cfg’
Generating grub configuration file …
Found linux image: /boot/vmlinuz-5.3.0-19-generic
Found initrd image: /boot/initrd.img-5.3.0-19-generic
Found linux image: /boot/vmlinuz-5.3.0-18-generic
Found initrd image: /boot/initrd.img-5.3.0-18-generic
Found Ubuntu 18.04.3 LTS (18.04) on /dev/sda2
Adding boot menu entry for EFI firmware configuration


I use refind for my EFI based systems that have multiple OS. Works nicely.

  • Ed

Hi Ed
That made matters worse. Now I get some sort of policy violation message (twice actually) before it boots and as before it boots only into 19.10. Is there a way to uninstall refind?



Hi Gary,

I’ve never needed to, though I’ve found a reinstall of the base Ubuntu version sets the corresponding version of grub as the boot manager.

What are you seeing when you restart the computer? The refind dialog is what you should see, with both Ubuntu versions as choices to select for the boot loader. I assume selecting 19.10 boots normally. What happens if you select 19.04?

  • Ed

I get a blue screen with a message saying there is a policy violation, asks you say ok to that, does it again, then boots into 19.10. There is no refind dialogue.


You haven’t said what kind of hardware you have or what OS you loaded refind with, so there’s a bit of guessing on my side.

Start by determining the boot mode, looking at your firmware setup screen. Make sure you’re in EFI boot mode, and that there is no protection on preventing you from booting a non-windows or OSX operating system (yeah, I know, but check the settings anyway).

There are lots of documentation pages, likely linked off of the above that should tell you how to replace refind if you need to.

  • Ed

Here’s the main refind page. It should have links to anything you’ll need.

My computer is a Lenovo 14 flex intel 1-3 with an SSD. I am in EfI boot mode. In the boot order refind is first then “ubuntu.” I can only boot into 19.10 so that is what I used to install refind.

I looked at the main refind page. I could not identify anything that would help other than he invited people to drop him a line if in need.

I have dual booted before. I had 18.04 and 1904. 1910 is installed to replace 1904, although I did a clean install of just 18.04 first. I made the 1904 partition a bit too small so I needed a clean disk to work with. The first time i loaded 1904 I had this very same problem but only once, then it gave me the choice of OS.

Ox1A security violation is the message I get when I boot. I get that message twice, I hit enter each time. Boot proceeds the second time, although slower than normal, it gets me there.


Strange. My newest machine is a recent Lenovo. They do have a lot of security options in the firmware settings, but I’d be hard-pressed to determine which might be relevant to your situation. My gut is telling me that’s the source of the issue.

Sorry to have complicated your situation.

  • Ed

Did you get any odd informational messages when you ran the refind install script?

Almost sounds like the 19.10 install overwrote the boot signature for 18.04.

I do not recall any error messages. I was expecting a console and never got one.


Here’s something to try in order to see whether your 18.04 boot signature is there. Run the following command, and look at the listed boot order, then look at the corresponding entries. Mine below shows Windows, Ubuntu 19.10 and refind, preceded by the order, which starts with refind. You’ll only need to look at this first part of the output to see whether it was recognized as available to boot.

➜ ~ efibootmgr -v

BootCurrent: 0002

Timeout: 0 seconds

BootOrder: 0002,0001,0000,0018,0019,001A,001B,001C,001D,001E,001F,0020,0021,0026

Boot0000* Windows Boot Manager HD(1,GPT,b81b8f5b-63d3-4088-8ad4-378cf1937069,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}…)…

Boot0001* ubuntu HD(1,GPT,b81b8f5b-63d3-4088-8ad4-378cf1937069,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

Boot0002* rEFInd Boot Manager HD(1,GPT,b81b8f5b-63d3-4088-8ad4-378cf1937069,0x800,0x82000)/File(\EFI\refind\refind_x64.efi)

In this document read the section on using efubootmgr to change the boot order. As in my last msg it should allow you to identify what is available, and to adjust the order, even if that only means booting directly into 19.10 without the security violation message.


This is the result. I am still trying to figure it out

efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0002,0001,0016,0017,0013,0014,0015,0018,0000
Boot0000* Windows Boot Manager HD(2,GPT,a95dd30f-0647-4c6d-9a6f-83bea378428d,0x1f4800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}…
Boot0001* ubuntu HD(1,GPT,fd4ae1e4-1484-4e78-936c-0e971312e0f9,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* rEFInd Boot Manager HD(1,GPT,fd4ae1e4-1484-4e78-936c-0e971312e0f9,0x800,0x100000)/File(\EFI\refind\shimx64.efi)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012 Diagnostic Splash FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0014* ATA HDD: SanDisk SDSSDA120G PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)…bYVD.A…O.
ATAPI CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0016* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0017* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* PCI LAN: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0019* Lenovo Recovery System PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(3,GPT,8b708773-a06e-4c58-8350-d98bc2c65368,0x276800,0x1f4000)/File(\EFI\Microsoft\Boot\lrsBootMgr.efi)


Looks like there’s only boot programs for refind, one version of Ubuntu, and Windows (which is likely uninstalled). Check in the Lenovo’s setup program (hit “enter” while powering up) as to whether “secure boot” is enabled. If so, disable it. That should get you to running refind without the policy failure.

If at that point there is only one ubuntu entry, then the 19.10 installation probably overwrote the 18.04 one.

BTW that last link on dealing with “bootloader coups” has a lot of good and likely relevant information in it.

Good luck!

Without the -v it is easier to figure out

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0002,0001,0016,0017,0013,0014,0015,0018,0000
Boot0000* Windows Boot Manager
Boot0001* ubuntu
Boot0002* rEFInd Boot Manager
Boot0010 Setup
Boot0011 Boot Menu
Boot0012 Diagnostic Splash
Boot0013* USB FDD:
Boot0014* ATA HDD: SanDisk SDSSDA120G
Boot0015* ATAPI CD:
Boot0016* USB HDD:
Boot0017* USB CD:
Boot0018* PCI LAN:
Boot0019* Lenovo Recovery System

So ‘ubuntu’ is first. Would that be the problem? rEFind should be first, no?