CentOS64 Error After yum update

L

lungkao

Verified User
Joined
Jun 4, 2008
Messages
35
CentOS64 Error After yum update

Error Summary
-------------
Disk Requirements:
At least 54MB needed on the /boot filesystem.

How to fix it
 
Format and reinstall?

What is the output of the command:

df -h
 
am use open vz
Code: 
[root@vps ~]# du -sh /boot/*
67K	/boot/config-2.6.18-92.1.18.el5.028stab060.2xen
63K	/boot/config-2.6.18-92.1.22.el5
63K	/boot/config-2.6.18-92.el5
210K	/boot/grub
2.5M	/boot/initrd-2.6.18-92.1.18.el5.028stab060.2xen.img
2.5M	/boot/initrd-2.6.18-92.1.22.el5.img
2.5M	/boot/initrd-2.6.18-92.el5.img
12K	/boot/lost+found
81K	/boot/message
110K	/boot/symvers-2.6.18-92.1.18.el5.028stab060.2xen.gz
93K	/boot/symvers-2.6.18-92.1.22.el5.gz
93K	/boot/symvers-2.6.18-92.el5.gz
1.2M	/boot/System.map-2.6.18-92.1.18.el5.028stab060.2xen
1.2M	/boot/System.map-2.6.18-92.1.22.el5
1.2M	/boot/System.map-2.6.18-92.el5
57M	/boot/vmlinux-2.6.18-92.1.18.el5.028stab060.2xen
1.9M	/boot/vmlinuz-2.6.18-92.1.18.el5.028stab060.2xen
1.8M	/boot/vmlinuz-2.6.18-92.1.22.el5
1.8M	/boot/vmlinuz-2.6.18-92.el5
357K	/boot/xen.gz-2.6.18-92.1.18.el5.028stab060.2
826K	/boot/xen-syms-2.6.18-92.1.18.el5.028stab060.2

Code: 
[root@vps ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3             436G  5.1G  409G   2% /
/dev/sdc1             452G   43G  386G  10% /hdd2
/dev/sdb1             452G   24G  405G   6% /hdd1
/dev/sda1              99M   80M   14M  86% /boot
tmpfs                 3.9G     0  3.9G   0% /dev/shm
 
Last edited:
Do as jeff says and delete the old kernels you are not using.
 
I don't think anyone is going to take resonsibility for telling you in a forum which kernels are safe to delete. Or even if you should be updating kernels or saving new or old kernels, instead of allowing your VPS vendor to update your kernel.

If you can't or won't figure it out yourself, then you should contact your VPS vendor to see if they can support you; this is an OS issue; it has nothing to do with DirectAdmin.

If your VPS vendor won't help you, then you could always do an admin/reseller backup, delete your VPS and recreate it (if your vendor allows you to do that) and then restore the backup, but I don't think any of us are going to take the responsibility for giving you details on that either.

Worst case option; hire a third party support company to take care of it for you (there are a few of us on these forums).

Jeff
 
You must log in or register to reply here.
Back
Top