The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.

[joshuaparris]

The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.26 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
CasperVersion: 1.315.1
Date: Mon Nov 18 23:35:57 2013
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ralic (ralic)]

Some details related to this available at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172065

[Yuan Chao (yuanchao)]

Same problem here: ubuntu 12.04.4 on macbook air 6,2. (2013)

[Renata Lopes Reis (renata-2103-lopes)]

ubuntu 13.10 on Samsung ATIV book 9 Lite

[Razvan (razvantoma16)]

I have the same problem on ubuntu 16.04 LTS

[Geb (gebhard-moser)]

Occured on Ubuntu Gnome 16.04 LTS during a fresh install on an Netbook Model ACER TravelMate B115.
Installation got aborted at that point.
Could only be installed by cancelling UEFI mode at beginning of installation.

[kraftb (kraftb)]

Same here.
Occurs on Default Ubuntu 16.04 LTS on a SSD Mushkin storage.

[vacho (vacho)]

Same proble

Ubuntu 16.04 LTS on a Asus laptop with ssd disk of 24 GB. as /

[Nikita (lzhec)]

Uuntu 16.04 on Intel 4670k, motherboard AsRock z87, 16 GB RAM. Ubuntu installed as second system. First Win 8 x64. HDD for Ubuntu 40 GB.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 0.0.10 release.

[Dr_SE (test911turbo)]

Ubuntu 16.10 fresh installation on new harddrive problem persists

[Paddy Landau (paddy-landau)]

Still getting this problem, installing 16.04 or 16.10 on VirtualBox.

[Dr_SE (test911turbo)]

In my case problem now solved: On installation, do not forget to create a EFI System Partition (ESP), if it doesn't already exist.

1.- Live USB Stick, install Ubuntu
2.- on partitioning, select "something else"
3.- create EFI System Partition (ESP):
      - on the 1st 100 G of the disk
      - size > 100 M (recommended 200 M)
      - "primary partition"
      - type: "EFI"
4.- everything else as usual.

Probably adjust your UEFI parameters after reboot, so system finds where to boot.
If it still doesn't boot, then use "boot-repair"

Summary: just follow instructions:

https://help.ubuntu.com/community/UEFI

[Paddy Landau (paddy-landau)]

@Dr_SE thank you, but my EFI has been many-times checked, and Boot Repair crashes for me :(

This bug really does need fixing, especially for newbies to Ubuntu, who would probably give up and go back to Windows.

[forteller (forteller)]

This bug has now stopped me from installing Lubuntu 17.04 beta 2 and both Cinnamon and LXDE version of Linux Mint 16.10. I have not tried to change the partition settings manually, because that's too technical for me. The interesting thing is that Deepin 15.3 installed and booted with no issues.

PC: Acer Aspire S3 MS2346

[Alexandre Ferreira (alexvirtualbr)]

I'm reinstall the Ubuntu 16.04 LTS because I tried install Gentoo but I didn't have success

[Anando Gopal Chatterjee (anandogc)]

This is also happening in Ubuntu 18.04

[Jesús R Cabrera S (jrcsdev)]

Same bug in Ubuntu 18.04

[Reshad Hosseini (reshadhosseini)]

This bug happens also in Ubuntu 18.04. I also followed the instruction in
                  https://help.ubuntu.com/community/UEFI#General_principles
but it did not help.

[Danilo Quispe (daniloquispe-gmail)]

My PC has both Ubuntu 18.04 (a previous installation via upgrading from 16.04) and Windows 7. All previous installation steps were executed as normal, but with package grub-efi-amd64-signed installation stopped at all.

[Phillip Susi (psusi)]

Your installation medium contained a mix of precise and saucy. Before reusing a USB stick for another release, you must clean it.

[Paddy Landau (paddy-landau)]

@Phillip Susi
This was not the case for me. I have had this multiple times, never with a mix of two different versions, and always with a completely fresh installation on a blank slate.

Therefore, this should not be marked as Invalid.

[Phillip Susi (psusi)]

Then your issue is not the same as this one.

[kranthi (kranthi.t2000)]

I'm also having the same problem with my lenovo ideapad 300

[David Surya (initaldevil)]

i'm also having the same problem on my Lenovo G405 with Ubuntu 18.04 LTS...
i need dual boot plz

[Tauno Erik (taunoerik)]

You have to go to Bios and change the Boot Mode settings. When it is UEFI change it to Legasy.

[Malcolm Jaros (maljaros)]

Still happening Ubuntu 19.10

[SM Randall-Friday (sharmarran)]

this is my 6th time trying to install ubuntu. My previous system has already been erased. My daughter recommended ubuntu, so I am sure we will work this out. However, I cannot do my work without being online, so I hope we can get this resolved in an expedient manner. Preferably, before Monday. cheers. SM

[SM Randall-Friday (sharmarran)]

P.S. Is there a fix for this? Or was the image I downloaded from ubuntu corrupted? SM

[Tauno Erik (taunoerik)]

You have to go to Bios and change the Boot Mode settings.
When it is UEFI change it to Legasy.
Tauno

Kontakt SM Randall-Friday (<email address hidden>) kirjutas kuupäeval
L, 4. aprill 2020 kell 17:10:

> P.S. Is there a fix for this? Or was the image I downloaded from ubuntu
> corrupted? SM
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1252255
>
> Title:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> Status in grub-installer package in Ubuntu:
> Invalid
>
> Bug description:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: ubiquity 2.10.26 [modified:
> lib/partman/automatically_partition/question]
> ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
> Uname: Linux 3.8.0-29-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.4
> Architecture: amd64
> CasperVersion: 1.315.1
> Date: Mon Nov 18 23:35:57 2013
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
> LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcEnviron:
> LANGUAGE=en_AU.UTF-8
> TERM=unknown
> PATH=(custom, no user)
> LANG=en_AU.UTF-8
> SHELL=/bin/bash
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions
>

[SM Randall-Friday (sharmarran)]

okay i will try that too

[SM Randall-Friday (sharmarran)]

and ...here we are again.

[SM Randall-Friday (sharmarran)]

This makes 8 attempts. As suggested, changed the boot mode to legacy. The only difference was another error message shortly after choosing Legacy Boot ...

"Ubuntu has been blocked by current security policy"

Clicked ok and my pc continue on to the same installation process, until it tried to install the grub, and received the same error message ...

"The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot"

[Tauno Erik (taunoerik)]

Maybe:
https://superuser.com/questions/1359322/grub-efi-amd64-signed-wont-install-to-usb-drive

"This problem happens when manually creating the disk partitions during a
UEFI enabled installation.

The point is that a UEFI installation requires the prior creation of a UEFI
partition. The error is generated when the installer cannot find a suitable
partition on the installation disk.

See for details the article Creating an EFI System Partition
<https://help.ubuntu.com/community/UEFI#Creating_an_EFI_System_Partition>,
but in short the size of the partition is recommended as 200 MB, of type
FAT32, and flagged as "boot". The partition editor of the installer may
take care of all the details (except the size) if it supports a partition
type of "UEFI"."

Tauno

Kontakt SM Randall-Friday (<email address hidden>) kirjutas kuupäeval
L, 4. aprill 2020 kell 18:10:

> This makes 8 attempts. As suggested, changed the boot mode to legacy.
> The only difference was another error message shortly after choosing
> Legacy Boot ...
>
> "Ubuntu has been blocked by current security policy"
>
> Clicked ok and my pc continue on to the same installation process, until
> it tried to install the grub, and received the same error message ...
>
> "The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot"
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1252255
>
> Title:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> Status in grub-installer package in Ubuntu:
> Invalid
>
> Bug description:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: ubiquity 2.10.26 [modified:
> lib/partman/automatically_partition/question]
> ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
> Uname: Linux 3.8.0-29-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.4
> Architecture: amd64
> CasperVersion: 1.315.1
> Date: Mon Nov 18 23:35:57 2013
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
> LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcEnviron:
> LANGUAGE=en_AU.UTF-8
> TERM=unknown
> PATH=(custom, no user)
> LANG=en_AU.UTF-8
> SHELL=/bin/bash
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions
>

[Shayan S (shayansadigh)]

Hi Dear Randall,

I suggest you to check if you have dual graphics on your system or not. If
yes, do not waist your time, cause I had the same issue. I tried many many
times and even sometimes when I successfully installed it, the issue raised
again, once rebooting the system. After 1 month struggling I ended up
installing Ubuntu on another system.

Regards,
Shayan

On Sat, Apr 4, 2020 at 10:10 PM SM Randall-Friday <
<email address hidden>> wrote:

> this is my 6th time trying to install ubuntu. My previous system has
> already been erased. My daughter recommended ubuntu, so I am sure we
> will work this out. However, I cannot do my work without being online,
> so I hope we can get this resolved in an expedient manner. Preferably,
> before Monday. cheers. SM
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1252255
>
> Title:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> Status in grub-installer package in Ubuntu:
> Invalid
>
> Bug description:
> The 'grub-efi-amd64-signed' package failed to install into /target/.
> Without the GRUB boot loader, the installed system will not boot.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: ubiquity 2.10.26 [modified:
> lib/partman/automatically_partition/question]
> ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
> Uname: Linux 3.8.0-29-generic x86_64
> ApportVersion: 2.0.1-0ubuntu17.4
> Architecture: amd64
> CasperVersion: 1.315.1
> Date: Mon Nov 18 23:35:57 2013
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
> LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
> (20130820.1)
> MarkForUpload: True
> ProcEnviron:
> LANGUAGE=en_AU.UTF-8
> TERM=unknown
> PATH=(custom, no user)
> LANG=en_AU.UTF-8
> SHELL=/bin/bash
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions
>