Re: Updating kernels impossible when /boot is getting full

[David Christensen <dpchrist@holgerdanske.com>]

On 8/2/21 11:29 AM, Greg Wooledge wrote:
> On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote:

> > Please post your console session showing how you created
> > initrd.img-5.10.0-8-amd64.txt.gz.
>
> I didn't.  It was created automatically when I installed dracut-core.
>
> Prior to that, it was created automatically every time I did anything
> with apt-get which touched the "low level stuff" (kernel, firmware,
> microcode, busybox, other tools that live in the initrd, and so on).


I'd rather not install dracut.


The source for lsinitrd.sh is available on github:

https://github.com/dracutdevs/dracut/blob/master/lsinitrd.sh


The cpio(1) listing incantation appears on line 177.  Reworking my 
previous command:

$ gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio --extract --verbose 
--list | sort -k9 | gzip -9 > initrd.img-4.19.0-17-amd64.txt.gz
246741 blocks


Please see initrd.img-4.19.0-17-amd64.txt.gz, attached.


If the OP would care to run the above command and post the result, 
perhaps we can see what is bloating their initrd.img.


David

Attachment: initrd.img-4.19.0-17-amd64.txt.gz
Description: application/gzip