[Bug 1713364] [NEW] grub-efi-amd64signed package not installed

Karl McAllister 1713364 at bugs.launchpad.net
Sun Aug 27 20:33:22 UTC 2017


Public bug reported:

I had Ubuntu 16.1 installed on my hp pavillion laptop.  It  started
acting eratic and finally crashed with a "There is no operating system
installed on this hard-drive" error.  I am currently running Ubuntu
17.04 from a start-up flash-drive.  I also have the original start-up
flash-drive for Ubuntu 16.1 which I originally installed Ubuntu from.
Both start-up drives work fine from the "try Ubuntu" mode, but when I
try to install or reinstall Ubuntu I get a "grub-efi-amd64sined" package
not installed error and the system won't boot.  This is weird because I
got this first when I tried to reinstall from the original 10.4 drive.
Then, using Ubuntu 16.1 from that original flash-drive, I downloaded and
created a new start-up flash-drive, this time with Ubuntu 17.04. The
drive works in the try version but when I try to install it I get the
same grub error.

I would assume that the new download should be complete.  How could it
have the same error?  Especially when I chose to erase the existing 16.1
and replace it with the new 17.4.

I then tried a solution I found online on the Ubuntu Community:

$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade

then:

$ sudo apt install --reinstall grub
$ sudo apt install --reinstall grub2-common
$ sudo apt install --reinstall grub-efi-amd64
$ sudo apt install --reinstall grub-efi-amd64-bin
$ sudo apt autoremove
$ sudo apt install grub-efi-amd64-signed

The only irregularities I encountered were once during the upgrade it
detected a difference between the coding from the software manufacturer
and the local one on my computer, and gave me a list of options.  I
chose to keep the local version since I believe I have the newest ubuntu
desktop (17.4).

Everything seemed to work as planned.  It didn't find the first grub to
reinstall but it said that it is replaced by the same grup2 and grub efi
as above, so I figured I was on the right track.

Only problem is when I again tried to install Ubuntu 17.4 on my computer
I get the same error.

What I don't know is if it's possible to successfully burn a Ubuntu
start-up flash-drive when Ubuntu is not installed on the system (ie.
only using a temporary Ubuntu via start-up flashdrive).

I also don't know if the solution I describe above to reinstall the
missing grub would attempt to reinstall the missing grub on the flash-
drive or on the computer itself.  Could this be sabotaging the
reinstall?  When I first made the 16.1 drive it was with a functioning
windows system.  Do I need to burn a new disc from a working laptop?
That is, is it not possible to update, upgrade and reinstall Ubuntu via
a presumably faulty Ubuntu start-up flash-drive.

I just can't think of why else the problem persists with the new flash-
drive.

Thanks for the help!

I love Ubuntu!

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CasperVersion: 1.380
Date: Sun Aug 27 22:04:03 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1713364

Title:
  grub-efi-amd64signed package not installed

Status in grub-installer package in Ubuntu:
  New

Bug description:
  I had Ubuntu 16.1 installed on my hp pavillion laptop.  It  started
  acting eratic and finally crashed with a "There is no operating system
  installed on this hard-drive" error.  I am currently running Ubuntu
  17.04 from a start-up flash-drive.  I also have the original start-up
  flash-drive for Ubuntu 16.1 which I originally installed Ubuntu from.
  Both start-up drives work fine from the "try Ubuntu" mode, but when I
  try to install or reinstall Ubuntu I get a "grub-efi-amd64sined"
  package not installed error and the system won't boot.  This is weird
  because I got this first when I tried to reinstall from the original
  10.4 drive.  Then, using Ubuntu 16.1 from that original flash-drive, I
  downloaded and created a new start-up flash-drive, this time with
  Ubuntu 17.04. The drive works in the try version but when I try to
  install it I get the same grub error.

  I would assume that the new download should be complete.  How could it
  have the same error?  Especially when I chose to erase the existing
  16.1 and replace it with the new 17.4.

  I then tried a solution I found online on the Ubuntu Community:

  $ sudo apt update
  $ sudo apt upgrade
  $ sudo apt dist-upgrade

  then:

  $ sudo apt install --reinstall grub
  $ sudo apt install --reinstall grub2-common
  $ sudo apt install --reinstall grub-efi-amd64
  $ sudo apt install --reinstall grub-efi-amd64-bin
  $ sudo apt autoremove
  $ sudo apt install grub-efi-amd64-signed

  The only irregularities I encountered were once during the upgrade it
  detected a difference between the coding from the software
  manufacturer and the local one on my computer, and gave me a list of
  options.  I chose to keep the local version since I believe I have the
  newest ubuntu desktop (17.4).

  Everything seemed to work as planned.  It didn't find the first grub
  to reinstall but it said that it is replaced by the same grup2 and
  grub efi as above, so I figured I was on the right track.

  Only problem is when I again tried to install Ubuntu 17.4 on my
  computer I get the same error.

  What I don't know is if it's possible to successfully burn a Ubuntu
  start-up flash-drive when Ubuntu is not installed on the system (ie.
  only using a temporary Ubuntu via start-up flashdrive).

  I also don't know if the solution I describe above to reinstall the
  missing grub would attempt to reinstall the missing grub on the flash-
  drive or on the computer itself.  Could this be sabotaging the
  reinstall?  When I first made the 16.1 drive it was with a functioning
  windows system.  Do I need to burn a new disc from a working laptop?
  That is, is it not possible to update, upgrade and reinstall Ubuntu
  via a presumably faulty Ubuntu start-up flash-drive.

  I just can't think of why else the problem persists with the new
  flash-drive.

  Thanks for the help!

  I love Ubuntu!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubiquity 17.04.9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CasperVersion: 1.380
  Date: Sun Aug 27 22:04:03 2017
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=unknown
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   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/1713364/+subscriptions



More information about the foundations-bugs mailing list