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:  How does your encrypted Linux system respond to the Cryptsetup bug?

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.

Related Post:  One reason you may be getting that "Relay access denied" error

Subscribe to LinuxBSDos.com

Subscribe to receive the latest articles in your Inbox

Trust me, you'll not be spammed...

Please share:
Tags:

We Recommend These Vendors and Free Offers

Google has got competition, because Presearch is building a blockchain-based search engine controlled by the community. At $0.15 a token, you can participation in Lot 3 of the token sale by clicking here

Open Money is building a solution that will run mainstream software on blockchain tech. Click here to get free tokens that will be the digital currency of the platform

COMSA allows centralized businesses to adopt blockchain technology. The token sale starts soon! Sign up for free by clicking here

Register now for Blockchain & Cryptocurrency Con 2018, international conference on blockchain technnology in Dallas, TX (USA), Feb. 23-24, 2018. Students can register at a 50% discount.

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).


3 Comments

  1. 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?

  2. 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 Comment

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

*