/boot partition full

[Labomba]

hello Folks,

Last week there was a Kernel update for Zentyal 3.0.21, but unable to install this one.
I noticed that the /boot partition is used for 100%, so I have have to remove some kernels but it keeps telling me about dependencies linked to the used kernel.
Can somebody tell me how to remove these older kernel versions and create some free space?

Thnx in advance!

[christian]

Removing kernel, I can't really help. 

Regarding disk space, I doubt removing kernels will solve your issue at least on long term.
Tell us a bit more about your storage topology.
- Is everything installed on one single disk, including /var ?
- if you disk(s) is already full, there is no option aside clean-up  but if space is used because of applications and components, clean-up will never be efficient enough.

Thus I suggest you look first at log files.
What's the result of:

Code: [Select]

sudo find /var -name *.gz | wc -l
This will tell you how many log files are there, as a very high level first step

[Labomba]

Hard drives:
Filesystem                Size  Used Avail Use% Mounted on
/dev/mapper/INETSRV-root  736G   24G  675G   4% /
udev                       4.9G  4.0K  4.9G   1% /dev
tmpfs                      2.0G  392K  2.0G   1% /run
none                        50M     0   50M   0% /run/lock
none                       4.9G     0  4.9G   0% /run/shm
/dev/cciss/c0d0p1         228M  228M     0 100% /boot
result of root@INETSRV:~# find /var -name *.gz | wc -l
377

There are older kernels in the /boot, can't they be removed?

[christian]

logs in /var/ do not really matter as /boot is on another disk.

Just curious, is this server installed using Zentyal installation ? partitioning is very different from a "standard" one.
What's the reason for having /boot on so small dedicated partition ?

[robb]

This looks like a manual install with softraid (mdadm)
But still I am puzzled why /boot is chosen on a separate disk and why so small?

[Gilberto Ferreira]

Hi

Try remove old kernels...


Cheers

[christian]

Try remove old kernels...

In case you didn't notice, his question is exactly this one 

noticed that the /boot partition is used for 100%, so I have have to remove some kernels but it keeps telling me about dependencies linked to the used kernel.

I suppose as a warning when running

Code: [Select]

sudo apt-get purge linux-image-x.x.x-x-server
If you can help with this, you're very welcome 

@Labomba:
what's the result of

Code: [Select]

uname -rand

Code: [Select]

dpkg --list | grep linux-image

[UdoB]

This looks like a manual install with softraid (mdadm)
But still I am puzzled why /boot is chosen on a separate disk and why so small?

As a sidenote: I've set up several systems with LVM2 on a Raid1/Mirror. It is not very long ago that Grub2/Grub/Lilo was not able to boot from a logical volume. The usual workaround was to prepare a small /boot Partition either standalone or a small, second Raid1for this purpose... 

[UdoB]

I suppose as a warning when running

Code: [Select]

sudo apt-get purge linux-image-x.x.x-x-server
If you can help with this, you're very welcome 

When apt-get fails removing packages I fall back do dpkg: sudo dpkg -P  linux-image-x.x.x-x-server

[robb]

As a sidenote: I've set up several systems with LVM2 on a Raid1/Mirror. It is not very long ago that Grub2/Grub/Lilo was not able to boot from a logical volume. The usual workaround was to prepare a small /boot Partition either standalone or a small, second Raid1for this purpose...

Then still the question: why such a small partition. Only 280MB.... 

[UdoB]

Then still the question: why such a small partition. Only 280MB.... 

*grin* - for me this looks oversized, probably because I am getting old . My current Ubuntu workstation has three Kernels installed. All three together do occupy 79 MB. So why should one want to waste more space for a dedicated /boot-Partition? (If you have a reason to have one in the first place.) 

Being off-topic here I hope my hint regarding "dpkg" helps Labomba...

[jase]

good evening
I don't wish to hijack Lambomba's thread, what is the etiquete here as I've got exactly the same issue and have been meaning to investigate further then saw this thread today?

robb: I also only have a 228mb boot partition, suspect this is a default or we both chose poorly
Filesystem                Size  Used Avail Use% Mounted on
/dev/mapper/zentyal-root  456G  6.4G  426G   2% /
udev                      1.4G  8.0K  1.4G   1% /dev
tmpfs                     577M  340K  577M   1% /run
none                       50M     0   50M   0% /run/lock
none                      1.5G  4.0K  1.5G   1% /run/shm
/dev/sda1                 228M  224M     0 100% /boot

christian:
I have 261 log files is this a high value?

this is just a test machine, I was going to duplicayte the disk then experiment with resizing tools, any advice appreciated.
thanks
jase

[christian]

If you boot with Ubuntu LiveCD, I don't wee yet why you could not resize

[EddieA]

Then still the question: why such a small partition. Only 280MB.... 

2 or 3 people have asked this question.

The answer is, that's what Zentyal allocates if you tell it to use the whole disk and let Zentyal do the allocations.   

But I'm also with UdoB here.  My 240M /boot partition is less than half full with 4 kernel images.

Also a quick Google with "ubuntu remove old kernel" will tell you all about "apt-get purge" to clean up.  Just remember to leave the latest 2 images intact.

***Update***
After a quick "sudo dpkg --get-selections | grep image" followed by 2 x "sudo apt-get purge linux-image-3.5.0-<nn>-generic" commands, my boot is now only a quarter full.

Cheers.

[christian]

Do you mean that if you let Zentyal using the whole disk, it will create dedicated /boot partition?

I'm surprised I don't have any on my 2.2 machine (but I built this one manually if I'm not wrong) neither on my 3.0 -> 3.1 mahine and this one was deployed, as far as I remember, using "default" Zentyal installation.

Anyway, yes storing only 2 kernels is very tight, especially if there is no process performing automatic clean-up when kernel is not used anymore. It's like for log files: there is a process to rotate logs, so far so good but none to clean-up old archives