[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system

[sudodus]

I have seen several cases, where bugs appear in situations typical for
end users, who want to install Ubuntu and Ubuntu family flavours in
their computers.

If I understand correctly, you have not seen these bugs in your internal
tests. Instead of testing only in virtual machines, I think at least
some of you developers should have separate test computers, where you
can test things directly, for example booting from USB drives. Otherwise
the debug process will be very slow because of the delay in the
communication between you (developers) and us (testers).

-o-

I did some tests with yesterday's Lubuntu Groovy iso file, the same as
in the previous test.

USB drives

- a 60 GB SSD, OCZ-AGILITY ITY3 in a USB to SATA adapter
- a 32 GB pendrive, Sandisk Extreme
- a 16 GB pendrive, Sandisk Extreme

Process: Cloning

Test computer: http://www.toshiba.se/laptops/satellite-pro/c850
/satellite-pro-c850-19w/

(This time *not* the Lenovo V130)

Tested with the USB drives

- in used state (with various data, typically leftovers after previous
tests with live or persistent live systems).

- when completely overwritten with zeros (matching your test case)

-o-

I can draw the following conclusions:

- I reproduce the bug, that a third partition is created, but without a
file system, when the USB drives are 'in used state'

- I reproduce your result, that a third partition is created with an
ext4 file system and the label 'writable', when the drives were
completely overwritten with zeros.

Please notice, that I have not had this issue before you started to
modify the boot system. I have created many live drives by cloning from
Ubuntu, Lubuntu ... 20.04.x and Groovy until the beginning of July, and
it was *never* necessary to overwrite the whole drive with zeros (in
order to get a third partition is created with an ext4 file system and
the label 'writable').

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1895329

Title:
  when booting cloned live drive 3rd partition is created without file
  system

Status in casper package in Ubuntu:
  Incomplete

Bug description:
  When iso testing the current daily Lubuntu iso file (dated 2020-09-11),
  I notice that a third partition is created (during the boot process),
  but no file system is recognized by lsblk -f, and it is not used for
  logging (as we are used to from Focal and previous versions of Groovy).

  In this case it is seen by lsblk as /dev/sda3. See details in the
  attached file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: casper 1.452
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  Date: Fri Sep 11 17:20:03 2020
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200911)
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.casper.conf: 2020-09-11T17:08:26.454154

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895329/+subscriptions