failed writing grub in UEFI install - win8.1 based Windows 10

Bug #1628364 reported by John Andrejsons
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

I revived my ubuntu on a Windows 7 based Windows 10 laptop after a memory upgrade and upgraded further to the 16.04 LTS. I was so impressed with the performance that I undertook to install it on my friends Windows 8 PC. He chronically resets to Windows 8.0 factory specs when his system slows to non-usability, I have a Windows 8.1 based Windows 10 AE PC, as well. The report is from this one.

I am installing from a memory stick. After some booting struggles with legacy settings, I thought that I had it right. The stick seems fine and it did install somewhat successfully on the Windows 8 system and I get a four item grub menu on boot. ununtu goes to black and Windows boots fine. I can get to ubuntu in safe mode and I shall work on that.

Meanwhile this install starts with about twenty more "things"(I am not linux-literate) than the 70 or so on the other system at the beginning of the install and I get some mount dialogues and I chose the easy way that does not allow repartitioning. I avoided the proprietary code part so as not to disturb the safe boot settings.

I don't know if this background helps more than the system generated data.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CasperVersion: 1.376
Date: Tue Sep 27 21:39:03 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
John Andrejsons (andrejs-m) wrote :
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.