[Bug 1851955] Re: ubuntu 19.10 boot installer failed

Ian Scott 1851955 at bugs.launchpad.net
Wed Jan 8 01:03:34 UTC 2020


Hi Steve

Thanks - I remember the sudo dpkg --configure -a command and have had to
use it before - didn't know what it was called though. I ran it but the
terminal had no feedback to make. I then ran your new command and here is
the output

Could not set BootOrder: Invalid argument
8


Ian

On Wed, Jan 8, 2020 at 1:00 PM Steve Langasek <steve.langasek at canonical.com>
wrote:

> On Tue, Jan 07, 2020 at 11:40:05PM -0000, Ian Scott wrote:
> > I'm at the library at the moment on another notebook but I'll be back in
> > an hour or so to try the new idea.  However "And then, could you try
> > finishing the configuration of the grub package?"
>
> > Unfortunately I have no idea at all how to do this. Can you provide some
> > instructions Steve? I only use computers, mainly for math analysis and
> > simulations, but I have very little understanding of what goes on inside
> > the OS.
>
> >From a console, you should be able to run 'sudo dpkg --configure -a' and
> watch it attempt to finish configuration of the grub packages that
> previously failed to configure.
>
> > On Wed, Jan 8, 2020 at 11:50 AM Steve Langasek <
> steve.langasek at canonical.com>
> > wrote:
> >
> > > The error message appears to be correct, you have both 2002 and 2003 in
> > > your BootOrder but neither is present in your list of boot options.  I
> > > don't think this is the cause of the grub failure.  Could you try
> > > instead running the command:
> > >
> > > sudo efibootmgr -o 0000,3000,0001,0002,2001; echo $?
> > >
> > > and see if that works better?  And then, could you try finishing the
> > > configuration of the grub package?
> > >
> > > Interestingly, I notice that Sri also has a BootOrder variable which
> > > references a non-existent boot entry.  So it's possible this is
> related.
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1851955
> > >
> > > Title:
> > >   ubuntu 19.10 boot installer failed
> > >
> > > Status in grub2 package in Ubuntu:
> > >   New
> > > Status in shim-signed package in Ubuntu:
> > >   Incomplete
> > >
> > > Bug description:
> > >   Installed on an ENVY notebook, installation afiled at the end with no
> > >   bootloader message
> > >
> > >   ProblemType: Bug
> > >   DistroRelease: Ubuntu 19.10
> > >   Package: ubiquity 19.10.21
> > >   ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
> > >   Uname: Linux 5.3.0-18-generic x86_64
> > >   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> > >   ApportVersion: 2.20.11-0ubuntu8
> > >   Architecture: amd64
> > >   CasperVersion: 1.427
> > >   Date: Sun Nov 10 08:32:41 2019
> > >   InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd
> > > quiet splash --- maybe-ubiquity
> > >   LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
> > >   SourcePackage: ubiquity
> > >   UpgradeStatus: No upgrade log present (probably fresh install)
> > >
> > > To manage notifications about this bug go to:
> > >
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to shim-
> > signed in Ubuntu.
> > https://bugs.launchpad.net/bugs/1851955
> >
> > Title:
> >   ubuntu 19.10 boot installer failed
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions
>
> --
> Steve Langasek                   Give me a lever long enough and a Free OS
> Debian Developer                   to set it on, and I can move the world.
> Ubuntu Developer                                   https://www.debian.org/
> slangasek at ubuntu.com                                     vorlon at debian.org
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1851955
>
> Title:
>   ubuntu 19.10 boot installer failed
>
> Status in grub2 package in Ubuntu:
>   New
> Status in shim-signed package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Installed on an ENVY notebook, installation afiled at the end with no
>   bootloader message
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: ubiquity 19.10.21
>   ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
>   Uname: Linux 5.3.0-18-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu8
>   Architecture: amd64
>   CasperVersion: 1.427
>   Date: Sun Nov 10 08:32:41 2019
>   InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd
> quiet splash --- maybe-ubiquity
>   LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions
>

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

Title:
  ubuntu 19.10 boot installer failed

Status in grub2 package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Incomplete

Bug description:
  Installed on an ENVY notebook, installation afiled at the end with no
  bootloader message

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubiquity 19.10.21
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.427
  Date: Sun Nov 10 08:32:41 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions



More information about the foundations-bugs mailing list