[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system
sudodus
1895329 at bugs.launchpad.net
Sat Oct 10 06:15:39 UTC 2020
The first test results from the current daily Ubuntu Groovy iso file
$ ls -l groovy-desktop-amd64.iso
-rw------- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
indicate that that squashing bug #1886148 did also squash bug #1895329,
but now there is another 3rd partition, and we should look for a 4th
partition.
sudodus at bionic64 /media/multimed-2/test/ubuntu $ sudo kpartx -av groovy-desktop-amd64.iso
add map loop0p1 (253:0): 0 5725588 linear 7:0 64
add map loop0p2 (253:1): 0 9952 linear 7:0 5725652
add map loop0p3 (253:2): 0 600 linear 7:0 5735604
sudodus at bionic64 /media/multimed-2/test/ubuntu $ lsblk -f /dev/loop0
NAME FSTYPE LABEL UUID MOUNTPOINT
loop0 iso9660 Ubuntu 20.10 amd64 2020-10-09-21-15-31-00
├─loop0p1 iso9660 Ubuntu 20.10 amd64 2020-10-09-21-15-31-00
├─loop0p2 vfat ESP 6508-0C9E
└─loop0p3
sudodus at bionic64 /media/multimed-2/test/ubuntu $ sudo kpartx -d groovy-desktop-amd64.iso
loop deleted : /dev/loop0
After booting, there is a 'writable' partition.
sudodus at bionic64 /media/multimed-2/test/ubuntu $ lsblk -f /dev/sdc
NAME FSTYPE LABEL UUID MOUNTPOINT
sdc iso9660 Ubuntu 20.10 amd64 2020-10-09-21-15-31-00
├─sdc1 iso9660 Ubuntu 20.10 amd64 2020-10-09-21-15-31-00
├─sdc2 vfat ESP 6508-0C9E
├─sdc3 iso9660 Ubuntu 20.10 amd64 2020-10-09-21-15-31-00
└─sdc4 ext4 writable 8b73f753-eb94-40ec-8995-f57c64933d3f
--
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
More information about the foundations-bugs
mailing list