Installation failed to install grub2

Bug #1781187 reported by Owen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Installation all went well but then got message saying it couldn't install grub2 and the system would be unable to boot! Is there no way of checking this ahead of starting anything at all to do with installation?!

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: Wed Jul 11 11:34:25 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=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
Owen (osavill-z) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

Your disk is currently partitioned to boot in bios mode, but you booted the installer in EFI mode. You either need to boot the installer in bios mode, 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: New → Invalid
Revision history for this message
Owen (osavill-z) wrote :

My point still stands however. The point I was raising wasn't that I was using BIOS or EFI but rather the installation progressed through the entire process and then left the system unbootable! This is surely unacceptable; especially for someone who may be new to Linux / Ubuntu and may be dual booting with some Windows setup who would then be left with a potentially unbootable system and without the systems knowledge to rectify the situation.

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.