[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Initramfs compression algorithm - was Re: /boot size and kernel updates



To reduce size of initramfs I change the compression setting in 

/etc/initramfs/initramfs.conf 

and set it to “xz”

After that one needs to rebuild initramfs.

Sent from my phone. Please forgive misspellings and weird “corrections”

> On 13 Nov 2022, at 16:35, David Christensen <dpchrist@holgerdanske.com> wrote:
> 
> On 11/13/22 01:41, Peter von Kaehne wrote:
>> I mostly let the installer do what it likes to do when installing Debian and this has worked out fine until the last couple installs on UEFI rather than legacy boot.
>> It now appears that the automatic installer does not get size of /boot right - even with only one new kernel update wanting to install itself it often fails with lack of space. One solution I found is to change the initramfs compression algorithm, which gives me space for two full kernels and initramfses. But this is still problematic. Are there other solutions other than reinstall with a larger boot partition?
>> For me the main problem are a couple of elderly relatives etc whose computers I administer mostly in a hands off fashion - with automatic security updates only and occasionally some more work during visits.
>> Now I am needing to look into sorting out remote access or simply disable all updates, neither of which is ideal for any variety of reasons.
>> Any clever suggestions which bring me back into a place where a few kernels can easily install without things getting too crowded?
>> Sent from my phone. Please forgive misspellings and weird “corrections”
> 
> 
> Please run the following commands as root and post the complete console session -- prompts, commands entered, and output displayed:
> 
> 2022-11-13 08:32:14 root@laalaa ~
> # cat /etc/debian_version ; uname -a
> 11.5
> Linux laalaa 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux
> 
> 2022-11-13 08:32:24 root@laalaa ~
> # ls -lF /boot
> total 109188
> -rw-r--r-- 1 root root       83 Sep  2 06:54 System.map-5.10.0-18-amd64
> -rw-r--r-- 1 root root       83 Oct 21 13:24 System.map-5.10.0-19-amd64
> -rw-r--r-- 1 root root   236286 Sep  2 06:54 config-5.10.0-18-amd64
> -rw-r--r-- 1 root root   236275 Oct 21 13:24 config-5.10.0-19-amd64
> drwxr-xr-x 5 root root     4096 Oct 29 13:48 grub/
> -rw-r--r-- 1 root root 48673909 Sep 24 17:33 initrd.img-5.10.0-18-amd64
> -rw-r--r-- 1 root root 48693403 Oct 29 13:19 initrd.img-5.10.0-19-amd64
> drwx------ 2 root root    16384 Jan  9  2022 lost+found/
> -rw-r--r-- 1 root root  6962016 Sep  2 06:54 vmlinuz-5.10.0-18-amd64
> -rw-r--r-- 1 root root  6963648 Oct 21 13:24 vmlinuz-5.10.0-19-amd64
> 
> 2022-11-13 08:32:50 root@laalaa ~
> # du -bc /boot
> 4379325    /boot/grub/locale
> 2010385    /boot/grub/i386-pc
> 2398204    /boot/grub/fonts
> 11195075    /boot/grub
> 16384    /boot/lost+found
> 122981258    /boot
> 122981258    total
> 
> 2022-11-13 08:33:20 root@laalaa ~
> # df /boot
> Filesystem     1M-blocks  Used Available Use% Mounted on
> /dev/sda1           920M  118M      739M  14% /boot
> 
> 
> David
> 


Reply to: