** Changed in: casper (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895329
Title:
when booting cloned live drive 3rd partition is created without
I tested also with the current daily Lubuntu Groovy iso file (dated
2020-10-10) and when cloned to a USB pendrive and booted, a 'writable'
partition is created as it should. This is a third indication that this
bug is squashed.
--
You received this bug notification because you are a member of
I zsynced the current daily Xubuntu Groovy iso date (dated 2020-10-10),
and when cloned to a USB pendrive and booted, a 'writable' partition is
created as it should.
This system was cloned directly after testing a larger Ubuntu Groovy
system, and with earlier iso files, it was likely to fail to
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
This bug is still alive in the current Ubuntu Desktop Groovy daily iso
file dated October 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895329
Title:
when booting cloned live drive 3rd
** Changed in: casper (Ubuntu)
Milestone: None => ubuntu-20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895329
Title:
when booting cloned live drive 3rd partition is created without file
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895329
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The bug is still there in the current daily Lubuntu Groovy iso file
(beta candidate). See the attached screenshot.
Please notice that the error is not temporary. It persists after reboot.
** Attachment added: "bug-1895329-in-lubuntu-beta-candidate.jpg"
Oops, I dont think F6 and persistent during boot works with 20.10. I
think I meant pressing "e" and typing persistence, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895329
Title:
when
Used "sudo mkfs.ext4 -L writable /dev/sdx3"
And partition sdx3 became persistent after using F6 and persistent
during boot.
Being able to make the spare space useful between Ubuntu and Windows for
data is still a big deal for me.
--
You received this bug notification because you are a member
Using sudo mkfs.ntfs -f -L data /dev/sdx3 and sudo mkfs.vfat -n data /dev/sdx3
I can format the third partition.
It is then accessible in Disks but it is not accessible in Windows.
With 20.04 the third partition was accessible in Windows after such formatting.
I have not tested if It can be
Now I tested the current Lubuntu Groovy iso file dated Sept 21. I could
repeat the results from yesterday: The Lubuntu iso file makes USB boot
drives, that can create a file system in the third partition, while the
Ubuntu Desktop and Xubuntu iso files (of the same date, Sept 21, fail to
do so.
--
Something has happened, that I discovered today: Lubuntu works.
I tested the current Groovy iso files of Ubuntu Desktop, Lubuntu and
Xubuntu.
- with the USB drives in used state (with various data, typically
leftovers after previous tests with live or persistent live systems)
- both in UEFI
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
This bug is still alive when tested with the current daily Ubuntu Groovy
iso file cloned to a USB drive and tested in a Dell Precision M4800.
This iso file is improved in many other ways, but this bug remains to be
fixed. Maybe there is some kind of race condition, that affects drives,
that were
I could reproduce the bug with today's daily Xubuntu Groovy iso file
(with the leftovers after testing yesterday's daily Lubuntu Groovy iso
fil in the 60 GB SSD, OCZ-AGILITY ITY3 drive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Not exactly reproducible here. If I download the lubuntu desktop ISO,
extend it with 'dd if=/dev/zero of=lubuntu-groovy-amd64.iso count=0 bs=1
seek=$((4*1024*1024*1024))', attach it to a VM as a virtio disk, and
boot into it, I get a fully configured 'writable' partition, which is
mounted at
Sorry for the garbled list in 'details.txt', the non-standard characters
are not rendered nicely by Firefox. Here is a better list from this
computer:
lubuntu@lubuntu:~$ lsblk -lo name,fstype,label,size
NAME FSTYPE LABEL SIZE
loop0 squashfs 1.6G
19 matches
Mail list logo
