/boot partition at 100%

aolong · 11-13-2009, 07:37 AM

How to fix a /boot partition that's at 100% usage... I cannot remove any linux images through synaptic or dpkg, will only end in errors.

/boot is 98MB mdraid.

pixellany · 11-13-2009, 07:42 AM

Please give us a more complete description of your system---including the output of "sudo fdisk -l" (ell, not one)

aolong · 11-13-2009, 07:46 AM

---------------------------------------
along@apollo:~$ sudo fdisk -l
[sudo] password for along:

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa76292b2

Device Boot Start End Blocks Id System
/dev/sda1 * 1 12 96358+ fd Linux raid autodetect
/dev/sda2 13 28882 231898275 fd Linux raid autodetect
/dev/sda3 29916 30401 3903795 fd Linux raid autodetect
/dev/sda4 28883 29915 8297572+ fd Linux raid autodetect

Partition table entries are not in disk order

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0008be8f

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 12 96358+ fd Linux raid autodetect
/dev/sdb2 13 28882 231898275 fd Linux raid autodetect
/dev/sdb3 29916 30401 3903795 fd Linux raid autodetect
/dev/sdb4 28883 29915 8297572+ fd Linux raid autodetect

Partition table entries are not in disk order

Disk /dev/md0: 98 MB, 98566144 bytes
2 heads, 4 sectors/track, 24064 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 237.4 GB, 237463732224 bytes
2 heads, 4 sectors/track, 57974544 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md3: 3997 MB, 3997368320 bytes
2 heads, 4 sectors/track, 975920 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/md2: 8496 MB, 8496611328 bytes
2 heads, 4 sectors/track, 2074368 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table
--------------------------------

along@apollo:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 220G 11G 199G 5% /
varrun 493M 128K 493M 1% /var/run
varlock 493M 0 493M 0% /var/lock
udev 493M 84K 493M 1% /dev
devshm 493M 12K 493M 1% /dev/shm
lrm 493M 40M 454M 8% /lib/modules/2.6.24-25-generic/volatile
/dev/md0 92M 89M 0 100% /boot
/dev/md2 7.9G 2.5G 5.1G 33% /var

----------------------------------

pixellany · 11-13-2009, 07:58 AM

So....what is IN /boot? (Mine is a total of ~10MB)

I would never bother with a separate partition for /boot, but that's another story----we need to find out what is filling up that directory.

In my /boot:

Code:

[mherring@Ath boot]$ ls -lR /boot
/boot:
total 9576
-rw-r--r-- 1 root root  959711 2009-10-23 02:19 System.map26
drwxr-xr-x 2 root root    4096 2009-10-09 09:18 grub
-rw-r--r-- 1 root root 6132383 2009-10-25 07:45 kernel26-fallback.img
-rw-r--r-- 1 root root  818539 2009-10-25 07:44 kernel26.img
-rw-r--r-- 1 root root 1856240 2009-10-23 02:19 vmlinuz26

/boot/grub:
total 324
-rw-r--r-- 1 root root    197 2009-10-09 15:53 default
-rw-r--r-- 1 root root     45 2009-10-09 15:53 device.map
-rw-r--r-- 1 root root   7804 2009-10-09 15:53 e2fs_stage1_5
-rw-r--r-- 1 root root   7356 2009-10-09 15:53 fat_stage1_5
-rw-r--r-- 1 root root   6636 2009-10-09 15:53 ffs_stage1_5
-rw-r--r-- 1 root root   6628 2009-10-09 15:53 iso9660_stage1_5
-rw-r--r-- 1 root root   8216 2009-10-09 15:53 jfs_stage1_5
-rw-r--r-- 1 root root   1745 2009-10-18 17:42 menu.lst
-rw-r--r-- 1 root root   6860 2009-10-09 15:53 minix_stage1_5
-rw-r--r-- 1 root root   9260 2009-10-09 15:53 reiserfs_stage1_5
-rw-r--r-- 1 root root    512 2009-10-09 15:53 stage1
-rw-r--r-- 1 root root 106812 2009-10-09 15:53 stage2
-rw-r--r-- 1 root root 102274 2008-12-28 11:26 stage2_eltorito
-rw-r--r-- 1 root root   6892 2009-10-09 15:53 ufs2_stage1_5
-rw-r--r-- 1 root root   6236 2009-10-09 15:53 vstafs_stage1_5
-rw-r--r-- 1 root root   9052 2009-10-09 15:53 xfs_stage1_5
[mherring@Ath boot]$

aolong · 11-13-2009, 08:04 AM

standard /boot stuff... when I built this system I was new to Ubuntu and didn't realize it hangs on to old kernels when updating...

along@apollo:~$ ls -l /boot
total 84653
-rw-r--r-- 1 root root 422667 2008-08-21 00:46 abi-2.6.24-19-generic
-rw-r--r-- 1 root root 422838 2008-11-24 17:47 abi-2.6.24-22-generic
-rw-r--r-- 1 root root 422838 2009-04-01 21:17 abi-2.6.24-23-generic
-rw-r--r-- 1 root root 422838 2009-09-18 16:18 abi-2.6.24-24-generic
-rw-r--r-- 1 root root 422838 2009-10-20 07:47 abi-2.6.24-25-generic
-rw-r--r-- 1 root root 80049 2008-08-21 00:46 config-2.6.24-19-generic
-rw-r--r-- 1 root root 80062 2008-11-24 17:47 config-2.6.24-22-generic
-rw-r--r-- 1 root root 80051 2009-04-01 21:17 config-2.6.24-23-generic
-rw-r--r-- 1 root root 80051 2009-09-18 16:18 config-2.6.24-24-generic
-rw-r--r-- 1 root root 80113 2009-10-20 07:47 config-2.6.24-25-generic
drwxr-xr-x 2 root root 1024 2009-11-13 08:31 grub
-rw-r--r-- 1 root root 7770195 2008-12-10 11:44 initrd.img-2.6.24-19-generic
-rw-r--r-- 1 root root 7335590 2008-12-10 10:59 initrd.img-2.6.24-19-generic.bak
-rw-r--r-- 1 root root 7770459 2008-12-10 12:23 initrd.img-2.6.24-22-generic
-rw-r--r-- 1 root root 7769172 2008-12-10 12:19 initrd.img-2.6.24-22-generic.bak
-rw-r--r-- 1 root root 7771383 2009-04-16 11:12 initrd.img-2.6.24-23-generic
-rw-r--r-- 1 root root 7771469 2009-04-07 16:23 initrd.img-2.6.24-23-generic.bak
-rw-r--r-- 1 root root 7775324 2009-10-09 15:47 initrd.img-2.6.24-24-generic
-rw-r--r-- 1 root root 7774982 2009-09-29 13:31 initrd.img-2.6.24-24-generic.bak
-rw-r--r-- 1 root root 7774858 2009-10-23 21:53 initrd.img-2.6.24-25-generic
drwx------ 2 root root 12288 2008-12-10 10:54 lost+found
-rw-r--r-- 1 root root 103204 2007-09-28 06:06 memtest86+.bin
-rw-r--r-- 1 root root 905170 2008-08-21 00:46 System.map-2.6.24-19-generic
-rw-r--r-- 1 root root 905617 2008-11-24 17:47 System.map-2.6.24-22-generic
-rw-r--r-- 1 root root 905833 2009-04-01 21:17 System.map-2.6.24-23-generic
-rw-r--r-- 1 root root 906320 2009-09-18 16:18 System.map-2.6.24-24-generic
-rw-r--r-- 1 root root 906551 2009-10-20 07:47 System.map-2.6.24-25-generic
-rw-r--r-- 1 root root 1921464 2008-08-21 00:46 vmlinuz-2.6.24-19-generic
-rw-r--r-- 1 root root 1921176 2008-11-24 17:47 vmlinuz-2.6.24-22-generic
-rw-r--r-- 1 root root 1922520 2009-04-01 21:17 vmlinuz-2.6.24-23-generic
-rw-r--r-- 1 root root 1926040 2009-09-18 16:18 vmlinuz-2.6.24-24-generic
-rw-r--r-- 1 root root 1926456 2009-10-20 07:47 vmlinuz-2.6.24-25-generic

pixellany · 11-13-2009, 08:06 AM

Well---there you have it!! Start deleting the old kernels--and the old initrd files. Or--if you are a hoarder--move them somewhere else.

aolong · 11-13-2009, 08:09 AM

I figured that much, but was unsure if the package manager will balk if packaged it thinks are installed are manually deleted.

aolong · 11-13-2009, 08:11 AM

Got it, removed the .bak files manually, making enough room to uninstall old kernels through dpkg. Thanks for the help.