PDA

View Full Version : Low disk Filesystem root at Upgrade - Help



ro7ca
May 7th, 2020, 02:59 PM
Hi,
I am new to Ubuntu, but I was able to have a dual boot (window + ubuntu) on X1 Carbon. Few days ago, I wanted to upgrade to the new OS - Fosa, but I couldn't complete the installation because of low disk space. I removed some unused files but I am still getting the error. Can anyone help me? Here is a screenshot

ActionParsnip
May 7th, 2020, 03:49 PM
If you start with:


sudo apt-get clean
sudo apt-get --purge autoremove
sudo dpkg -P `dpkg -l | grep ^rc | awk {'print $2'}`


Then you can remove old kernels. If you can give the output of:


uname -a; dpkg -l | grep linux-image


We can get old kernels pulled off the system and free up some space.

Impavidus
May 7th, 2020, 08:09 PM
Your root partition is almost full. It's 45GB and there's less than 1GB free space, which is not enough for temporary storage of all packages needed for the upgrade. Removing some old kernels and cache may help, but I don't expect it will clear that much space. The OS should only take about a third of that space, so most can be gained from cleaning up your documents or media files. Unless you suffer from overflowing log files. Can you investigate which files or directories take most space?

BTW, instead of posting a screenshot of your terminal, it's easier if you just copy-paste the output from the terminal to the forum. After all, it's just text. But don't forget to use code tags.

ro7ca
May 7th, 2020, 09:12 PM
Your root partition is almost full. It's 45GB and there's less than 1GB free space, which is not enough for temporary storage of all packages needed for the upgrade. Removing some old kernels and cache may help, but I don't expect it will clear that much space. The OS should only take about a third of that space, so most can be gained from cleaning up your documents or media files. Unless you suffer from overflowing log files. Can you investigate which files or directories take most space?

BTW, instead of posting a screenshot of your terminal, it's easier if you just copy-paste the output from the terminal to the forum. After all, it's just text. But don't forget to use code tags.

Thank you; I will remove some files and then follow the steps above to see if that helps. Is it possible to maybe re-partition again?

ro7ca
May 7th, 2020, 09:30 PM
Linux youssoufj-ThinkPad-X1-Carbon-6th 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 amd64 Signed kernel image generic
ii linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 amd64 Signed kernel image generic
ii linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1 amd64 Signed kernel image generic
ii linux-image-generic-hwe-18.04 5.3.0.46.102 amd64 Generic Linux kernel image



Hi, thank you for your help; Here is above the output

ro7ca
May 7th, 2020, 09:31 PM
If you start with:


sudo apt-get clean
sudo apt-get --purge autoremove
sudo dpkg -P `dpkg -l | grep ^rc | awk {'print $2'}`


Then you can remove old kernels. If you can give the output of:


uname -a; dpkg -l | grep linux-image


We can get old kernels pulled off the system and free up some space.

Here it is; thank you



Linux youssoufj-ThinkPad-X1-Carbon-6th 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 amd64 Signed kernel image generic
ii linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 amd64 Signed kernel image generic
ii linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1 amd64 Signed kernel image generic
ii linux-image-generic-hwe-18.04 5.3.0.46.102 amd64 Generic Linux kernel image

ActionParsnip
May 8th, 2020, 10:10 AM
sudo apt-get --purge remove linux-image-5.0.0-36-generic linux-image-5.0.0-40-generic
sudo apt-get --purge autoremove

Holger_Gehrke
May 8th, 2020, 10:47 AM
Another thing that should free up a GB or two is to remove the older revisions of snap packages that are kept as backups in case a new version of a package does not work as intended. Do 'snap list -all' to get a list of all installed snaps including the older revisions. In that list the old files should have a note in the last column calling them 'deactivated' or 'inactive' or something to that effect. You can remove those by running 'snap remove --revision n x' (x being the name of the package and n the revision number of a deactivated version from the list).

Going through your screenshot I find that these are redundant and can be removed. There might be more ...



Package

Revision



gnome-logs
81


krita
54



gnome-calculator
544


pycharm-community
188


skype
118


eclipse
40


core
8935


core18
1668


gnome-3-28-1804
110


gnome-system-monitor
127


gnome-characters
399


gtk-common-themes
1474



Holger