[ubuntu] Ubuntu Server Disk Space Messed up

[FN-GM]

Hi,

 

We have a Ubuntu server we use for XIBO. I am not sure how this has happened but we appear to have run out of space in 1 partition and plenty of space in another.

 

How can I balance this back out please? Did I stuff something up during install?

 

Thanks

[MunkySpanner]

Looks fine to me. The /boot partition is like the hidden partition that Windows creates.

Here's what ours looks like

 

[FN-GM]

Hmm. It doesn't look like that on another server we have. We also can't install updates due to the lack of disk space.

[pete]

^ You have a whole bunch of kernel updates installed and /boot has filled. Uninstall all but the current kernel you're using and then retry updating.

 

 

uname -a will tell you the kernel you're currently using.

 

Then dpkg -l | grep linux-image to see how many kernel versions you have installed.

 

sudo aptitude remove linux-image-blah

 

to get rid of all but the kernel Linux is actually running on (found out above using uname -a) and any superseding it.

 

Example attached, but I only have one kernel installed on the box I used.

Edited December 9, 2015 by pete
attachment info not sanitised

[Geoff]

sudo apt-get autoremove

 

will clear out old kernels and initramfs from /boot

[FN-GM]

Well I did what @Geoff suggested as it looked easier. The server will not boot now. Good job I have a snapshot.

 

[FN-GM]

Restored the snapshot and ran it again seems ok this time. I am now able to install the updates.

 

Thanks folks.

[pete]

@Geoff

 

Does autoremove handle "I tried to install this kernel image but ran out of space so I've left it there unconfigured", well for you? I've had grief in the past.

 

Day-to-day it works fine for keeping /boot tidy but I've always chosen to clear a full /boot manually.

[Geoff]

That's not apt-get autoremoves fault. Doing an apt-get dist-upgrade would of tried to build the files in /boot at which failed due to lack of disk space. You would of got a warning about this at the time on the screen and in the log. You should also have you free disk space monitored in some fashion. Remember, Linux will burn your house down without warning if you tell it to. Linux assumes you know what you are doing at all times. That said...

 

update-initramfs -u

 

to unbreak the situation once you have some disk space back.

[FN-GM]

That's not apt-get autoremoves fault. Doing an apt-get dist-upgrade would of tried to build the files in /boot at which failed due to lack of disk space. You would of got a warning about this at the time on the screen and in the log. You should also have you free disk space monitored in some fashion. Remember, Linux will burn your house down without warning if you tell it to. Linux assumes you know what you are doing at all times. That said...

 

update-initramfs -u

 

to unbreak the situation once you have some disk space back.

 

Thanks

 

What does that command actually do please?

 

Thanks

[Geoff]

rebuilds the initramfs for the latest installed kernel (the initramfs was missing and caused the kernel panic in your screenshot).

[FN-GM]

Oh right i see.

 

Anyway got it sorted. Thanks very much for the assistance.