Thank you for the explanation. I think it's good to have this in mind
for the future (when someone notices this being broken there as well),
but in this case I'm taking it off from the .4 milestone.
** Changed in: finalrd (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => None
--
You received this
Hi, interestingly this is _not_ reproducible on Focal. I started seeing
the failures in Impish. On paper the issue should be present on Focal,
but due to its racey nature it's difficult tell exactly why it is not
showing up.
I can quickly prepare a SRU upload with only the minimal Before= change,
What is the status of this for 20.04.4? Is this just a matter of
backporting the finalrd change from 9 to impish and focal? Is there
anything blocking this? Since I assume this is reproducible on focal as
well, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: finalrd (Ubuntu Focal)
Milestone: None => ubuntu-20.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data failed to read block
To
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data failed to read block
To manage
I can confirm the Jammy arm64 images are rebooting fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data
This bug was fixed in the package finalrd - 9
---
finalrd (9) jammy; urgency=medium
* finalrd.service: set Before=shutdown.target.
Eliminate race between finalrd and shutdown.target.
See also: lintian's systemd-service-file-shutdown-problems.
Thanks to Dimitri John
I've uploaded this for Paride in the interest of getting it into the
archive quickly (I assume he's in bed).
$ dput finalrd_9_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /home/bdmurray/source-trees/finalrd/finalrd_9_source.changes: Valid
signature from
** Tags removed: amd64 apport-bug apport-collected id-5d557981385f317578944153
verification-done verification-done-bionic
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~paride/finalrd/+git/finalrd/+merge/413012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live
** Also affects: casper (Ubuntu Jammy)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: High
Status: Confirmed
** Also affects: finalrd (Ubuntu Jammy)
Importance: Undecided
Assignee: Paride
** Merge proposal linked:
https://code.launchpad.net/~paride/ubuntu/+source/finalrd/+git/finalrd/+merge/412931
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to
Actually there may be an even better solution:
Before=shutdown.target
which lintian has been nagging us about:
https://lintian.debian.org/tags/systemd-service-file-shutdown-problems
"There is race condition between stopping units and systemd getting a
request to exit the main loop, so it
@brian-murray prepared a test Jammy arm64 ISO with finalrd from the PPA
above (serial: 20211208.1). I chose arm64 as it's the architecture
most heavily affected by this issue (at least in our test environment).
I performed several ISO test runs on the image and the success rate went
from <50%
** Changed in: finalrd (Ubuntu Eoan)
Status: New => Won't Fix
** Also affects: casper (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: finalrd (Ubuntu Hirsute)
Importance:
As we have a Conflicts=umount.target, then
> It doesn't matter which of the two ordering dependencies is
> used, because stop jobs are always ordered before start jobs
literally as xnox said. I'm preparing a finalrd with
Before=umount.target in a PPA.
--
You received this bug notification
Hmm but umount.target is special (as in systemd.special(7)), so that's
not so obvious...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or
From [1]:
> if a unit is configured with After= on another unit,
> the former is stopped before the latter if both are
> shut down.
so maybe we need After=umount.target in finalrd.service.
[1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html
--
You received this bug
I wonder if we need before= or after= umount.target
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data
Added a subiquity task as this could be worked around there, while I
think the kernel tasks could be set to Invalid or Wontfix...
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Our installer could stop finalrd before issuing shutdown too, as a
workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
we should check ordering of services for stop in a booted live session
(desktop / server / next-installer) and then figure out if we can add
additional dependencies to finalr.service (after) such that its stop is
ordered before everything else is stopped.
** Also affects: finalrd (Ubuntu)
I have more evidence that the issue is indeed the same.
The original bug was fixed by making casper depend on finalrd, see the
explanatory casper 1.420 d/changelog entry reported in comment 33.
However it appears that the fix is racey: sometimes finalrd is not
triggered in time at
Attachment: full dmesg.
** Attachment added: "dmesg.log.xz"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5532416/+files/dmesg.log.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am occasionally seeing this again with the Impish live-server
(subiquity) daily ISO images. I saw this happening only on ppc64el and
on arm64, and only on preseeded installs (via answers.yaml).
This doesn't prevent the installation from succeeding: what fails is
just the post-install reboot.
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data failed to read block
To manage
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package casper - 1.394.3
---
casper (1.394.3) bionic; urgency=medium
* Cherrypick from eoan: Add dependency on finalrd for reliable
live-session shutdown. Casper setup live systems do have layering
violations (/ actually depends on /cdrom) and it
I verified on Ubuntu Desktop 20200128, that casper from proposed pulls
finalrd and that it successfully fixes the issue on both a VM and
baremetal.
Marking as verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
Hello Jean-Baptiste, or anyone else affected,
Accepted casper into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/casper/1.394.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. To properly
** Description changed:
Last known good image: Eoan Ubuntu Desktop 20190715
+
+ Similar results started to happen with new linux-hwe kernel based on
+ eoan for 18.04.4 release.
Test Case:
1. Boot eoan desktop to a live session
2. Wait a couple of minutes until snapd settles
3.
** Also affects: casper (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance:
Install into QEMU/KVM vm with Ubuntu desktop 20191001.2 completed
successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm
This bug was fixed in the package casper - 1.421
---
casper (1.421) eoan; urgency=medium
* Drop empty directory (doesn't track well in git)
* Use debian/casper.dirs to install conf.d
casper (1.420) eoan; urgency=medium
* Add dependency on finalrd for reliable live-session
** Changed in: casper (Ubuntu Eoan)
Importance: High => Critical
** Changed in: casper (Ubuntu Eoan)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
subiquity image has similar, but it manages to reboot fine (attaching
subiquity screenshots)
squashfs errors are still bad though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
** Attachment added: "subiquity-2.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5291858/+files/subiquity-2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "subiquity-1.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5291857/+files/subiquity-1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While recreating this with an image from today I noticed that before
seeing the squashfs errors, after pressing an error key in the plymouth
screen, there were messages regarding "Failed unmounting /cdrom". I've
attached a screenshot showing the messages.
** Attachment added:
I'm having this problem when installing in QEMU/KVM vms. If I disconnect
the ISO as per install instructions, the system hangs, with the errors
shown in the OP if I choose another tty. Leaving the ISO attached allows
the system to reboot but it boots into the ISO.
--
You received this bug
Booted daily Ubuntu x86_64 19.10 (2019-09-17) on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
Booted live, waited 5 mins
Suspend system, waited 2 mins (was looking at wrong test-steps screen, noting
here as 2 mins had passed before I noticed my mistake)
resumed system, waited 2 mins
I tested it with the current iso (2019-09-17).
1. Booted into live session
2. Waited for 30 minutes
3. Restarted via System menu
4. Restart of the system was successful without any error
Can anybody test it and verify it if it works for them too?
Thanks
--
You received this bug notification
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data failed to read block
To
** Also affects: casper (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Also affects: linux (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Last known good image: Eoan Ubuntu Desktop 20190715
Test Case:
1. Boot eoan desktop to a live session
2. Wait a couple of minutes until snapd settles
3. Reboot the system from the system menu or from the command line
Expected result:
The system reboots
** Tags added: id-5d557981385f317578944153
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
squashfs_read_data failed to read
I had a look at this and got pretty confused! Feels more like a kernel
problem than a casper one, somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from
48 matches
Mail list logo
