• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Root clearing

T

TonyTTL

Guest
Im a newbie - so please bear with me:

My boot partition /hda1 is now @100%
This is causing mysql errors (as it does) and I want to clear some space.

What files should I clear/delete &
How can I move them?

Can I use root access thru WinScp and 'drag' them to a new folder off the partition? - and if so where is the best place to resite the files?
 
Run these commands:

uname -a
ll /boot
rpm -q kernel kernel-smp
cat /etc/grub.conf /etc/lilo.conf

and send the output. You probably recently upgraded your kernel and hit your partition's limit, you may need to remove an older kernel (using rpm -e, not rm!) to free up space. I typically only have 2~3 kernels available, previous, current and new. Once I reboot to new I blow away the oldest kernel.
 
Thank you for your response to my FIRST ever Post !
/$ uname -a
Linux s152058xx.linehome-server.info 2.6.14-051115a #1 SMP Tue Nov 15 13:06:41 CET 2005 i686 i686 i386 GNU/Linux
/$ ll /boot
-bash: line 39: ll: command not found
/$ rpm -q kernel kernel-smp
kernel-2.6.10-1.771_FC2
kernel-smp-2.6.10-1.771_FC2
/$ cat /etc/grub.conf /etc/lilo.conf
cat: /etc/grub.conf: No such file or directory
boot=/dev/hda
root=/dev/hda1
install=/boot/boot.b
vga=normal
timeout=60
prompt
lba32
read-only
default=lx
append="console=tty0 panic=30"
image=/boot/vmlinuz
label=lx
image=/boot/vmlinuz.old
label=lx.old

GREEK to me. !!
Translate / Action plan ????
 
Looks like you have a completely custom kernel built there (2.6.14). You should be able to "rpm -e kernel-2.6.10-1.771_FC2" and "rpm -e kernel-smp-2.6.10-1.771_FC2" without any harm.

I guess ll didn't work, it is a habit of mine (alias)...

ls -l /boot

would show what it is in the boot directory. Is your server with 1&1, by chance? It looks like their work, and if that is the case you probably have a 500MB root partition.
 
Thanks for your response. You seem to know Ur way about ;)
Right on all counts. Im pretty sure I can work with (without repartitioning) the 500MB boot partition that 1&1 uk provided if I keep it trim.
So heres the layout:
/$ ls -l /boot
total 7684
-rw-r--r-- 1 root root 736955 Mar 28 2005 System.map-2.6.10-1.771_FC2
-rw-r--r-- 1 root root 764264 Mar 28 2005 System.map-2.6.10-1.771_FC2smp
-rw-r--r-- 1 root root 768240 Nov 15 12:09 System.map-2.6.14-051115a
-rw-r--r-- 1 root root 512 Oct 9 2004 boot.0300
-rw-r--r-- 1 root root 5824 Mar 12 2004 boot.b
-rw-r--r-- 1 root root 612 Mar 12 2004 chain.b
-rw-r--r-- 1 root root 54511 Mar 28 2005 config-2.6.10-1.771_FC2
-rw-r--r-- 1 root root 54311 Mar 28 2005 config-2.6.10-1.771_FC2smp
-rw-r--r-- 1 root root 28268 Nov 15 12:02 config-2.6.14-051115a
-rw-r--r-- 1 root root 205892 Oct 12 02:43 initrd-2.6.10-1.771_FC2.img
-rw-r--r-- 1 root root 195940 Oct 12 02:44 initrd-2.6.10-1.771_FC2smp.img
-rw-r--r-- 1 root root 111682 Nov 17 11:45 initrd-2.6.14-051115a
drwx------ 2 root root 49152 Mar 14 21:02 lost+found
-rw------- 1 root root 38400 Mar 14 21:02 map
-rw-r--r-- 1 root root 640 Mar 12 2004 os2_d.b
lrwxrwxrwx 1 root root 28 Mar 14 21:01 vmlinuz -> /boot/vmlinuz-2.6.14-051115a
-rw-r--r-- 1 root root 1471499 Mar 28 2005 vmlinuz-2.6.10-1.771_FC2
-rw-r--r-- 1 root root 1411870 Mar 28 2005 vmlinuz-2.6.10-1.771_FC2smp
-rw-r--r-- 1 root root 1887364 Nov 15 12:09 vmlinuz-2.6.14-051115a
lrwxrwxrwx 1 root root 30 Mar 14 21:01 vmlinuz.old -> /boot/vmlinuz-2.6.10-1.771_FC2

So whats eating up the space?
 
It is definately the extra kernels, the 500MB partition can only hold about 3 or 4 kernels. Typically it isn't the kernel but the modules (/lib/modules/) that come with the kernel that eat up the space. They are about 60MB per kernel installation. I would use rpm to erase the 2.6.10 kernels, since you have a custom built 2.6.14 kernel.


This command can tell you on the root partition (/) what are the top 15 largest directories (or subdirectories).

du -kx --max-depth=3 / |sort -n -r |head -15

Here is what mine looks like...

201064 /
144944 /lib
125980 /lib/modules
74264 /lib/modules/2.6.10-2.3.legacy_FC2smp
48212 /lib/modules/2.6.10-1.771_FC2smp
30284 /etc
21872 /etc/security
21776 /etc/security/selinux
11808 /sbin
8160 /boot
5008 /bin
3500 /lib/modules/2.6.9-041221
2752 /lib/kbd
2700 /lib/tls
1760 /lib/i686

I have three kernels installed, 2.6.9 (which 1&1 built), my current and the new one.
 
Fantastic:
You have single-handedly fixed several (various) errors that were caused by a lack of space on hda1 (boot).
First of all thank you !

There were some dependencies that prevented removal of


/$ rpm -e kernel-smp-2.6.10-1.771_FC2
error: Failed dependencies:
kernel >= 2.6.4-1.300 is needed by (installed) policy-1.11.3-3
kernel >= 2.4.10 is needed by (installed) prelink-0.3.2-1
kernel >= 2.4.20 is needed by (installed) iptables-1.2.9-2.3.1
kernel >= 2.2 is needed by (installed) pciutils-2.1.99.test3-1.1
kernel >= 2.4 is needed by (installed) quota-3.10-2
kernel >= 2.4.14 is needed by (installed) vconfig-1.8-2
kernel >= 2.2.0 is needed by (installed) libpcap-0.8.3-6.FC2.1
kernel >= 2.2.0 is needed by (installed) tcpdump-3.8.2-6.FC2.1
kernel >= 2.4 is needed by (installed) bind-9.2.3-13
but that still made enough room to be getting on and learning what to do. :) Ta ;)
 
Yeah, those dependencies are bogus because your 2.6.14 kernel is not registered in the package manager (rpm). Unfortunately the only thing you can do is --nodeps removal using "rpm -e kernel-smp-2.6.10-1.771_FC2 --nodeps".
 
Done and dusted. Another successful operation carried out under your direction. Theres a long way to go yet but I appreciate the time a & effort U afforded me. Ta
 
Back
Top