1

I keep having issues due to my boot drive running out of space. It fills up as soon as I try to sort out packages with apt-get upgrade, or if for any other reason dependencies try to be resolved or similar. And when I clear it out often I break something I'm working on. So as it has inevitably filled up again causing me issues I want to give it some more space.

GParted is showing my lvm partition as having only 44MiB of unused space. df shows I'm only using 33% of the total space. Is there any way I can re-organise this partition so that I can free up some space to give to /boot? If not, should I grab another drive and extend the boot partition?

enter image description here enter image description here

ll /boot

enter image description here

  • 3
    that boot partition isn't small - what's on it? in some distros you have to manually uninstall old kernels, if you don't do that, no size will ever be enough in the long run – frostschutz Oct 1 '18 at 16:44
  • Per @frostschutz comment/query, you probably need to clean up old kernel images or something similar. As for the LVM question, please update the question with details on the logical volumes on /dev/sda5. Output from df -hTP and lsblk is probably sufficient. – 0xSheepdog Oct 1 '18 at 16:45
  • @0xSheepdog I've ran the commands and added the screenshot of the results to the post – Shardj Oct 2 '18 at 10:01
  • @frostschutz lots of different vm bits and bobs, moving over to docker soon I hope. I added a screenshot to the post – Shardj Oct 2 '18 at 10:02
  • @Shard you don't keep "vm bits and bobs" on the hosts' /boot partition. That looks very much like old kernels to me, there's even still 4.4 kernels when you're already using 4.15 and you only need the very latest one (or two) of those. – frostschutz Oct 2 '18 at 10:29
0

Clearing boot (which I suspected would be the only suggestion) obviously didn't work for me as as soon as I try to do anything with my packages it generates a ton more stuff and fills it back up.

I suspect the reason I couldn't shrink sda5 was due to the partition table being mbr rather than gpt, resolving that may fix this for others. For me it seems something was majorly fucked up with my system so I bought a new ssd and I'm in the process of installing a new distro to that before transferring over my old files.

I won't mark this as an accepted answer, because it isn't an acceptable answer. But this may help someone so here you go.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.