subiquity 22.02.2+git180.1b7ab29e: corrupt partitioning menu

Bug #1968160 reported by Heinrich Schuchardt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity (Ubuntu)
Fix Released
Undecided
Dan Bungert

Bug Description

I tried to install with subiquity 22.02.2+git180.1b7ab29e on SiFive Unmatched

I have two disks:
/dev/sda
/dev/nvme0n1

By accicent I chose complete device and the /dev/nvem0n1 device and hit "Done".

I then used "Back" and chose the /dev/sda1 device.

After pressing "Done" both devices were marked to be formatted. This would have deleted the operating system on /dev/nvme0n1. The only solution was to reset the system.

This problem should be fixed before the Jammy release.

Tags: jammy
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

On /dev/nvme0n1 the volume group is called ubuntu-vg.

When installing on /dev/sda the same volume group name is chosen.

This does not make sense. A different group name should be used.

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

My installation on /dev/nvme0n1 does not use any volume group.

So I wonder why in the subiquity display volume group "ubuntu-vg" was shown for /dev/nvme0n1.

Revision history for this message
Dan Bungert (dbungert) wrote :

@Heinrich, when you selected the wrong disk, how far did you get? Did you say Continue on the dialog titled "Confirm destructive action"?

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

@Dan, no I caught my error when seeing the list of partition usages. I did not destroy my preexisting installation on /dev/nvme0n1.

Dan Bungert (dbungert)
Changed in subiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Bungert (dbungert) wrote :

For the LP description issue, I have opened https://github.com/canonical/subiquity/pull/1263.
For the comment about a duplicate ubuntu-vg entry, I can't reproduce that problem.

Changed in subiquity (Ubuntu):
assignee: nobody → Dan Bungert (dbungert)
status: Confirmed → In Progress
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

As of subiquity 22.04.1 I see no problem. So let't put this to "Fix committed".

Actually a volume group "ubuntu-vg-1" with a distinct name is created on the second install:

sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 1G 0 part
├─sda2 8:2 0 1.5G 0 part
└─sda3 8:3 0 230.3G 0 part
  └─ubuntu--vg-ubuntu--lv 253:0 0 100G 0 lvm
sdb 8:16 1 29.8G 0 disk
├─sdb1 8:17 1 1G 0 part /boot/efi
├─sdb2 8:18 1 2G 0 part /boot
└─sdb3 8:19 1 26.8G 0 part
  └─ubuntu--vg--1-ubuntu--lv 253:1 0 13.4G 0 lvm /

Changed in subiquity (Ubuntu):
status: In Progress → Fix Committed
description: updated
Changed in subiquity (Ubuntu):
status: Fix Committed → Fix Released
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.