Ubuntu Mate 20.04 kernel updates 1042 and 1043 attempt to create symlinks in /boot even though /boot on Raspberry Pi is vfat
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The focal (20.04) kernel updates 1042 and 1043 attempt to create symlinks in /boot. This was tested on a Pi 4 (arm64).
On Raspberry Pi, /boot is a vfat partition; vfat does not support symlinks.
I think (but am not sure) that /boot on Raspberry Pi has to be vfat (cannot be ext3/4 or another filesystem that supports symlinks)
This problem manifests itself as:
# apt-get upgrade
[...]
Setting up linux-image-
/etc/kernel-
Processing triggers for linux-image-
/etc/kernel/
update-initramfs: Generating /boot/initrd.
Using DTB: bcm2711-rpi-4-b.dtb
Installing /lib/firmware/
Taking backup of bcm2711-
Installing new bcm2711-
ln: failed to create symbolic link '/boot/
run-parts: /etc/initramfs/
run-parts: /etc/kernel/
dpkg: error processing package linux-image-
installed linux-image-
Errors were encountered while processing:
linux-image-
E: Sub-process /usr/bin/dpkg returned an error code (1)
Even when /etc/kernel-
Kernel Image management overrides
See kernel-img.conf(5) for details
do_symlinks = no
no_symlinks = yes
do_bootloader = no
link_in_boot = no
No. On Ubuntu raspi the VFAT partition is mounted on /boot/firmware, not /boot. There is something wrong with your system setup.
ubuntu@ rpi-4b- rev1d4- d9f5:~$ mount | grep mmc discard, errors= remount- ro) fmask=0022, dmask=0022, codepage= 437,iocharset= ascii,shortname =mixed, errors= remount- ro)
/dev/mmcblk0p2 on / type ext4 (rw,relatime,
/dev/mmcblk0p1 on /boot/firmware type vfat (rw,relatime,