Skip to main content

/dev/vda1 getting filled up

thesmahesh
Dear All, I am having a vps with cpanel 11.5 installed on centos 7 machine df -h gives me this: Filesystem Size Used Avail Use% Mounted on /dev/mapper/cos-root 2.0T 58G 1.9T 3% / devtmpfs 15G 0 15G 0% /dev tmpfs 15G 666M 14G 5% /dev/shm tmpfs 15G 849M 14G 6% /run tmpfs 15G 0 15G 0% /sys/fs/cgroup /dev/vda1 243M 210M 21M 92% /boot But i frequently getting alert from cpanel stating that "The filesystem "/dev/vda1", which is mounted at "/boot", has reached "warn" status because it is 86.5% full" Please help me in getting this resolved. Thanks and Regards

Comments

7 comments

Date Votes
  • Jcats
    /boot stores your kernel images, you most likely have a lot of older kernel images in there that are no longer necessary What does this show:
    # ls -lah /boot/
    Can you also do:
    # uname -a
    0
  • thesmahesh
    Thanks for the reply. Please help
    root@server [~]# ls -lah /boot/ total 200M dr-xr-xr-x. 5 root root 3.0K Sep 25 15:34 ./ dr-xr-xr-x. 20 root root 4.0K Sep 24 06:10 ../ -rw-r--r-- 1 root root 121K Aug 6 03:15 config-3.10.0-229.11.1.el7.x86_64 -rw-r--r-- 1 root root 121K Sep 15 17:14 config-3.10.0-229.14.1.el7.x86_64 -rw-r--r-- 1 root root 121K Jun 24 00:15 config-3.10.0-229.7.2.el7.x86_64 -rw-r--r--. 1 root root 121K Mar 6 2015 config-3.10.0-229.el7.x86_64 drwxr-xr-x. 2 root root 1.0K Jul 15 10:03 grub/ drwxr-xr-x. 6 root root 1.0K Sep 25 15:34 grub2/ -rw-r--r--. 1 root root 39M Jul 15 09:55 initramfs-0-rescue-7d6225e3e2594f369d47e539de05d237.img -rw-r--r-- 1 root root 18M Aug 8 12:58 initramfs-3.10.0-229.11.1.el7.x86_64.img -rw-r--r-- 1 root root 18M Aug 8 14:32 initramfs-3.10.0-229.11.1.el7.x86_64kdump.img -rw-r--r-- 1 root root 18M Sep 25 15:34 initramfs-3.10.0-229.14.1.el7.x86_64.img -rw-r--r-- 1 root root 18M Jul 15 10:04 initramfs-3.10.0-229.7.2.el7.x86_64.img -rw-r--r-- 1 root root 18M Jul 15 11:03 initramfs-3.10.0-229.7.2.el7.x86_64kdump.img -rw-r--r--. 1 root root 18M Jul 15 09:55 initramfs-3.10.0-229.el7.x86_64.img -rw-r--r-- 1 root root 18M Jul 19 21:18 initramfs-3.10.0-229.el7.x86_64kdump.img -rw-r--r--. 1 root root 576K Jul 15 09:53 initrd-plymouth.img drwx------. 2 root root 12K Jul 15 09:51 lost+found/ -rw-r--r-- 1 root root 235K Aug 6 03:17 symvers-3.10.0-229.11.1.el7.x86_64.gz -rw-r--r-- 1 root root 235K Sep 15 17:16 symvers-3.10.0-229.14.1.el7.x86_64.gz -rw-r--r-- 1 root root 235K Jun 24 00:17 symvers-3.10.0-229.7.2.el7.x86_64.gz -rw-r--r--. 1 root root 235K Mar 6 2015 symvers-3.10.0-229.el7.x86_64.gz -rw------- 1 root root 2.8M Aug 6 03:15 System.map-3.10.0-229.11.1.el7.x86_64 -rw------- 1 root root 2.8M Sep 15 17:14 System.map-3.10.0-229.14.1.el7.x86_64 -rw------- 1 root root 2.8M Jun 24 00:15 System.map-3.10.0-229.7.2.el7.x86_64 -rw-------. 1 root root 2.8M Mar 6 2015 System.map-3.10.0-229.el7.x86_64 -rwxr-xr-x. 1 root root 4.8M Jul 15 09:55 vmlinuz-0-rescue-7d6225e3e2594f369d47e539de05d237* -rwxr-xr-x 1 root root 4.8M Aug 6 03:15 vmlinuz-3.10.0-229.11.1.el7.x86_64* -rw-r--r-- 1 root root 171 Aug 6 03:15 .vmlinuz-3.10.0-229.11.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 4.8M Sep 15 17:14 vmlinuz-3.10.0-229.14.1.el7.x86_64* -rw-r--r-- 1 root root 171 Sep 15 17:14 .vmlinuz-3.10.0-229.14.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 4.8M Jun 24 00:15 vmlinuz-3.10.0-229.7.2.el7.x86_64* -rw-r--r-- 1 root root 170 Jun 24 00:15 .vmlinuz-3.10.0-229.7.2.el7.x86_64.hmac -rwxr-xr-x. 1 root root 4.8M Mar 6 2015 vmlinuz-3.10.0-229.el7.x86_64* -rw-r--r--. 1 root root 166 Mar 6 2015 .vmlinuz-3.10.0-229.el7.x86_64.hmac

    "Uname -a" gives me this 3.10.0-229.11.1.el7.x86_64

    root@server [/]# rpm -qa |grep kernel kernel-3.10.0-229.7.2.el7.x86_64 kernel-tools-libs-3.10.0-229.14.1.el7.x86_64 kernel-3.10.0-229.14.1.el7.x86_64 kernel-devel-3.10.0-229.7.2.el7.x86_64 kernel-devel-3.10.0-229.11.1.el7.x86_64 kernel-tools-3.10.0-229.14.1.el7.x86_64 kernel-devel-3.10.0-229.14.1.el7.x86_64 kernel-3.10.0-229.el7.x86_64 kernel-3.10.0-229.11.1.el7.x86_64 kernel-devel-3.10.0-229.el7.x86_64 kernel-headers-3.10.0-229.14.1.el7.x86_64
    0
  • Jcats
    You are running 3.10.0-229.11.1 but you have 3.10.0-229.14.1 installed. I would boot into the newest kernel, then you can remove the older kernels Once you confirmed you are running the latest kernel, check
    # rpm -qa |grep kernel
    again, if you see any older ones, use
    rpm -e kernel-3.10.0-229.11.1.el7.x86_64
    as an example to remove the old ones. You can also remove any of the images in /boot that remain to clean it up. The only other way is to make that partition bigger or removing that partition so it uses the space on /
    0
  • thesmahesh
    Hello Jcats, Thanks again for replying. Sorry for the newbie question: "I would boot into the newest kernel, then you can remove the older kernels" Can you please let me know how to do that ? Thanks and Regards
    0
  • Jcats

    # cat /etc/grub.conf
    Make sure the latest kernel is at the top of the list. Then reboot, you will boot into the latest kernel, you can also hit any key while its rebooting during the splash screen(it shows a count down) but you would need console/kvm access to see it.
    0
  • thesmahesh

    root@server [/]# cat /etc/grub.conf cat: /etc/grub.conf: No such file or directory
    Please help. Thanks and Regards
    0
  • cPanelMichael
    Hello :) Typically, you can simply reboot the server to ensure it's using the latest kernel. Once you do this, the following thread explains how to safely remove the older kernels:
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post