[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system
Michael Hudson-Doyle
1895329 at bugs.launchpad.net
Wed Sep 16 09:38:33 UTC 2020
It could be a race, this is the code that creates the partition and
filesystem:
echo "start=$start" | sfdisk --no-reread -q $DEVICE -a || return
for d in ${DEVICE}$newpartno ${DEVICE}p$newpartno ${DEVICE}-part$newpartno; do
if [ -e $d ]; then
mkfs.ext4 -q -L "$(root_persistence_label)" -F $d
break
fi
done
udevadm trigger
udevadm settle
But my understanding is that sfdisk (with the options we use here)
doesn't return until it has told the kernel about the new partitions.
I also doubt that the changes to image mastering made a difference here
and suspect it was some other change that coincidentally happened around
the same time but who knows. (If the partition wasn't being created, I
could quite easily believe the mastering changes would make a
difference). I'll see if I can reproduce on my laptop tomorrow.
--
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