Hello,

I've received the Drive Space Warning message and in WHM --> Service Status I see the yellow warning lamp on Disk hda1 (/boot) DMA+ 82 %
What I have to do? It's first time it happens.

It look like this

Filesystem Type Size Used Avail Use% Mounted on
/dev/hda2 ext3 71G 5.2G 62G 8% /
/dev/hda1 ext3 99M 77M 18M 82% /boot
none tmpfs 250M 0 250M 0% /dev/shm


Thank you
1001

It looks like you have extra stuffs in your /boot directory. You might need to review its contents and see if anything can be deleted or moved to a different location. Try the following and post the results:

du -s /boot/*

It will show the size of all items in your /boot directory.

Hello,

I tried it did the following:

49 /boot/config-2.4.21-15.0.2.EL
49 /boot/config-2.4.21-15.0.2.ELsmp
49 /boot/config-2.4.21-15.0.3.EL
49 /boot/config-2.4.21-15.0.3.ELsmp
49 /boot/config-2.4.21-15.0.4.EL
49 /boot/config-2.4.21-15.0.4.ELsmp
49 /boot/config-2.4.21-15.EL
49 /boot/config-2.4.21-15.ELsmp
48 /boot/config-2.4.21-4.EL
49 /boot/config-2.4.21-4.ELsmp
48 /boot/config-2.4.21-9.0.1.EL
49 /boot/config-2.4.21-9.0.1.ELsmp
48 /boot/config-2.4.21-9.0.3.EL
49 /boot/config-2.4.21-9.0.3.ELsmp
188 /boot/grub
248 /boot/initrd-2.4.21-15.0.2.EL.img
251 /boot/initrd-2.4.21-15.0.2.ELsmp.img
250 /boot/initrd-2.4.21-15.0.3.EL.img
251 /boot/initrd-2.4.21-15.0.3.ELsmp.img
249 /boot/initrd-2.4.21-15.0.4.EL.img
252 /boot/initrd-2.4.21-15.0.4.ELsmp.img
245 /boot/initrd-2.4.21-15.EL.img
251 /boot/initrd-2.4.21-15.ELsmp.img
241 /boot/initrd-2.4.21-4.EL.img
246 /boot/initrd-2.4.21-4.ELsmp.img
247 /boot/initrd-2.4.21-9.0.1.EL.img
248 /boot/initrd-2.4.21-9.0.1.ELsmp.img
240 /boot/initrd-2.4.21-9.0.3.EL.img
247 /boot/initrd-2.4.21-9.0.3.ELsmp.img
1 /boot/kernel.h
1 /boot/lost+found
24 /boot/message
22 /boot/message.ja
0 /boot/quota.user
0 /boot/System.map
564 /boot/System.map-2.4.21-15.0.2.EL
590 /boot/System.map-2.4.21-15.0.2.ELsmp
564 /boot/System.map-2.4.21-15.0.3.EL
590 /boot/System.map-2.4.21-15.0.3.ELsmp
564 /boot/System.map-2.4.21-15.0.4.EL
590 /boot/System.map-2.4.21-15.0.4.ELsmp
564 /boot/System.map-2.4.21-15.EL
590 /boot/System.map-2.4.21-15.ELsmp
562 /boot/System.map-2.4.21-4.EL
589 /boot/System.map-2.4.21-4.ELsmp
563 /boot/System.map-2.4.21-9.0.1.EL
589 /boot/System.map-2.4.21-9.0.1.ELsmp
563 /boot/System.map-2.4.21-9.0.3.EL
589 /boot/System.map-2.4.21-9.0.3.ELsmp
2829 /boot/vmlinux-2.4.21-15.0.2.EL
3432 /boot/vmlinux-2.4.21-15.0.2.ELsmp
2829 /boot/vmlinux-2.4.21-15.0.3.EL
3432 /boot/vmlinux-2.4.21-15.0.3.ELsmp
2829 /boot/vmlinux-2.4.21-15.0.4.EL
3436 /boot/vmlinux-2.4.21-15.0.4.ELsmp
2829 /boot/vmlinux-2.4.21-15.EL
3432 /boot/vmlinux-2.4.21-15.ELsmp
2846 /boot/vmlinux-2.4.21-4.EL
3452 /boot/vmlinux-2.4.21-4.ELsmp
2850 /boot/vmlinux-2.4.21-9.0.1.EL
3452 /boot/vmlinux-2.4.21-9.0.1.ELsmp
2825 /boot/vmlinux-2.4.21-9.0.3.EL
3424 /boot/vmlinux-2.4.21-9.0.3.ELsmp
1219 /boot/vmlinuz-2.4.21-15.0.2.EL
1319 /boot/vmlinuz-2.4.21-15.0.2.ELsmp
1219 /boot/vmlinuz-2.4.21-15.0.3.EL
1318 /boot/vmlinuz-2.4.21-15.0.3.ELsmp
1218 /boot/vmlinuz-2.4.21-15.0.4.EL
1319 /boot/vmlinuz-2.4.21-15.0.4.ELsmp
1219 /boot/vmlinuz-2.4.21-15.EL
1318 /boot/vmlinuz-2.4.21-15.ELsmp
1214 /boot/vmlinuz-2.4.21-4.EL
1316 /boot/vmlinuz-2.4.21-4.ELsmp
1218 /boot/vmlinuz-2.4.21-9.0.1.EL
1316 /boot/vmlinuz-2.4.21-9.0.1.ELsmp
1216 /boot/vmlinuz-2.4.21-9.0.3.EL
1315 /boot/vmlinuz-2.4.21-9.0.3.ELsmp

It seems that
this is full /dev/hda1 ext3 99M 77M 18M 82% /boot
and this is empty /dev/hda2 ext3 71G 5.2G 62G 8% /
correct?
How can I do?

Thank you
1001

You have way too many kernel boot images in /boot. 17 is too much!! Unless you need them all, it may be a good idea to move most of them elsewhere, and leave only one or two images in /boot (those that you need). If you don't know which is needed in your case, it is probably best to open a ticket in Orbit, describe the problem and ask support to move the unneeded files to another location.

In any case, if you didn't put them there, it is likely that SM support put them there when they setup or fix-up the server. So they should know what is going on and how to fix it, one would hope .

I'm surprised the boot partition isn't larger by default. I've always kinda wondered why its so small. Afterall, that's not even enough to fill a Zip disk. I'd expect 250mb boot might work a little better on default installs especially with all the kernal updates and other things that could potentially fill this up.

Hello again,

I finally tried to open a ticket... Orbit said... delete old kernel
then I found this post

http://forums.servermatrix.com/viewtopic.p...=kernel+up2date

follow the steps and now it seems works fine.
Now the boot is 5%



Thank you again for help

Bye

For a typical server setup, there is no need for a large /boot partition, just enough to store a few boot images. Mine has four bootable images, and it consumes less than 25 MB. So a large partition would be a waste anyway. If there is ever a need for more, I would keep the extras somewhere else. Of course, other people's usage may be different depending on their actual needs.

FWIW, the /boot partition is not even necessary. It is only a convenience for those who want to play around with the boot process and experimenting with different kernel images on different devices/partitions.