/boot is 100% full (corrupted ?)
Hi Linux gurrus :-)
hope you all will be doing well. Well I am facing a problem first time in my sys admin experience. I am using RHEL-4, I am unable to access /boot partition. when i try to access this partion or want to show its contents, It seems /boot is corrupted. see the following outputs #ls /boot/ 9?^?????tdÜ°??????4?çj? #df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 145G 98G 40G 72% / /dev/sda1 1.4T 1.4T 0 100% /boot none 501M 0 501M 0% /dev/shm Note: its showing the wrong entries /dev/sda1 (1.4T) and its 100% full. #fdisk -l Disk /dev/sda: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 9726 78019672+ 8e Linux LVM Disk /dev/sdb: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 9726 78124063+ 8e Linux LVM Can any body help me whats wrong with /boot? Number of applications are being run (24x7) on this server. I cant reboot it and cant interrupt the running applications. Can any body tell me what should i do now? Server's info: #cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 5) # uname -r 2.6.9-11.ELsmp waiting for an early response. Thanks Sohail |
Remove old and unwanted kernel updates carefully, this will free up space on the /boot partition.
rpm -qa 'kernel*' rpm -e kernel-<version number here> FYI: kernel-2.6.9-11.ELsmp is quite a bit out of date(RHEL4 update 1), it may be a good idea to plan and execute a system restart. The latest is kernel-smp-2.6.9-67.0.1.EL Dec. 21, 2007 FYI: You might want to fully update this system before the restart also. |
Quote:
Thanks for your reply, I really appreciate your time. See the output #rpm -qa | grep kernel kernel-2.6.9-11.EL kernel-utils-2.4-13.1.66 kernel-smp-2.6.9-11.EL I cant reboot the system as clients applications are running on this server. Can you suggest something else? I know it may create problem if i reboot the server, so can we save whats in the server and then once satisfied then take risk to reboot? waiting for your help. Sam |
I suggested that you plan (schedule a date/time) a update/maintenance/reboot of the system, this is a good idea please consider doing so ASAP. The kernel for one has been updated numerous times for one, so based on the information you posted;
Quote:
If the output from the typed command cat /etc/*release shows that the system is at the update 5 level then the running smp kernel should be upgraded to at least the 2.6.9-55.EL smp kernel. As a suggestion try unmounting the /boot partition; unmount /dev/sda1 After verifying that /dev/sda1 is the boot partition, then remount the partition; mount -t auto /dev/sda1 /boot FYI: one does not need the /boot partition to be mounted unless a kernel or module update is being done. Code:
$ parted /dev/sda |
All times are GMT -5. The time now is 07:28 PM. |