Tutorials/Tips

Solution to grub-efi-amd64-signed package failed to install into target

The ‘grub-efi-amd64-signed’ package failed to install into /target/ error message, shown in Figure 1, is one I got when attempting to install KDE Neon alongside Windows 10 on a friend’s HP 15-ba009dx notebook. This post offers the solution.

GRUB failed to install
Figure 1: Error message when GRUB failed to install

In instances when an installer crashes, you usually get more detailed messages on the bug report screen, but not in this case. So in an attempt to find a clue why GRUB failed to install, I restarted the installer from the command line, hoping that some messages will be printed on the command line when the installer crashes. But that didn’t happen.

GRUB error
Figure 2: No additional information provided why the install crashed

After several attempts of the above, I finally decided to look in the system log file, that is, in /var/log/syslog. Grep-ing for anything related to GRUB returned lines like the ones below:

Related Post:  5 things to do that will boost the security profile of your smartphone

That gave me a clue. The installer needed to install something that was not on the installation image. But it couldn’t. And the reason it couldn’t was because the computer I was installing it on was not connected to the Internet. If it did, the installer would have been able to find the package it needed from a remote repository, provided I selected the options shown in Figure 3.

KDE Neon
Figure 3: Option to download updates while installing KDE Neon

So that’s the solution to the The ‘grub-efi-amd64-signed’ package failed to install into /target/ error message. Make sure that the target computer is connected to the Internet, and that you enabled the option (shown in Figure 3) to download updates during the installation.

Please share:
Tags:

We Recommend These Services

Register now for Big Data & AI Conference, international Big Data and AI conference in Dallas, TX (USA), June 27 - 29, 2019

Reasons to use control panel for your server

Register for the End-to-end Machine Learning with TensorFlow on Google Cloud Platform workshop. It will be conducted by the manager of Google's Cloud AI Advocacy team

Launch an SSD VPS in Europe, USA, Asia & Australia on Vultr's KVM-based Cloud platform starting at $5:00/month (15 GB SSD, 768 MB of RAM).


18 Comments

  1. It’s work for me.
    OS: Ubuntu Desktop 18.10
    1. During Live-OS, must do some delete default route and setting default route.
    2. And make sure can ping 8.8.8.8 and can ping http://www.google.com
    3. Click installer then to install OS.

    But in my PXE Server, it’s not Non-Internet environment.
    So, I need to find another methods to solve the problem.

  2. Nope, machine is connected to the internet, I can bring up webpages, etc. STILL fails with this message.

  3. Sarah Corriher

    This worked. Thank you!

  4. Solve the problem perfectly for 18.04.01 on i7-8700K with Samsung 860 EVO. It seems to be a driver problem?

  5. Works fro me, thanks.

  6. Artur Silva

    Not working man

  7. Ritej Gerrard

    Thank you for your post. It worked for me.

  8. vidyadhara b

    I am trying to install ubuntu 18.04 on an asus x200la laptop. ubuntu 14.04 worked without any hitches.

  9. vidyadhara b

    This did not work for me. I am connected to the internet as you can see that I have posted a comment here. But that does not solve the problem.

  10. No, this isn’t a general solution. I have been trying to install Ubuntu for long but haven’t been able to do so despite having all those options checked.

  11. Thank you 🙂
    This post helped me…

  12. thanks man!!! you save me!

  13. This solved the same problem while installing Kde Neon, thank you.

  14. Even_more_slowly

    Many thanks for posting this solution.
    I have clicked the download updates, but this didn’t fix the problem…
    I am a little confused Catching_On_Slowly as to how to install mint-meta-codecs into a non-booting system?

  15. Catching_On_Slowly

    I was installing mint 18.2 and had the same issue when installing via a usb. I didn’t read the release notes (link seen on first page of install process) when I started the first time, but I read it the 2nd time around since I couldn’t get anything to work from what I saw on line. As you said it has to be online to receive the codec directory, so I had to go to the Konsole and type in without quotes “apt download mint-meta-codecs”. It works perfectly now, thanks for your thread in getting me to think differently and solving my problem.

Leave a Reply to Catching_On_Slowly Cancel

Your email address will not be published. Required fields are marked *

*