>>109522226
>if the update manager messes with the kernel.
It does update the kernel package.
It also never runs "autoremove".
It's a major glaring flaw with the apt package manager that it will happily let your system update into a state where there isn't enough room left for the kernel to unpack itself.
There should be a huge flashing red WARNING that occurs when it sees those kernel packages accumulating and the space in /boot getting too low, but there isn't.
To fix your problem you just need to access the "advanced boot" options and manually boot into an older
Kernel version whose initrd.img file is already available in /boot.
Once you're into the system you need to purge the other kernel package versions (NOT THE ONE YOU ARE CURRENTLY RUNNING)
# show currently running kernel version
uname -r
# list all the explicitly versioned kernel packages on your machine that are NOT the one you're currently running
dpkg -l | grep -E '^ii' | grep -E 'linux-image-[0-9]' | awk '{print $2}' | grep -v "$(uname -r)"
# remove versioned kernel image package
sudo apt-get purge linux-image-$version_you_are_not_running
# show everything in /boot
# you should now see the files for only one kernel version, matching the version you're currently running
ls -a -l /boot
Then reboot the machine again.
You should remember to run "sudo apt autoremove" every once in awhile.
When you have three or more kernel images installed, it will auto-remove the oldest ones, leaving two versions on your machine: the currently running version, and the highest-versioned alternative that isn't currently running.
Basically, your /boot for is probably too full. Simple as.
