This is my first post here, and I have been encouraged to write this because we worked on this problem two times (see https://forum.ubuntuusers.de/topic/server-haengt-beim-einspielen-der-updates/)
I have a small server on a RaspberryPi with Nextcloud which is administrated via SSH. I recently upgraded it to 22.04.1 LTS.
The latest upgrades made some problems:
~$ sudo apt upgrade
E: Der dpkg-Prozess wurde unterbrochen; Sie müssen manuell »sudo dpkg --configure -a« ausführen, um das Problem zu beheben.
~$ sudo dpkg --configure -a
linux-firmware (20220329.git681281e4-0ubuntu3.6) wird eingerichtet ...
update-initramfs: Generating /boot/initrd.img-5.15.0-1017-raspi
This process does not finish; i had to ctrl+c it.
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
tmpfs 92M 3,0M 89M 4% /run
/dev/mmcblk0p2 59G 23G 34G 41% /
tmpfs 459M 0 459M 0% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
/dev/mmcblk0p1 253M 118M 135M 47% /boot/firmware
tmpfs 92M 4,0K 92M 1% /run/user/1000
~$ ls -la /boot
insgesamt 67079
drwxr-xr-x 4 root root 4096 Nov 2 16:48 .
drwxr-xr-x 20 root root 4096 Nov 2 16:35 ..
-rw-r--r-- 1 root root 242965 Okt 14 10:12 config-5.15.0-1017-raspi
lrwxrwxrwx 1 root root 44 Okt 27 16:27 dtb -> dtbs/5.15.0-1017-raspi/./bcm2709-rpi-2-b.dtb
lrwxrwxrwx 1 root root 44 Okt 27 16:27 dtb-5.15.0-1017-raspi -> dtbs/5.15.0-1017-raspi/./bcm2709-rpi-2-b.dtb
drwxr-xr-x 28 root root 4096 Okt 21 06:54 dtbs
drwxr-xr-x 3 root root 11264 Jan 1 1970 firmware
lrwxrwxrwx 1 root root 28 Okt 21 06:50 initrd.img -> initrd.img-5.15.0-1017-raspi
-rw-r--r-- 2 root root 27971743 Nov 2 16:25 initrd.img-5.15.0-1017-raspi
-rw-r--r-- 2 root root 27971743 Nov 2 16:25 initrd.img-5.15.0-1017-raspi.dpkg-bak
-rw-r--r-- 1 root root 0 Nov 2 16:48 initrd.img-5.15.0-1017-raspi.new
lrwxrwxrwx 1 root root 28 Okt 27 12:07 initrd.img.old -> initrd.img-5.15.0-1017-raspi
-rw------- 1 root root 4113043 Okt 14 10:12 System.map-5.15.0-1017-raspi
lrwxrwxrwx 1 root root 25 Okt 21 06:50 vmlinuz -> vmlinuz-5.15.0-1017-raspi
-rw------- 1 root root 8348160 Okt 14 10:12 vmlinuz-5.15.0-1017-raspi
lrwxrwxrwx 1 root root 25 Okt 27 12:07 vmlinuz.old -> vmlinuz-5.15.0-1017-raspi
After that it seems that /boot is too small to complete the update-initramfs-process again. I had to move the file initrd.img-5.15.0-1017-raspi.dpkg-bak to /home/myuser to finish the next upgrade.
My question: Why is the partition /boot designed so small? After downloading the image I put it on a sd-card with Raspberry Pi Imager, and the partition size is already set there and cannot be changed. For me this never happened with Ubuntu <22.04.1 LTS; is there maybe a bigger initrd.img-*-file than before? This problem was really annoying and I cannot imagine I am the only one to get troubled with this.
Thanks in advance!
