[SOLVED] Ubuntu boot disk nearly full. How do I prune
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use Ubuntu (14.16 light?) and at start up I get a message that there is only 2.9MB free space on boot disk. When I press the examine key no details appear. How do I get access and prune?
You could run df -h from a terminal. It will show the size, amount used and amount available of mounted partitions. Do you have a separate boot partition or is it all on the / partition? With a separate boot partition you could use the option explained in the first post at the link below. If the / filesystem is close to full, you need to move some data.
Firstly, do you have any idea what content is taking up space? Meaning do you save a lot of files, documents, large things like movies? Or do you just use your system, save nothing more major than written documents, and thus have no starting clues on this subject?
Command line, a.k.a. Terminal? Or Desktop GUI? For instance on the command line there are commands such as the df which was raised by yancek, on the UI you can view your file folders and get properties. You should also right mouse to get a general menu and enable viewing of hidden files and folders. The initial things people are going to try and assist you with are to ascertain the total disk size you have, and whether or not disk usage is system files and applications or personal files which are pure data that you can consider backing up somewhere else.
the files system looks like this
Filesystem Size Used Avail Use Mounted on
/dev/mapper/ubuntu--vg-root 913G 13G 854G 2 /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.7G 4.0K 1.7G 1% /dev
tmpfs 334M 1.3M 333M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.7G 288K 1.7G 1% /run/shm
none 100M 28K 100M 1% /run/user
/dev/sda2 237M 222M 2.8M 99% /boot
/dev/sda1 511M 3.4M 508M 1% /boot/efi
presumably the message refers to /dev/sda2 ???
Whatever that is! Does this shed any light on the problem.
Thanks for the replies so far.
Mike
So what that says is that you are only using 2% of your disk. You're reading it incorrectly.
For your root file system that is. The boot partition is largely full, but that should not matter, it should be solely to contain the boot information which will not change. Root is "/", the first one. 854G available. And that is likely where your /home/[your username] directory is located.
No problem. Just realizing though that the whole reason you raised the question was because your system was complaining. Yes, there's 2.8'ish Meg left on the /boot partition. That really should not be a problem. I do wonder why it complains. It should not even be mounting /boot except to start up.
If you run a "mount" command, just that word from the terminal, does it show that /dev/sda2 is mounted anywhere? If mounted, at the very least it should be read-only "ro". Once again I do wonder why the system is complaining...
It may cause a problem the next time he updates his kernel. If it tries to keep the older ones or if the new one is a few MB bigger than the one it removes, it'll cause trouble.
Ubuntu doesn't or doesn't always remove old kernels and people who have a separate boot partition often see this problem and have to manually remove older kernels. Lots of posts about this problem at the various Ubuntu forums. Posting the link I forgot in my earlier post.
You might want to bookmark that page or make a note of the command(s) as it is likely to happen again if you are doing regular updates of kernels. In some cases, a separate boot partition is useful or necessary but for the average user, it's not anymore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.