grub-install /dev/dm-0 fails for "Erase entire disk" install type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
This should not be happening at all. Install fails with a grub-install error; failing to find /dev/dm-0. Interestingly, I picked "Erase entire disk", for a system (Dell Vostro V130) that was previously installed with Xubuntu. Given that "Erase entire disk" should just wipe all partitions and create new ones, none of which using LVM (because that was not picked at all, neither LVM not LVM with crypto); it should not be trying to use dm-0 at all.
There are other errors earlier on with ubiquity failing to properly recognize the type of filesystem.
Test Case
1. Install a system using LVM (not encryted) and proceed with the installation
2. Install a second time on the same system but this time select "Erase entire disk"
Expected result
Second installation is successful
Actual result
grub-installer fails because it tries to install grub on /dev/dm-0
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:14:21 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: id-59e7bcfce82483e3f1f4632b |
Changed in ubuntu-release-notes: | |
status: | New → Fix Released |
Changed in ubiquity (Ubuntu): | |
status: | Won't Fix → Confirmed |
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here: iso.qa. ubuntu. com/qatracker/ reports/ bugs/1724417
http://