ubuntu 20 failed install on Dell Precision 5510 Windows 10 - grub-install: error: failed to register the EFI boot entry: Invalid argument.

Bug #1875911 reported by Vidal Montgomery
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

was installing ubuntu on a windows 10 machine when I was prompted for the WiFi again in mid install, i supplied it and the the installer simultaneously reported that installation had failed AND that installation had been successful and I needed to reboot. We'll see which one was right...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 15:43:31 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Vidal Montgomery (vmuntapped) wrote :
summary: - ubuntu 20 failed install on Dell Precision 5510 Windows 10
+ ubuntu 20 failed install on Dell Precision 5510 Windows 10 - grub-
+ install: error: failed to register the EFI boot entry: Invalid argument.
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in grub-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Rob (desmobob) wrote :

I experienced the same issue, albeit without the complication of a second drive containing another O/S. My workaround was to perform an install without WiFi connectivity and then after completing the install perform the necessary updates and third party driver modifications. The installation consumed much more time due to the latter event unfortunately.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.