Calling 'apt-install grub-efi-amd64-signed' failed

[Sascha]

/plugininstall.py: Exception during installation:
/plugininstall.py: Traceback (most recent call last):
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739, in <module>
/plugininstall.py: install.run()
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 61, in wrapper
/plugininstall.py: func(self)
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 227, in run
/plugininstall.py: self.configure_bootloader()
/plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 971, in configure_bootloader
/plugininstall.py: "GrubInstaller failed with code %d" % ret)
/plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1

************************

+++++++++++++++++++++++++++++++++++++++++++++
MBR-EFI-GPT explanations/requirements:

https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
+++++++++++++++++++++++++++++++++++++++++++++

Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3

also see: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1763441/comments/2

https://help.ubuntu.com/community/Boot-Repair

https://ubuntuforums.org/showthread.php?t=2390700

************************

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 28 20:39:35 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[dino99 (9d9)]

https://askubuntu.com/questions/789998/16-04-new-installation-gives-grub-efi-amd64-signed-failed-installation-target

[massimo roccaforte (rockasan)]

Ok
Reinstallato con BIOS legacy

Il Dom 29 Apr 2018, 09:30 dino99 <email address hidden> ha scritto:

> ** Summary changed:
>
> - bootmanger : Calling 'apt-install grub-efi-amd64-signed' failed
> + Calling 'apt-install grub-efi-amd64-signed' failed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767644).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[TaHkictOnlin (tahkictonlin)]

I use the recovery disk Boot-repair solved the problem, I apologize for the trouble, now everything works.

[Eduardo D. Dequilla (eddeqs)]

Dear Sir:
Kindly clarify what do you mean by recovery disk Boot-repair ? How did you
solve the problem using this disk?

Thank you very much.

On Sun, Apr 29, 2018 at 8:39 PM, TaHkictOnlin <email address hidden>
wrote:

> I use the recovery disk Boot-repair solved the problem, I apologize for
> the trouble, now everything works.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767562).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller failed with code 1
>
> ************************
> Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
> boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[massimo roccaforte (rockasan)]

i'm used bios "legacy" boot
intallation ok
thank's

2018-04-30 3:06 GMT+02:00 Eduardo D. Dequilla <email address hidden>:

> Dear Sir:
> Kindly clarify what do you mean by recovery disk Boot-repair ? How did you
> solve the problem using this disk?
>
> Thank you very much.
>
>
> On Sun, Apr 29, 2018 at 8:39 PM, TaHkictOnlin <email address hidden>
> wrote:
>
> > I use the recovery disk Boot-repair solved the problem, I apologize for
> > the trouble, now everything works.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767562).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> > GrubInstaller failed with code 1
> >
> > ************************
> > Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> > 1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.
> seed
> > boot=casper only-ubiquity quiet splash ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > 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/1767703/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767644).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug descriptio...

[TaHkictOnlin (tahkictonlin)]

boot repair is a special recovery disk that allows, for example, to restore the windows boot after installing linux and vice versa. You can download it at SourceForge.net.

[massimo roccaforte (rockasan)]

It worked.

Il Lun 30 Apr 2018, 12:20 TaHkictOnlin <email address hidden> ha
scritto:

> boot repair is a special recovery disk that allows, for example, to
> restore the windows boot after installing linux and vice versa. You can
> download it at SourceForge.net.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767644).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[Alejandro (princecharming)]

I run kill disk. Then reinstall ubuntu 18.04 lts. It works

On Mon, Apr 30, 2018, 6:31 PM massimo roccaforte <email address hidden>
wrote:

> It worked.
>
> Il Lun 30 Apr 2018, 12:20 TaHkictOnlin <email address hidden> ha
> scritto:
>
> > boot repair is a special recovery disk that allows, for example, to
> > restore the windows boot after installing linux and vice versa. You can
> > download it at SourceForge.net.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767644).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller
> > failed with code 1
> >
> > ************************
> > Manual fix:
> >
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash
> ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > 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/1767703/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767404).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during ...

[Flavio Mota (fhmota)]

Boot repair Works for me. Thanks a lot for attention.

Em seg, 30 de abr de 2018 07:50, Alejandro <email address hidden>
escreveu:

> I run kill disk. Then reinstall ubuntu 18.04 lts. It works
>
> On Mon, Apr 30, 2018, 6:31 PM massimo roccaforte <
> <email address hidden>>
> wrote:
>
> > It worked.
> >
> > Il Lun 30 Apr 2018, 12:20 TaHkictOnlin <email address hidden> ha
> > scritto:
> >
> > > boot repair is a special recovery disk that allows, for example, to
> > > restore the windows boot after installing linux and vice versa. You can
> > > download it at SourceForge.net.
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1767644).
> > > https://bugs.launchpad.net/bugs/1767703
> > >
> > > Title:
> > > Calling 'apt-install grub-efi-amd64-signed' failed
> > >
> > > Status in grub-installer package in Ubuntu:
> > > Confirmed
> > >
> > > Bug description:
> > > /plugininstall.py: Exception during installation:
> > > /plugininstall.py: Traceback (most recent call last):
> > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py",
> line
> > > 1739, in <module>
> > > /plugininstall.py: install.run()
> > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py",
> line
> > > 61, in wrapper
> > > /plugininstall.py: func(self)
> > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py",
> line
> > > 227, in run
> > > /plugininstall.py: self.configure_bootloader()
> > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py",
> line
> > > 971, in configure_bootloader
> > > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> > GrubInstaller
> > > failed with code 1
> > >
> > > ************************
> > > Manual fix:
> > >
> >
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
> > >
> > > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > > installer/+bug/1763441/comments/2
> > >
> > > ************************
> > >
> > > ProblemType: Bug
> > > DistroRelease: Ubuntu 18.04
> > > Package: ubiquity 18.04.14
> > > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > > Uname: Linux 4.15.0-20-generic x86_64
> > > ApportVersion: 2.20.9-0ubuntu7
> > > Architecture: amd64
> > > CasperVersion: 1.394
> > > CurrentDesktop: ubuntu:GNOME
> > > Date: Sat Apr 28 20:39:35 2018
> > > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> > > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash
> > ---
> > > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > > (20180426)
> > > ProcEnviron:
> > > LANGUAGE=de_DE.UTF-8
> > > PATH=(custom, no user)
> > > XDG_RUNTIME_DIR=<set>
> > > LANG=de_DE.UTF-8
> > > LC_NUMERIC=C.UTF-8
> > > 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/1767703/+subscriptions
> > >
> >
> > --
> > You recei...

[ziya (bazzkpr1)]

Done

On Tue 1 May, 2018, 8:41 PM dino99, <email address hidden> wrote:

> ** Description changed:
>
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
> +
> + https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767467).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiqu...

[shubham (techgene)]

I formatted my laptop... I couldnt install grub..hence i freshly installed
windows and then ubuntu as a dual boot..this time i didn't find error.

Before formatting:

 i was unable to instal grub..i tried boot repair..even it was able to
rectify during the repair process..but while installing ubuntu it asked for
grub...and i failed...so only option was to delete all partition and
freshly install windows and hence ubuntu

On Tue 1 May, 2018, 9:31 PM ziya, <email address hidden> wrote:

> Done
>
> On Tue 1 May, 2018, 8:41 PM dino99, <email address hidden> wrote:
>
> > ** Description changed:
> >
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller
> > failed with code 1
> >
> > ************************
> > Manual fix:
> >
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> > +
> > + https://help.ubuntu.com/community/Boot-Repair
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash
> ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > SourcePackage: grub-installer
> > UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767467).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.ru...

[TaHkictOnlin (tahkictonlin)]

I do not know what to say to you, because I solved my problem. discuss the topic further yourself, and I'm leaving, the forum is too complicated for my understanding, goodbye.

[shubham (techgene)]

Thanks a lot!

On Wed 2 May, 2018, 12:11 AM TaHkictOnlin, <email address hidden> wrote:

> I do not know what to say to you, because I solved my problem. discuss
> the topic further yourself, and I'm leaving, the forum is too
> complicated for my understanding, goodbye.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767103).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[Dhanraj Prem Kotian (dhanrajkotian12)]

The way I solved this problem was simple. I had the option of installing Ubuntu 18.04 LTS, either using uefi mode or the device boot option (invoked through the BIOS startup by pressing ESC or F2). When I installed using uefi mode, I got this error. What I did next was to boot my USB through the device boot option in the BIOS startup and there was no aforementioned problem.

That is how I escaped the error. Hope this helps.

[shubham (techgene)]

Awesome, thanks!

On Wed 2 May, 2018, 1:21 AM Dhanraj Prem Kotian, <email address hidden>
wrote:

> The way I solved this problem was simple. I had the option of installing
> Ubuntu 18.04 LTS, either using uefi mode or the device boot option
> (invoked through the BIOS startup by pressing ESC or F2). When I
> installed using uefi mode, I got this error. What I did next was to boot
> my USB through the device boot option in the BIOS startup and there was
> no aforementioned problem.
>
> That is how I escaped the error. Hope this helps.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767103).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[George von Fuchs (gvf0935)]

Extreme Thanks, UEFI failed also destroyed my boot loader and I had a dead machine for a while. Working again now.

Sent from Mail for Windows 10

From: Dhanraj Prem Kotian
Sent: Tuesday, May 1, 2018 12:51 PM
To: <email address hidden>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

The way I solved this problem was simple. I had the option of installing
Ubuntu 18.04 LTS, either using uefi mode or the device boot option
(invoked through the BIOS startup by pressing ESC or F2). When I
installed using uefi mode, I got this error. What I did next was to boot
my USB through the device boot option in the BIOS startup and there was
no aforementioned problem.

That is how I escaped the error. Hope this helps.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1768172).
https://bugs.launchpad.net/bugs/1767703

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions

[Keshav Parankusham (keshavparankusham)]

I tried to use boot-repair, but it's giving the error efi directory not found. I tried fresh download and also tried multiple times by trying to format a partition in the front of the disk, every time some booting problem occurs, but boot-repair used to work.

[Niranjan Shrestha (hernewson)]

I solved the problem using legacy boot mode rather than UEFI.

On 2 May 2018 at 19:38, Keshav Parankusham <email address hidden>
wrote:

> I tried to use boot-repair, but it's giving the error efi directory not
> found. I tried fresh download and also tried multiple times by trying to
> format a partition in the front of the disk, every time some booting
> problem occurs, but boot-repair used to work.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767367).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller failed with code 1
>
> ************************
> Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
> boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[ziya (bazzkpr1)]

Success!

On Wed 2 May, 2018, 10:51 PM Niranjan Shrestha, <email address hidden>
wrote:

> I solved the problem using legacy boot mode rather than UEFI.
>
> On 2 May 2018 at 19:38, Keshav Parankusham <email address hidden>
> wrote:
>
> > I tried to use boot-repair, but it's giving the error efi directory not
> > found. I tried fresh download and also tried multiple times by trying to
> > format a partition in the front of the disk, every time some booting
> > problem occurs, but boot-repair used to work.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767367).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> > GrubInstaller failed with code 1
> >
> > ************************
> > Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> > 1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > https://help.ubuntu.com/community/Boot-Repair
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed
> > boot=casper only-ubiquity quiet splash ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > 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/1767703/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767467).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-...

[Gil0224 (gi44-0224)]

Hi

Just a precision for the installation of a Linux OS.

To use the UEFI mode, a "gpt" partition is needed to load the OS (not a "mbr" formatted disk, compatible with the "BIOS-legacy" mode).

Here to find more information:

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

https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/

http://www.rodsbooks.com/linux-uefi/

[apt-ghetto (apt-ghetto)]

@Gil0224, that is not true.

GPT is part of the UEFI standard, but you can install a Linux OS also in BIOS Legacy mode on a GPT formatted disk (you need a bios_grub-partition). On the other side you can install a Linux OS on a MBR formatted disk in UEFI mode.

If you install in the UEFI mode, you just need an EFI-System-Partition with FAT32 as filesystem.

[Gil0224 (gi44-0224)]

@apt-ghetto (apt-ghetto)
yes, also, as it is fully described in the links above.
Tschüß

[adnan ashraf ghonem (adnan.ghonem)]

when i try to use legacy instead of uefi it says that i have to update my
microcode to 0x20
i am using lenovo z50 70 and i have tried alot of solutions there but it
did nothing

On Wed, 2 May 2018, 7:21 pm Niranjan Shrestha, <email address hidden>
wrote:

> I solved the problem using legacy boot mode rather than UEFI.
>
> On 2 May 2018 at 19:38, Keshav Parankusham <email address hidden>
> wrote:
>
> > I tried to use boot-repair, but it's giving the error efi directory not
> > found. I tried fresh download and also tried multiple times by trying to
> > format a partition in the front of the disk, every time some booting
> > problem occurs, but boot-repair used to work.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767367).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> > GrubInstaller failed with code 1
> >
> > ************************
> > Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> > 1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > https://help.ubuntu.com/community/Boot-Repair
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed
> > boot=casper only-ubiquity quiet splash ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > 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/1767703/+subscriptions
> >
>
> --
> You received this bug...

[Mohammad Hossein Shakouri (mhshakouri)]

I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all the disk for installation when it failed. I've tried to install it while formatting the whole disk and I've not yet tried to install it along side windows. I will see what goes on while doing that.

[ziya (bazzkpr1)]

Thanks!

On Fri 4 May, 2018, 1:41 AM Mohammad Hossein Shakouri, <email address hidden>
wrote:

> I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all
> the disk for installation when it failed. I've tried to install it while
> formatting the whole disk and I've not yet tried to install it along
> side windows. I will see what goes on while doing that.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767467).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[Harimbola (harimbola)]

Thank you everyone.

Actually I solved the problem using an older version of Lubuntu.

I don't know what was the problem but it works perfectly now.

2018-05-04 18:57 GMT+03:00 ziya <email address hidden>:

> Thanks!
>
> On Fri 4 May, 2018, 1:41 AM Mohammad Hossein Shakouri, <
> <email address hidden>>
> wrote:
>
> > I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all
> > the disk for installation when it failed. I've tried to install it while
> > formatting the whole disk and I've not yet tried to install it along
> > side windows. I will see what goes on while doing that.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1767467).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Confirmed
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller
> > failed with code 1
> >
> > ************************
> > Manual fix:
> > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > https://help.ubuntu.com/community/Boot-Repair
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> > Uname: Linux 4.15.0-20-generic x86_64
> > ApportVersion: 2.20.9-0ubuntu7
> > Architecture: amd64
> > CasperVersion: 1.394
> > CurrentDesktop: ubuntu:GNOME
> > Date: Sat Apr 28 20:39:35 2018
> > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash
> ---
> > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> > (20180426)
> > ProcEnviron:
> > LANGUAGE=de_DE.UTF-8
> > PATH=(custom, no user)
> > XDG_RUNTIME_DIR=<set>
> > LANG=de_DE.UTF-8
> > LC_NUMERIC=C.UTF-8
> > 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/1767703/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768404...

[Richard Idiens (idiens)]

Boot repair failed for me with "grub-efi-amd04signed" package failed to install
Partitioning from a Live CD to create an EFI system partition failed as there were already four partitions on the drive (dual boot with W7).
Trying grub-install ..... error: failed to get canonical path of `/cow'
Tried installing 14.04 over the top of a partial 18.04.
Great - it works.
Bad news - it overwrote the whole disk, now no W7 and cross SWMBO :-(
After that, 18.04 overwrote 14.04 happily and other problems started.

[Till (thuelsemann)]

I chose to manually create the partitions during install, to optimize the use of multiple hard drives. And I just forgot to create an efi-partition.
Since this was a fresh install on a new computer, that was easy to fix, so for me everything is fine now. A warning "You don't have an efi-partition. Do you really want to continue?" or something alike, would have helped a lot though.

[[e-mail] (jooprenes)]

How do i create an efi-partition during install of 18.04.i also want manual
partitioning as i also have multiple drives.TIA

On Sat, May 5, 2018 at 5:59 PM, Till <email address hidden> wrote:

> I chose to manually create the partitions during install, to optimize the
> use of multiple hard drives. And I just forgot to create an efi-partition.
> Since this was a fresh install on a new computer, that was easy to fix, so
> for me everything is fine now. A warning "You don't have an efi-partition.
> Do you really want to continue?" or something alike, would have helped a
> lot though.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768086).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller failed with code 1
>
> ************************
> Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
> boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> 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/1767703/+subscriptions
>

[Tommi (lockenhorst)]

I can confirm, that it affected my system as well (see https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769732) trying to install on a non-UEFI system.
BIOS settings for USB-Boot were set to UEFI-Boot, though.

I changed the settings in BIOS, no need to change anything on the installer (media). The install wizard detects the drives correctly. I still needed to set the mounting pount of sdc (where Ubuntu was to be installed) as well as (important!) the bootloader set to sda.

[Harimbola (harimbola)]

Actually, I just shift to an older version of lubuntu, 16 if I'm correct.
It worked perfectly. Thanks for your help everyone.

Le mardi 8 mai 2018, Tommi <email address hidden> a écrit :

> I can confirm, that it affected my system as well (see
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769732)
> trying to install on a non-UEFI system.
> BIOS settings for USB-Boot were set to UEFI-Boot, though.
>
> I changed the settings in BIOS, no need to change anything on the
> installer (media). The install wizard detects the drives correctly. I
> still needed to set the mounting pount of sdc (where Ubuntu was to be
> installed) as well as (important!) the bootloader set to sda.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768404).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller failed with code 1
>
> ************************
>
> +++++++++++++++++++++++++++++++++++++++++++++
> MBR-EFI-GPT explanations/requirements:
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-
> partition
> https://askubuntu.com/questions/831216/how-can-i-
> reinstall-grub-to-the-efi-partition
> https://askubuntu.com/questions/578928/why-i-need-
> several-boot-partitions-efi-and-bios-grub
> +++++++++++++++++++++++++++++++++++++++++++++
>
>
> Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
> boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_...

[huynh nhat duy (duyhuynh)]

Thank you

On Tue, May 8, 2018, 16:41 dino99 <email address hidden> wrote:

> ** Description changed:
>
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
>
> +++++++++++++++++++++++++++++++++++++++++++++
> MBR-EFI-GPT explanations/requirements:
>
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
>
> https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
>
> https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
> +++++++++++++++++++++++++++++++++++++++++++++
>
> -
> - Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
> + Manual fix:
> +
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
> +
> + https://ubuntuforums.org/showthread.php?t=2390700
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcEnviron:
> LANGUAGE=de_DE.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=de_DE.UTF-8
> LC_NUMERIC=C.UTF-8
> SourcePackage: grub-installer
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1769228).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Confirmed
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall....

[Till (thuelsemann)]

To create an efi-partition during install, just create a partition and choose efi instead of ext4.
If I remember correctly, it should be at least 100MB and the default one, Ubuntu creates on automatic installation is about 500MB.

[Luis Tobias (mcflysuper)]

My problem was due to a previous Windows installation which was done in Legacy mode. Thus, installing ubuntu in legacy mode solved the issue. This is not a bug rather a fail on my side because I did not realised the Windows installation had created a NTFS recovery partition instead of an EFI one. My bad. Closing the issue as for now.

[Phillip Susi (psusi)]

Your disk is currently partitioned to boot in bios mode, but you booted the installer in EFI mode. A warning message prompted you that this could be a problem and recommended performing a bios mode install instead, but you chose not to. You either need to perform the bios mode install, or partition the disk using GPT and set up an EFI system partition to install in EFI mode. This will be done for you if you choose the "use entire disk" guided install option.

[john (yegnal)]

I booted windows 10 and ubuntu 16.04 uefi before trying to I stall 18.04.

I did NOT receive any such warning whatsoever when trying to I stall 18.04.. Don't know where you got that idea.

I tried custom partitioning and creating an efi partition but 18.04 simply will not install grub.

I booted 16.04 uefi and re-installed 16.04 with no issue before forcing an upgrade to 18.04 in apt.

System is now booting uefi 18.04 and win10 only due to the work around of forcing the upgrade.

The 18.04 media will NOT install whereas 16.04 will. Based on that alone, there is obviously something different happening in the 18.04 package.

[Jane C Poche (jane.3.14)]

Greetings!!

The disk originally had only windows 10, a diagnostics partition and a
system restore partition.

I can not wipe windows to let Linux use the entire disk.

Also, there is no room to create a larger boot area on /dev/sda.

I burned a DVD from the iso using Brasero - and I have no idea what boot
the installer uses.
I received no warning messages when loading and starting the DVD.

Which warning message do you refer to.??

Thanks,
Jay and Jane

On 5/9/2018 2:06 PM, Phillip Susi wrote:
> Your disk is currently partitioned to boot in bios mode, but you booted
> the installer in EFI mode. A warning message prompted you that this
> could be a problem and recommended performing a bios mode install
> instead, but you chose not to. You either need to perform the bios mode
> install, or partition the disk using GPT and set up an EFI system
> partition to install in EFI mode. This will be done for you if you
> choose the "use entire disk" guided install option.
>
> ** Changed in: grub-installer (Ubuntu)
> Status: Confirmed => Invalid
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[dino99 (9d9)]

@psusi

you have answered (#37) to the OP and was right to set the report as 'invalid'. But a lot of dupes also exist; that is why some links have been added on top of the report to teach and educate users hiting such issue.

Please let that report opened to let people find it and give them some paths for fixing their problem. Setting it as 'incomplete' for now instead.

[uthi (a132791)]

On same system (disk) older 1604 intalls fine, but 1804 is not - this is not enough for bug to be accepted ?
Maybe installer should call not grub-efi-amd64-signed but something else ?

[Graham Mitchell (graham-grahammitchell)]

I've been running Linux as my sole OS since 2001 and have been dual-booting Windows and Linux since the summer of 2015.

In particular, Windows 7 with Ubuntu 15.04.

Upgraded in-place to 15.10 in December 2015. Then to 16.04 in May 2016. Upgraded the Windows side to Windows 10 without issue in July 2016. Then Ubuntu 16.10 in October of that year. Then 17.04 when it came out then 17.10, and finally 18.04 -- all upgraded in place.

However, I managed to hit some Ubiquity bug, so video game performance was degraded:
   https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1733136

I tried following the steps in the bug and messed something up, corrupting my graphical system.

No worries! Just make a Ubuntu 18.04 boot disk and fix things that way! Guess I'm due for a clean install anyway.

Used my wife's Windows PC to make a bootable USB installer and booted my machine off of that. Told it to install "alongside" the existing Ubuntu partition. Install seems normal and takes fifteen minutes or so. At the VERY end: ERROR. "Sorry, your system might be in an unusable state." Um, thanks?

Tried lots and lots of things. No dice. Everything I tried THOUGHT it could install Ubuntu just fine but then would error out at the very end.

Eventually I just had to remove all the partitions from the disk and create one new single EXT4 partition and install Ubuntu from scratch. Which actually worked.

Lost all the files on my Windows partition, since I never dreamed that an Ubuntu installer in 2018 would mess THAT up. Would have lost my Linux files, too, but I actually back those up and in particular had done a full backup the night before "just in case."

This is a bug.

If the installer can't successfully do its thing, it needs to tell the user that BEFORE it has permanently altered partitions with gParted.

Bugs happen. I get that. I ain't even mad.

But to call a bug with 173 duplicates "invalid" just because the very first person who successfully reported it theoretically had a workaround is unacceptable.

Our situations are not the same as theirs.

> A warning message prompted you that this
> could be a problem and recommended performing a bios mode install
> instead, but you chose not to

This is literally false. I never saw any such message. My bug is marked as a duplicate of this bug. So either mine is not a duplicate or this bug should still be OPEN.

[Abheek Gogoi (abheekubuntu179)]

I successfully solved this problem by reinstalling windows and then
installing Ubuntu.

On Thu, May 10, 2018, 9:41 PM Graham Mitchell <email address hidden>
wrote:

> I've been running Linux as my sole OS since 2001 and have been dual-
> booting Windows and Linux since the summer of 2015.
>
> In particular, Windows 7 with Ubuntu 15.04.
>
> Upgraded in-place to 15.10 in December 2015. Then to 16.04 in May 2016.
> Upgraded the Windows side to Windows 10 without issue in July 2016. Then
> Ubuntu 16.10 in October of that year. Then 17.04 when it came out then
> 17.10, and finally 18.04 -- all upgraded in place.
>
> However, I managed to hit some Ubiquity bug, so video game performance was
> degraded:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1733136
>
> I tried following the steps in the bug and messed something up,
> corrupting my graphical system.
>
> No worries! Just make a Ubuntu 18.04 boot disk and fix things that way!
> Guess I'm due for a clean install anyway.
>
> Used my wife's Windows PC to make a bootable USB installer and booted my
> machine off of that. Told it to install "alongside" the existing Ubuntu
> partition. Install seems normal and takes fifteen minutes or so. At the
> VERY end: ERROR. "Sorry, your system might be in an unusable state." Um,
> thanks?
>
> Tried lots and lots of things. No dice. Everything I tried THOUGHT it
> could install Ubuntu just fine but then would error out at the very end.
>
> Eventually I just had to remove all the partitions from the disk and
> create one new single EXT4 partition and install Ubuntu from scratch.
> Which actually worked.
>
> Lost all the files on my Windows partition, since I never dreamed that
> an Ubuntu installer in 2018 would mess THAT up. Would have lost my Linux
> files, too, but I actually back those up and in particular had done a
> full backup the night before "just in case."
>
> This is a bug.
>
> If the installer can't successfully do its thing, it needs to tell the
> user that BEFORE it has permanently altered partitions with gParted.
>
> Bugs happen. I get that. I ain't even mad.
>
> But to call a bug with 173 duplicates "invalid" just because the very
> first person who successfully reported it theoretically had a workaround
> is unacceptable.
>
> Our situations are not the same as theirs.
>
> > A warning message prompted you that this
> > could be a problem and recommended performing a bios mode install
> > instead, but you chose not to
>
> This is literally false. I never saw any such message. My bug is marked
> as a duplicate of this bug. So either mine is not a duplicate or this
> bug should still be OPEN.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767418).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Incomplete
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install....

[uthi (a132791)]

@Abheek Gogoi

You think it is the solution ? )

Last time i tried install on my sdf disk in UEFI mode - at end grub failed to install on disk sda, why sda ?
In BIOS mode installation was succesfull, but then nvdidia drivers bings black screen (https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053)

Next i try reinstall on same disk opensuse tumbleweed, and it installed ok in uefi mode. So installation procedure of 1804 somehow is wrong.

[uthi (a132791)]

@Luis Tobias

Why "Invalid" again ?
Many users has that problem and no solution.

[Graham Mitchell (graham-grahammitchell)]

There are some edge cases when the user's disk is partitioned to boot in bios mode, but the EFI mode installer doesn't detect it.

There is supposed to be a warning message about this combination but it does not always show up -- as evidenced by this thread.

For these users, there is NO indication that something is wrong until the very end, when 'apt-install grub-efi-amd64-signed' fails, but by then it is too late.

Many people have lost data because of this bug.

Is there an existing bug report for "EFI mode installer doesn't always detect when booted in BIOS mode"? If so then maybe this bug can be marked as a duplicate of that one.

But this bug should not be closed as invalid until then.

[dino99 (9d9)]

@Graham & others complaining

Take note that the installer has been designed more than a decade ago; but recent hardware have introduced some ubknown concept a few years back: uefi/efi, gpt, nvme.
That is way different than the 'legacy' mode known by ubiquity.

Server has already a new installer, but not the desktop yet. So reworking ubiquity is not the way Canonical is thinking about.

https://www.phoronix.com/scan.php?page=news_item&px=Mark-Shuttleworth-Ubiquity-NG

[Graham Mitchell (graham-grahammitchell)]

Thanks for weighing in.

I don't mean to imply that there's a bug in Ubiquity. But there's clearly a failure somewhere in the installation process.

And I'm going to complain every time this bug is closed as "invalid" until there's a more appropriate bug to reference.

[John D (johnniedoo)]

My 2¢ again, I just could not figure out how to boot into the perfectly sound installation on a drive partition. Only 2 partitions and a block of unallocated space. However, I was able to install ubuntu 18.04 using a cd media to another partition on a 3rd drive , and it worked perfectly first shot. And, a consequence of that grub install was it found the original non bootable drive. So, now I have 2 drives with ubuntu bionic beaver I can boot into.as well as windows 10. Not what I had originally intended but it works for me. Now anyway

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

________________________________
From: <email address hidden> <email address hidden> on behalf of Graham Mitchell <email address hidden>
Sent: Tuesday, May 15, 2018 11:08:44 AM
To: <email address hidden>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

Thanks for weighing in.

I don't mean to imply that there's a bug in Ubiquity. But there's
clearly a failure somewhere in the installation process.

And I'm going to complain every time this bug is closed as "invalid"
until there's a more appropriate bug to reference.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1770787).
https://bugs.launchpad.net/bugs/1767703

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

Status in grub-installer package in Ubuntu:
  Incomplete

Bug description:
  /plugininstall.py: Exception during installation:
  /plugininstall.py: Traceback (most recent call last):
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739, in <module>
  /plugininstall.py: install.run()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 61, in wrapper
  /plugininstall.py: func(self)
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 227, in run
  /plugininstall.py: self.configure_bootloader()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 971, in configure_bootloader
  /plugininstall.py: "GrubInstaller failed with code %d" % ret)
  /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1

  ************************

  +++++++++++++++++++++++++++++++++++++++++++++
  MBR-EFI-GPT explanations/requirements:

  https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
  https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
  https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
  +++++++++++++++++++++++++++++++++++++++++++++

  Manual fix:
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3

  also see: https://bugs.launchpad.net/ubuntu/+source/grub-
  installer/+bug/1763441/comments/2

  https://help.ubuntu.com/community/Boot-Repair

  https://ubuntuforums.org/showthread.php?t=2390700

  ************************

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Archite...

[aimwin (aimausy)]

@Graham Mitchell (graham-grahammitchell)
I view the same as yours.
More though, there is or are the bugs somewhere in the new 18.04 Ubuntu, Kylyn, Lubuntu.
I confirmed the problems.

https://askubuntu.com/questions/1028921/the-grub-efi-amd64-signed-package-failed-to-install-into-target-during-ins/1037036#1037036

My conclusions they are another very bad bugs.
Since the all old 16.04 works fine for exact same environments.

All 16.04 will detect my notebook is uefi, and will have the installation screen as uefi mode.
But since I purposely do not provide efi partition.
In order to force all installation to prohibit UEFI mode which I did make mistake again with new SSD half a year back on 16.04.4 fresh installation. End up no F12.
And I have to open up my broken notebook to short jumpers again to get F12 BACK.

So the installation process will warn me in all 16.04 flavors, UBUNTU Mint Mate lubuntu kylyn xubuntu.
And I will choose to click on go back button to FORCE BIOS mode installation.

But I did not encounter the same warning from any of my 6-7 times on my LH532 notebook with 18.04 Ubuntu Kylyn nor Lubuntu.
Therefore, I have no chance to force the installation process back to activate BIOS installation mode.

My conclusion the bugs lies in the 3 parts.

1. It did not detect that we have BIOS mode installations in place like the 16.04.4 and older version
(I have not tried 17. at all) so I will keep on going to find efi partition to install uefi ubuntu.

2. It should have check if the efi partition exist before it activate the efi installation mode.

3. At the end error last 2 warning page freez and stay there until we reboot.
except Lubuntu 18.04 allow us to close the freez warning page.

I hope the Guru will have some clues by now how to find these bugs and fix it.

Best Regards

[OE (onno-ebbinge)]

Can anybody confirm that the workaround in the bug report below works?

https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651

If so, then it could be a duplicate...

[aimwin (aimausy)]

Sorry I could not find the old edit link to go and edit my post so I repeat the part that need modifications/////

My conclusion is Moderator must now file this as real bugs in 18.04

The bugs lies in the 4 parts.

1. It did not detect that we have BIOS mode installations in place,
like the 16.04.4 and older version (I have not tried 17. at all).
So It keep going to install to efi partition which resulted in this error.

2. I belived I did find once or twice in some different configuration that it present the choice at the beginning of the installation process and I chose Bios.
But still got the same result of same errors.
But some how most of time no questions ask at the begging.

3. It should have check if the efi partition exist before it activate the efi installation mode.
I did not have EFI partition on purpose, And It should find that easily by use the program algorithm.

4. At the end error last 2 warning page freezed and stay there until we reboot.
except Lubuntu 18.04 allow us to close the error warning pages.
So even within 18.04 there are bugs for sure.
Lubuntu did not have this 4th bug while the UBUNTU AND KYLIN HAS.

I hope the Guru will have some clues by now how to find these bugs and fix it.

Best Regards

[OE (onno-ebbinge)]

For the people who are looking for a workaround; I think you have three options:

- Use a GPT partition table on the disk
- Boot the installer in legacy mode
- When both are not an option (or fail), use the workaround described in:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651

I hope this helps, regards,
Onno

[Kamrul Hasan (sumonrn)]

Is this really a bug?
In my opinion it is not.
This is just a user fault.

The solution of this problem relies on two basic steps. At first you need to create your Ubuntu 18.04 bootable flash drive correctly. And secondly, you need to bootup you machine using the bootable flash drive in the correct mode (UEFI/CSM/Legacy BIOS). When your system is MBR Partitioned with legacy BIOS and you try to install Ubuntu in UEFI mode, failure of the installation process is natural.

You may want to read more:

https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-failed.html

[Yasin Balcancı (ybalcanci)]

Yes I learnt about it afterwards and solved the problem somehow. Thanks.

17 May 2018 Per, saat 19:21 tarihinde Kamrul Hasan <email address hidden> şunu
yazdı:

> Is this really a bug?
> In my opinion it is not.
> This is just a user fault.
>
> The solution of this problem relies on two basic steps. At first you
> need to create your Ubuntu 18.04 bootable flash drive correctly. And
> secondly, you need to bootup you machine using the bootable flash drive
> in the correct mode (UEFI/CSM/Legacy BIOS). When your system is MBR
> Partitioned with legacy BIOS and you try to install Ubuntu in UEFI mode,
> failure of the installation process is natural.
>
> You may want to read more:
>
> https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-
> failed.html
> <https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-failed.html>
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1771217).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Incomplete
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
>
> +++++++++++++++++++++++++++++++++++++++++++++
> MBR-EFI-GPT explanations/requirements:
>
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
>
> https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
>
> https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
> +++++++++++++++++++++++++++++++++++++++++++++
>
> Manual fix:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> https://ubuntuforums.org/showthread.php?t=2390700
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet sp...

[Uwe Wartemann (uwe-watermann60)]

Sorry, but I used a CD from Umbuntu. And Not all User been so smart like
you.

Kamrul Hasan <email address hidden> schrieb am Do., 17. Mai 2018, 18:21:

> Is this really a bug?
> In my opinion it is not.
> This is just a user fault.
>
> The solution of this problem relies on two basic steps. At first you
> need to create your Ubuntu 18.04 bootable flash drive correctly. And
> secondly, you need to bootup you machine using the bootable flash drive
> in the correct mode (UEFI/CSM/Legacy BIOS). When your system is MBR
> Partitioned with legacy BIOS and you try to install Ubuntu in UEFI mode,
> failure of the installation process is natural.
>
> You may want to read more:
>
> https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-
> failed.html
> <https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-failed.html>
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1771665).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Incomplete
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
> ************************
>
> +++++++++++++++++++++++++++++++++++++++++++++
> MBR-EFI-GPT explanations/requirements:
>
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
>
> https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
>
> https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
> +++++++++++++++++++++++++++++++++++++++++++++
>
> Manual fix:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> https://ubuntuforums.org/showthread.php?t=2390700
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---...

[alexandrubutoi (alexandrubutoi)]

I am just an user, not an linux expert. In my opinion your reaction is very inapropiate !

Numai bine !
Alexandru Butoi
Tel. [phone]

    On Thursday, May 17, 2018, 7:41:30 PM GMT+3, Yasin Balcancı <email address hidden> wrote:

 Yes I learnt about it afterwards and solved the problem somehow. Thanks.

17 May 2018 Per, saat 19:21 tarihinde Kamrul Hasan <email address hidden> şunu
yazdı:

> Is this really a bug?
> In my opinion it is not.
> This is just a user fault.
>
> The solution of this problem relies on two basic steps. At first you
> need to create your Ubuntu 18.04 bootable flash drive correctly. And
> secondly, you need to bootup you machine using the bootable flash drive
> in the correct mode (UEFI/CSM/Legacy BIOS). When your system is MBR
> Partitioned with legacy BIOS and you try to install Ubuntu in UEFI mode,
> failure of the installation process is natural.
>
> You may want to read more:
>
> https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-
> failed.html
> <https://abcsofubuntu.blogspot.com/2018/05/how-to-fix-grub-installation-failed.html>
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1771217).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
>  Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
>  Incomplete
>
> Bug description:
>  /plugininstall.py: Exception during installation:
>  /plugininstall.py: Traceback (most recent call last):
>  /plugininstall.py:  File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
>  /plugininstall.py:    install.run()
>  /plugininstall.py:  File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
>  /plugininstall.py:    func(self)
>  /plugininstall.py:  File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
>  /plugininstall.py:    self.configure_bootloader()
>  /plugininstall.py:  File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
>  /plugininstall.py:    "GrubInstaller failed with code %d" % ret)
>  /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller
> failed with code 1
>
>  ************************
>
>  +++++++++++++++++++++++++++++++++++++++++++++
>  MBR-EFI-GPT explanations/requirements:
>
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
>
> https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
>
> https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
>  +++++++++++++++++++++++++++++++++++++++++++++
>
>  Manual fix:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3
>
>  also see: https://bugs.launchpad.net/ubuntu/+source/grub-
>  installer/+bug/1763441/comments/2
>
>  https://help.ubuntu.com/community/Boot-Repair
>
>  https://ubuntuforums.org/showthread.php?t=2390700
>
>  ************************
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: ubiquity 18.04.14
>  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>  Uname: Linux 4.15.0-20-generic x86_64
>  ApportVersion: 2.20.9-0ubuntu7
>  Architecture: amd64
> ...

[OE (onno-ebbinge)]

> Is this really a bug?

When the previous LTS had not problems in these situations, then it's not only a bug but a regression as well.

When a large portion of your user-base is experiencing trouble where they don't expect it and/or had none before, it should be fixed. Especially when a fix is (easily) feasible and expands the use of Ubuntu and it derivatives considerably.

Thus, it's a bug.

[Kamrul Hasan (sumonrn)]

True.

I faced the same problems at first.
Anyway, a Linux user should be a little more advanced.
And as because we do not have the possibility to get the fixed version very soon, we as a user should try to learn a bit more.

Yes, I have realized later that it is a bug and also an user fault.

I agree. #OE

[uthi (a132791)]

@Kamrul Hasan
> This is just a user fault.

Once again - installation of 1404 and 1604 on same disk was fine.
But installation 1804 has error - is it user fault of that ?
Is user need to wipe disk and install 1804 ? (yes, that works ok)
Or repartition disk, or buy the new one ?

On same disk opensuse installs fine in uefi mode, but 1804 was not - is any other comments needed ?

[Kamrul Hasan (sumonrn)]

May be I was too rude in my previous comment.

But this is actually as simple as selecting the right mode while booting up your machine.
In ubuntu 14.04 and 16.04 the selection window ware coming while installation.
In ubuntu 18.04 you need to select it manually while booting up.

The process is explained here in a very simple manner.

https://abcsofubuntu.blogspot.com/2018/05/bootup-your-machine-from-bootable-usb-device-in-right-mode.html

Yes, this is a bug if you say so. Or, may be intentionally removal of a fetcher for some reason.

[Kamrul Hasan (sumonrn)]

This should be the same if you use a bootable DVD instead of bootable flash drive.

[Vitaly Bondar (johngull)]

I believe that some message during installation should appear. It should explain issue about UEFI and give the recommendation to change the drive or to reboot in legacy mode.

[uthi (a132791)]

> In ubuntu 18.04 you need to select it manually while booting up.

Yes, user can select UEFI mode or BIOS at boot time of installation, but somehow UEFI mode installation of opensuse (thumbleweed) works fine, but 1804 is not (on same disk and machine).

Also UEFI mode installation 1804 on that machine displays "message" what it will be "manufactered mode" (as i remembered) and incorrectly defines (displays in partition table) all existing ext4 partition as "efi", and cant install grub on /dev/sdf(1), but tried on /dev/sda with failure message.

[John D (johnniedoo)]

I made an installer of ubuntu mate 18.04 and encountered failures in all methods of installation, side by side or to a newly created (gparted) ext4 partition with plenty of room and free space. It gets all the way though almost and kicks out the same error ‘apt-install grub efi …….’ I have a hybrid motherboard in this computer can use bios or uefi. Only way I got any joy was with a dvd ubuntu bionic beaver method. Usb never works and I tried over 20 times with different methods. I even tried to follow the ubuntu one directions to add the bootloader grub using copy/paste method. No good. I came to learn, after I was successful with the ubuntu via cd that there was indeed a successful installation but it never showed up until later when I put in the grub customizer app. So , I do have a working , or 2 working installations of ubuntu. The ubuntu mate (which is my favorite DE) is not successful. I am not any expert so no way to know how much is my fault and if or how much is a bug or issue with the installer. I used 3 separate methods to create the live dvd or usb too.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

________________________________
From: <email address hidden> <email address hidden> on behalf of uthi <email address hidden>
Sent: Friday, May 18, 2018 4:35:52 AM
To: <email address hidden>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

> In ubuntu 18.04 you need to select it manually while booting up.

Yes, user can select UEFI mode or BIOS at boot time of installation, but
somehow UEFI mode installation of opensuse (thumbleweed) works fine, but
1804 is not (on same disk and machine).

Also UEFI mode installation 1804 on that machine displays "message" what
it will be "manufactered mode" (as i remembered) and incorrectly defines
(displays in partition table) all existing ext4 partition as "efi", and
cant install grub on /dev/sdf(1), but tried on /dev/sda with failure
message.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1770787).
https://bugs.launchpad.net/bugs/1767703

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

Status in grub-installer package in Ubuntu:
  Incomplete

Bug description:
  /plugininstall.py: Exception during installation:
  /plugininstall.py: Traceback (most recent call last):
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739, in <module>
  /plugininstall.py: install.run()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 61, in wrapper
  /plugininstall.py: func(self)
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 227, in run
  /plugininstall.py: self.configure_bootloader()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 971, in configure_bootloader
  /plugininstall.py: "GrubInstaller failed with code %d" % ret)
  /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1

  ************************

  +++++++++++++++++++++++++++++++++++++++++++++
  MBR-EFI-GPT explanations/requirements:

  https://askubuntu.com/questions/500359/efi-boot...

[ziya (bazzkpr1)]

It worked.

On Fri 18 May, 2018, 6:21 PM John D, <email address hidden> wrote:

> I made an installer of ubuntu mate 18.04 and encountered failures in all
> methods of installation, side by side or to a newly created (gparted)
> ext4 partition with plenty of room and free space. It gets all the way
> though almost and kicks out the same error ‘apt-install grub efi …….’ I
> have a hybrid motherboard in this computer can use bios or uefi. Only
> way I got any joy was with a dvd ubuntu bionic beaver method. Usb never
> works and I tried over 20 times with different methods. I even tried to
> follow the ubuntu one directions to add the bootloader grub using
> copy/paste method. No good. I came to learn, after I was successful with
> the ubuntu via cd that there was indeed a successful installation but it
> never showed up until later when I put in the grub customizer app. So ,
> I do have a working , or 2 working installations of ubuntu. The ubuntu
> mate (which is my favorite DE) is not successful. I am not any expert
> so no way to know how much is my fault and if or how much is a bug or
> issue with the installer. I used 3 separate methods to create the live
> dvd or usb too.
>
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
> ________________________________
> From: <email address hidden> <email address hidden> on behalf of uthi <
> <email address hidden>>
> Sent: Friday, May 18, 2018 4:35:52 AM
> To: <email address hidden>
> Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed'
> failed
>
> > In ubuntu 18.04 you need to select it manually while booting up.
>
> Yes, user can select UEFI mode or BIOS at boot time of installation, but
> somehow UEFI mode installation of opensuse (thumbleweed) works fine, but
> 1804 is not (on same disk and machine).
>
> Also UEFI mode installation 1804 on that machine displays "message" what
> it will be "manufactered mode" (as i remembered) and incorrectly defines
> (displays in partition table) all existing ext4 partition as "efi", and
> cant install grub on /dev/sdf(1), but tried on /dev/sda with failure
> message.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1770787).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Incomplete
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStep...

[Keshav Parankusham (keshavparankusham)]

I've tried boot-repair and many other solutions, but I was always getting an error that boot/efi directory was not found. Finally I tried disabling the UEFI mode and it worked like a charm. I don't know why I've never seen anyone mention to disable this, instead I just found more discription of how things work and tried to create partitions etc etc...

[OE (onno-ebbinge)]

Is this a "grub-installer" bug -or- is the use of grub in "ubiquity" the problem ???

If the latter, then this bug should be assigned to the "ubiquity" package...

[apt-ghetto (apt-ghetto)]

As far as I can see, the problem occurs only if the disk is MBR/MSDOS formatted and the installer is booted in the EFI mode. So we should create some test cases and test.

Test case 1:
Prerequisites:
 - one disk; partition table -> GPT
 - no EFI-System-Partition
 - The installer is booted in EFI mode => [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
Expected result:
 - Warning is printed about missing ESP, no crash

Test case 2:
Prerequisites:
 - one disk; partition table -> MBR/MSDOS
 - no EFI-System-Partition
 - The installer is booted in EFI mode => [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
Expected result:
 - Warning is printed about missing ESP, no crash

Test case 3:
Prerequisites:
 - one disk; partition table -> GPT
 - EFI-System-Partition exists
 - The installer is booted in EFI mode
Expected result:
 - Installation succeeds

Test case 4:
Prerequisites:
 - one disk; partition table -> MBR/MSDOS
 - EFI-System-Partition exists
 - The installer is booted in EFI mode
Expected result:
 - Installation succeeds

In my opinion, it is a bug in ubiquity, that it is not complaining about a missing ESP before the installation begins.

[phyzzy2008 (nigellumsden)]

Lenovo Z570
If you create a /boot/efi partition (Fat32) first Ubuntu 18.04 installs BUT
you cannot boot Windows 7 which is install legacy/bios boot. The only way I
could solve it was to delete all the partitions and reinstall Windows 7 in
UEFI boot mode. Then you can install 18.04 and boot either OS at startup.
Of course you have to keep all your data somewhere else. I got the computer
second hand so I didn't have any apps or data on it.

With best wishes,
Nigel Lumsden

[phone]

On 19 May 2018 at 09:27, Keshav Parankusham <email address hidden>
wrote:

> I've tried boot-repair and many other solutions, but I was always
> getting an error that boot/efi directory was not found. Finally I tried
> disabling the UEFI mode and it worked like a charm. I don't know why
> I've never seen anyone mention to disable this, instead I just found
> more discription of how things work and tried to create partitions etc
> etc...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1770991).
> https://bugs.launchpad.net/bugs/1767703
>
> Title:
> Calling 'apt-install grub-efi-amd64-signed' failed
>
> Status in grub-installer package in Ubuntu:
> Incomplete
>
> Bug description:
> /plugininstall.py: Exception during installation:
> /plugininstall.py: Traceback (most recent call last):
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 1739, in <module>
> /plugininstall.py: install.run()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 61, in wrapper
> /plugininstall.py: func(self)
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 227, in run
> /plugininstall.py: self.configure_bootloader()
> /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> 971, in configure_bootloader
> /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> /plugininstall.py: ubiquity.install_misc.InstallStepError:
> GrubInstaller failed with code 1
>
> ************************
>
> +++++++++++++++++++++++++++++++++++++++++++++
> MBR-EFI-GPT explanations/requirements:
>
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-
> partition
> https://askubuntu.com/questions/831216/how-can-i-
> reinstall-grub-to-the-efi-partition
> https://askubuntu.com/questions/578928/why-i-need-
> several-boot-partitions-efi-and-bios-grub
> +++++++++++++++++++++++++++++++++++++++++++++
>
> Manual fix:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> 1766945/comments/3
>
> also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> installer/+bug/1763441/comments/2
>
> https://help.ubuntu.com/community/Boot-Repair
>
> https://ubuntuforums.org/showthread.php?t=2390700
>
> ************************
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: ubiquity 18.04.14
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CasperVersion: 1.394
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 28 20:39:35 2018
> InstallCmdLine: ...

[ziya (bazzkpr1)]

Thanks for the info.

On Tue 22 May, 2018, 12:06 PM phyzzy2008, <email address hidden>
wrote:

> Lenovo Z570
> If you create a /boot/efi partition (Fat32) first Ubuntu 18.04 installs BUT
> you cannot boot Windows 7 which is install legacy/bios boot. The only way I
> could solve it was to delete all the partitions and reinstall Windows 7 in
> UEFI boot mode. Then you can install 18.04 and boot either OS at startup.
> Of course you have to keep all your data somewhere else. I got the computer
> second hand so I didn't have any apps or data on it.
>
> With best wishes,
> Nigel Lumsden
>
> [phone]
>
> On 19 May 2018 at 09:27, Keshav Parankusham <email address hidden>
> wrote:
>
> > I've tried boot-repair and many other solutions, but I was always
> > getting an error that boot/efi directory was not found. Finally I tried
> > disabling the UEFI mode and it worked like a charm. I don't know why
> > I've never seen anyone mention to disable this, instead I just found
> > more discription of how things work and tried to create partitions etc
> > etc...
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1770991).
> > https://bugs.launchpad.net/bugs/1767703
> >
> > Title:
> > Calling 'apt-install grub-efi-amd64-signed' failed
> >
> > Status in grub-installer package in Ubuntu:
> > Incomplete
> >
> > Bug description:
> > /plugininstall.py: Exception during installation:
> > /plugininstall.py: Traceback (most recent call last):
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 1739, in <module>
> > /plugininstall.py: install.run()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 61, in wrapper
> > /plugininstall.py: func(self)
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 227, in run
> > /plugininstall.py: self.configure_bootloader()
> > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line
> > 971, in configure_bootloader
> > /plugininstall.py: "GrubInstaller failed with code %d" % ret)
> > /plugininstall.py: ubiquity.install_misc.InstallStepError:
> > GrubInstaller failed with code 1
> >
> > ************************
> >
> > +++++++++++++++++++++++++++++++++++++++++++++
> > MBR-EFI-GPT explanations/requirements:
> >
> >
> https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-
> > partition
> > https://askubuntu.com/questions/831216/how-can-i-
> > reinstall-grub-to-the-efi-partition
> > https://askubuntu.com/questions/578928/why-i-need-
> > several-boot-partitions-efi-and-bios-grub
> > +++++++++++++++++++++++++++++++++++++++++++++
> >
> > Manual fix:
> > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/
> > 1766945/comments/3
> >
> > also see: https://bugs.launchpad.net/ubuntu/+source/grub-
> > installer/+bug/1763441/comments/2
> >
> > https://help.ubuntu.com/community/Boot-Repair
> >
> > https://ubuntuforums.org/showthread.php?t=2390700
> >
> > ************************
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 18.04
> > Package: ubiquity 18.04.14
> > ProcVersion...

[apt-ghetto (apt-ghetto)]

To get a working dual boot, you have to install both operating systems in the same mode.
Of course, if you have a lot of time and patience, you can reinstall Windows. Reinstalling Ubuntu in the same mode as Windows is normally the faster way.

[Andrew Gadd (redbubbble481)]

I have now have ubuntu and win 10 dual boot working. I did a BIOS update. Then it just worked. Who knows what the problem was. Thanks for your time and help.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

________________________________
From: <email address hidden> <email address hidden> on behalf of apt-ghetto <email address hidden>
Sent: Tuesday, May 22, 2018 4:21:02 PM
To: <email address hidden>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

To get a working dual boot, you have to install both operating systems in the same mode.
Of course, if you have a lot of time and patience, you can reinstall Windows. Reinstalling Ubuntu in the same mode as Windows is normally the faster way.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1771861).
https://bugs.launchpad.net/bugs/1767703

Title:
  Calling 'apt-install grub-efi-amd64-signed' failed

Status in grub-installer package in Ubuntu:
  Incomplete

Bug description:
  /plugininstall.py: Exception during installation:
  /plugininstall.py: Traceback (most recent call last):
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1739, in <module>
  /plugininstall.py: install.run()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 61, in wrapper
  /plugininstall.py: func(self)
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 227, in run
  /plugininstall.py: self.configure_bootloader()
  /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 971, in configure_bootloader
  /plugininstall.py: "GrubInstaller failed with code %d" % ret)
  /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1

  ************************

  +++++++++++++++++++++++++++++++++++++++++++++
  MBR-EFI-GPT explanations/requirements:

  https://askubuntu.com/questions/500359/efi-boot-partition-and-biosgrub-partition
  https://askubuntu.com/questions/831216/how-can-i-reinstall-grub-to-the-efi-partition
  https://askubuntu.com/questions/578928/why-i-need-several-boot-partitions-efi-and-bios-grub
  +++++++++++++++++++++++++++++++++++++++++++++

  Manual fix:
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766945/comments/3

  also see: https://bugs.launchpad.net/ubuntu/+source/grub-
  installer/+bug/1763441/comments/2

  https://help.ubuntu.com/community/Boot-Repair

  https://ubuntuforums.org/showthread.php?t=2390700

  ************************

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 20:39:35 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=de_DE.UTF-8
   LC_NUM...

[Carlos centurión (carloscent2)]

El problema ha sido solucionado muchas gracias a todos.

[Phillip Susi (psusi)]

Your disk is currently partitioned to boot in bios mode, but you booted the installer in EFI mode. A warning message prompted you that this could be a problem and recommended performing a bios mode install instead, but you chose not to. You either need to perform the bios mode install, or partition the disk using GPT and set up an EFI system partition to install in EFI mode. This will be done for you if you choose the "use entire disk" guided install option.

[Graham Mitchell (graham-grahammitchell)]

> A warning message prompted you that this could be a problem

Why do you keep saying this?

I ran the installer maybe five or six times and NEVER saw ANY warning message. Stop claiming that I did.

This bug is NOT invalid.

[Andrew Gadd (redbubbble481)]

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Graham Mitchell<mailto:<email address hidden>>
Sent: 07 June 2018 03:30
To: <email address hidden><mailto:<email address hidden>>
Subject: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed

> A warning message prompted you that this could be a problem

Why do you keep saying this?

I ran the installer maybe five or six times and NEVER saw ANY warning
message. Stop claiming that I did.

I did get the warning.

I did fix it by Updating my BIOS. There is an old MBR on one of my hard disks but not /dev/sda.
The Windows 10 install was a clean install to a UEFI BIOS. Something was wrong but is no longer wrong with the BIOS.

I now have a working Ubuntu setup.

[Till (thuelsemann)]

I didn't get any warning either.

So there is probably something wrong with the detection, if a warning should be displayed.

[Graham Mitchell (graham-grahammitchell)]

> I did get the warning.

I'm sure you did. With 293 people affected by this bug I'm sure there are some that got a warning and ignored it.

I agree with Till; there is definitely something wrong with the detection in some component somewhere.

[Graham Mitchell (graham-grahammitchell)]

For the record, this bug is in the top 30 out of ALL of Ubuntu by bug heat: https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat&start=0

[Karl William (karl-william)]

I have also tried to install 18.04 LTS and it failed several times.
Seeking a solution I read somewhere about leaving 1-2 MB of space before efi partition. In the beginning of linux era as I remember there was a practice of leaving some space before adding partitions.
So I did so through Ubuntu installer:
- Create 2 MB FAT32 partition
- Create 1024 MB efi partition
- Create / (root) partition on the rest
- Delete 2 MB partition

Click on Install now!

I haven't changed anything else, just these 2 MB and voila it installed without any problem!

[Phillip Susi (psusi)]

There used to be a prompt that while worded poorly, did give you the ability to switch to a bios mode install even though you booted the installer in UEFI mode, but it was removed in 18.04. Unfortunately, instead of making it switch to a bios mode install by default, it keeps with the UEFI install and crashes. This mistake is being tracked in bug #1668148. Hopefully this will be fixed in 18.04.1, but until then, you just have to get your system to boot the installer in bios mode. If you are using a USB stick you can delete the EFI directory to make sure it can't boot in UEFI mode.

[Graham Mitchell (graham-grahammitchell)]

Wonderful news! I'm glad we finally have a proper bug we can track.

Thanks for the update.