Just ran in to this on Ubuntu 20.04, with an encrypted root partition. The
partition layout is the one automatically generated when you install and ask
for root partition encryption - I didn't mess with it.
Drive is 512Gb NVME
Machine is a Lenovo Thinkbook 15
Kernel 5.8.0-59-generic
The /boot
This was a fresh install of 20.04. I enabled encryption as it's a work laptop.
I don't think I have logs - just the failure due to /boot being full on the
update UI.
I then followed the instructions at
https://help.ubuntu.com/community/RemoveOldKernels under "Safely remove old
kernels" so I
I've not yet found a way to make a USB boot that would allow me to start
the machine in the event of something going wrong. Without a plan to
revert the change, I'm a bit nervous. I know it *should* work fine - but
I don't want to suddenly have an unbootable laptop I can't rescue.
--
You
Thanks for that advice.
I'm a bit in trepidation about removing the default HWE. How do I protect
myself from having an unbootable system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
And then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space?field.comment=And
then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space.
Now /boot contains:
# du -sh /boot/*
248K
Here is the result of linux-purge --info
My /boot is like this:
# du -sh /boot/*
248K/boot/config-5.10.0-1038-oem
248K/boot/config-5.10.0-1044-oem
248K/boot/config-5.11.0-25-generic
248K/boot/config-5.11.0-27-generic
244K/boot/config-5.8.0-63-generic
48M /boot/efi
8.0M
Ok, did it.
That's freed up a load of space.
Where would I file the bug about having two sets of kernels?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Sorry I was not clear enough.
When I said "Filled with" I meant that they were the files occupying space. I'm
sorry if that gave the idea that the corresponding vmlinuz-* files weren't
present - it was just that in terms of bytes occupied, the initrd files are the
big ones.
As you can see from
I managed to get some free space back on /boot.
I'm posting this in the hopes that what I did may inform any fixing process.
1) List kernels with `dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'`
2) Delete the oldest initrd with update-initramfs -d -k 5.8.0-59-generic. There
was now 111Mb
Ok, more information. Just got warned that /boot is full again.
I have attached a directory listing for /boot.
Where do I find the logs for the update process that's doing this?
** Attachment added: "Directory listing for /boot"
I have now run linux-purge. It only freed up 50Mb or so, and no kernels
got removed
** Attachment added: "Directory listing for /boot"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5512828/+files/slash-boot-contents-post-linux-purge.txt
--
You received
11 matches
Mail list logo
