Install 19.10 on Alieanware Steammachine R2

Bug #1851560 reported by Sønke Lorenzen
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

I attempted to install 19.10 on an Alienware Steammachine R2 along SteamOS 2.0 and got an error at the end. The installation was to a nvme where I had left around 140GB unused partition space, which the installer chose correctly. SteamOS is installed on a separate harddisk.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.12
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CasperVersion: 1.419
Date: Wed Nov 6 20:57:44 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sønke Lorenzen (solorenzen) wrote :
Revision history for this message
Sønke Lorenzen (solorenzen) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you give some details on the installation mode and the error? When did you get the error, on what installer part? What was the UI/message exactly?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Sønke Lorenzen (solorenzen) wrote :

Thank you for looking into this.

The error came at the bootloader install part. I do not remember the exact wording and did not take a screenshot, but it was at least similar to what UbiquitySyslog.txt logged:

Nov 6 19:57:37 ubuntu /plugininstall.py: "GrubInstaller failed with code %d" % ret)
Nov 6 19:57:37 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1

I was able to install grub from a chroot and then boot and it is a working system. There where leftovers since the cleanup part was not run. I did find some installed packages named with ubiquity which I uninstalled.

But looking at UbiquitySyslog.txt which start at September 26 I now realize that I used the beta installer from September 26. The September 26 part of that log is from another and successful install on a different system.

Since I did not use this install much, I will download the released installer and remove the partitions created by this install and try again to see if it the new installer will install grub successfully.

And report back here about how that goes.

Revision history for this message
Sønke Lorenzen (solorenzen) wrote :

I got the same result with a fresh downloaded installer and reported #1852333 for that.

Changed in ubiquity (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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