2

When upgrading via sudo do-release-upgrade, the installer said to have not enough space and suggested the sudo apt autoremove. (I am not sure, but it was probably about the /.) So, I did it:

Also, the administrator of the virtual image increased the size, and then growpart was used to use the space:

The growpart

After the growpart:

After growpart

I have repeated the sudo apt autoremove (just to be sure). When trying the do-release-upgrade again, I can observe:

The do-release-upgrade after adding space

I believe (based only on what I remember) that this time is reported the /boot instead of /. The suggested autoremove have not released more space.

The df -h shows:

The df -h

So, probably the /dev/sda1 size has to be increased. Is that correct?

Then... How can I increase the size of the /dev/sha1?

Update after the first comments: As possible alternative, I have another space allocated by the admin, and I could growpart the partion for the boot. Is there any way to move the other partitions to the end of the allocated disk to make space for extending the /dev/sda1?

pepr
  • 125

1 Answers1

2

With current /boot you can try: Use linux-purge to delete more kernels. Supposing your booted kernel works fine you could purge all other kernels: sudo linux-purge --keep=0 --clear-boot will save space. You could try with --simulate first to check what it is about to do (though it will ask you for confirmation without it before purging unless you use --yes). With --choose you get most control via interactive selection of kernels to remove.

Besides you could set gz compression for initramfs to save some space in /boot (though it is slower): related question

jarno
  • 6,175