Pi images for jammy exclude boot partition mount
Bug #1950677 reported by
Dave Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-image (Ubuntu) |
Fix Released
|
Undecided
|
William Wilson | ||
Jammy |
Fix Released
|
Undecided
|
William Wilson |
Bug Description
The current jammy images for Pi appear to be missing a line for the "system-boot" partition in /etc/fstab with the result that the boot partition is not mounted at runtime (and various operations which rely on copying to the boot partition, usually mounted under /boot/firmware, fail in interesting ways).
tags: | added: raspi-image |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Dave Jones (waveform) |
tags: | added: fr-1904 |
affects: | livecd-rootfs (Ubuntu Jammy) → ubuntu-image (Ubuntu Jammy) |
Changed in ubuntu-image (Ubuntu Jammy): | |
assignee: | Dave Jones (waveform) → William Wilson (jawn-smith) |
status: | Confirmed → In Progress |
Changed in ubuntu-image (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package ubuntu-image - 2.1+22.04ubuntu1
---------------
ubuntu-image (2.1+22.04ubuntu1) jammy; urgency=medium
[ Łukasz 'sil2100' Zemczak ]
* Make sure the generated disk IDs are unique.
* Add support for specifying a disk sector-size to use while building the
images (LP: #1942416)
[ William 'jawn-smith' Wilson ]
* Pull in upstream change from go-diskfs to fix integer overflows on armhf
(LP: #1949208)
* Add logic to name system-data partitions "writable" if a name isn't
specified (LP: #1951334)
* Fix logic for filesystem labeling in /etc/fstab (LP: #1950677)
* Add --validation flag (LP: #1933665)
-- William 'jawn-smith' Wilson <email address hidden> Tue, 02 Nov 2021 12:57:01 -0500