Re: Enlarging /boot
On Mon 03 Aug 2020 at 08:38:55 (+0200), Erwan David wrote:
> Le 02/08/2020 à 23:48, Leslie Rhorer a écrit :
> > On 8/2/2020 3:32 PM, Erwan David wrote:
> >> I used the buster installer about 1 year ago,with a fully encrypted
> >> disk, thus
> >>
> >> a /boot/efi partition, a /boot partition then an encrypted lvm.
> >>
> >> /boot is now not large enough to even have 2 kernels on it,
> >> initramfs-tools cannot create the images.
> >>
> >> I see this
> >> /dev/nvme0n1p2 237M 92M 133M 41% /boot
> >> /dev/nvme0n1p1 511M 5.3M 506M 2% /boot/efi
> >>
> >> Is it possible to reduce /boot/efi and have some more room for /boot, or
> >> should I reinstall the computer ?
> >
> > Um, the kernel is only about 5M in size. With 133M free, there
> > should be plenty of room for multiple kernels. The initrd image is
> > usually under 40M, so there should be room for the entire boot image to
> > be duplicated. Note the current use is only 41%. You shouldn't need
> > more space, per se, except that normally the initrd is temporarily
> > uncompressed while it is being created. I think you could get around
> > this by employing chroot.
>
> My initrd is 69 M...
In the absence of # du -sh /boot/*/ ; ls -l /boot/
that's a help. So you likely have one of System.map, config,
initrd.img and vmlinuz in /boot.
As long as you have other means of booting the system, you could try
copying initrd.img to a backup, and rebuilding it with MODULES=dep
in /etc/initramfs-tools/initramfs.conf, and see how much space that
would save. If you can still boot successfully with the dep version,
then you might have room now to install a second kernel, even with
MODULES=most restored.
It does make future upgrades a little more tedious.
Cheers,
David.
Reply to: