[CentOS] [Newbie] Reclaiming /boot space

Tue Mar 8 23:17:02 UTC 2011
Todd Cary <todd at aristesoftware.com>

Here is the output of mount:

/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/hdc1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

Does not appear to be mounted...correct?

Todd

On 3/8/2011 3:08 PM, Simon Matter wrote:
>> When trying to do a yum update, I am told I need more space in
>> /boot.  When I check the contents of /boot (ls -l /boot), there
>> are no files.
> Hm, that's not good.
>
>> If I do a df -h, there is no available space yet it shows that it
>> has a lot of used space.
> Is /boot mounted? Please show as the output of 'mount'.
>
>> The fstab shows the following:
>>
>> # This file is edited by fstab-sync - see 'man fstab-sync' for
>> details
>> /dev/VolGroup00/LogVol00 /                       ext3
>> defaults        1 1
>> LABEL=/boot             /boot                   ext3
>> defaults        1 2
>> none                    /dev/pts                devpts
>> gid=5,mode=620  0 0
>> none                    /dev/shm                tmpfs
>> defaults        0 0
>> none                    /proc                   proc
>> defaults        0 0
>> none                    /sys                    sysfs
>> defaults        0 0
>> /dev/VolGroup00/LogVol01 swap                    swap
>> defaults        0 0
>> /dev/hda                /media/cdrom            auto
>> pamconsole,exec,noauto,managed 0 0
>>
>> # fschk.ext3 /boot gives this error:
> First, to check the filesystem you have to unmount it. And then to check,
> you usually give the device name, not it's label (I'm not sure it work by
> naming with the label). Usually something like
>
> fsck.ext3 /dev/sda1
>
> Simon
>
>> The superblock could not be read or does not describe a correct ext2
>> filesystem.  If the device is valid and it really contains an ext2
>> filesystem (and not swap or ufs or something else), then the
>> superblock
>> is corrupt, and you might try running e2fsck with an alternate
>> superblock:
>>       e2fsck -b 8193<device>
>>
>> I am not sure what I should do next.
>>
>> Thank you in advance for any suggestions...
>>
>> Todd
>>
>> --
>> Ariste Software
>> Petaluma, CA 94952
>>
>> http://www.aristesoftware.com
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>

-- 
Ariste Software
Petaluma, CA 94952

http://www.aristesoftware.com