On Sun, 2020-05-10 at 15:50 +0200, Rainer Dorsch wrote: > Thanks Raymond for your quick and accurate answer. Fortunately, I am in a > much > better position than what you describe in your blog entry, I had kernel n-1 > and n installed, when trying to install n+1. > > I removed my oldest kernel version (n-1) which resolved the issue. I shold > have created a larger /boot partition in the first place. > > Interesting enough there was a initrd.img-4.19.0-9-amd64 created already > before and also booting the -9 kernel worked well.
Most likely the upgrade process resulted in two initramfs rebuilds.
This ideally shouldn't happen, but currently it sometimes does.
> After removing the n-1
> kernel, the initrd for n+1 grew by around 300 bytes. Since df reported that
> more than 22 MB are free, I do not undertand why update-initramfs complained
> that it has not enough space.
[...]
update-initramfs will never delete an old initramfs before building a
replacement. So, there has to be space for an extra initramfs image.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
signature.asc
Description: This is a digitally signed message part
