From: Thomas E. Maleshafske on
Ant wrote:

> On 2/25/2010 3:55 PM PT, unruh typed:
>
>>>> How can I resize my /'s /boot to get more free disk space without
>>>> getting another bigger HDD to copy over or reinstalling from
scratch?
>>
>> Sorry, you are very unclear. Do you have a completely separate
partition
>> /boot and for /? Or is /boot just a directory in /?
>
> $ cd /
> $ ls -all
> total 65
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 .
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 ..
> drwxr-xr-x 2 root root 4096 2010-02-22 06:56 bin
> drwxr-xr-x 3 root root 1024 2010-02-21 08:27 boot
> lrwxrwxrwx 1 root root 11 2007-08-27 22:58 cdrom -> media/cdrom
> -rw-r--r-- 1 root root 4 2008-05-08 04:35 debian-binary
> drwxr-xr-x 15 root root 3920 2010-02-25 14:44 dev
> drwxr-xr-x 172 root root 10240 2010-02-25 17:14 etc
> drwxr-xr-x 6 ant ant 4096 2008-10-14 20:53 extra
> drwxr-xr-x 7 root root 4096 2008-01-27 11:12 home
> drwxr-xr-x 2 root root 1024 2007-08-27 22:59 initrd
> lrwxrwxrwx 1 root root 28 2009-12-05 18:24 initrd.img ->
> boot/initrd.img-2.6.30-2-686
> drwxr-xr-x 13 root root 9216 2010-02-24 06:31 lib
> drwxr-xr-x 4 root root 1024 2010-02-24 06:31 media
> drwxr-xr-x 3 root root 1024 2009-06-12 13:31 mnt
> drwxr-xr-x 3 root root 1024 2008-05-25 03:52 opt
> drwxr-xr-x 3 root root 1024 2008-09-15 13:23 others
> dr-xr-xr-x 153 root root 0 2010-02-23 00:11 proc
> drwxr-xr-x 19 root root 1024 2010-02-25 11:37 root
> drwxr-xr-x 2 root root 5120 2010-02-25 11:36 sbin
> drwxr-xr-x 2 root root 1024 2008-09-16 00:38 selinux
> drwxr-xr-x 3 root root 1024 2009-03-10 07:04 srv
> drwxr-xr-x 8 root root 4096 2009-12-20 05:24 storage
> drwxr-xr-x 2 root root 1024 2007-08-27 22:58 stuff
> drwxr-xr-x 12 root root 0 2010-02-23 00:11 sys
> drwxrwxrwt 10 root root 4096 2010-02-25 15:34 tmp
> drwxr-xr-x 13 root root 4096 2008-01-27 11:11 usr
> drwxr-xr-x 16 root root 4096 2010-01-26 08:25 var
> lrwxrwxrwx 1 root root 25 2009-12-05 18:24 vmlinuz ->
> boot/vmlinuz-2.6.30-2-686
> $ cd /boot
> $ ls -all
> total 22028
> drwxr-xr-x 3 root root 1024 2010-02-21 08:27 .
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 ..
> -rw-r--r-- 1 root root 103541 2009-12-03 21:08 config-2.6.30-2-686
> drwxr-xr-x 3 root root 6144 2010-01-26 07:43 grub
> -rw-r--r-- 1 root root 9833276 2010-02-21 08:27
initrd.img-2.6.30-2-686
> -rw-r--r-- 1 root root 9363480 2010-01-22 08:57
> initrd.img-2.6.30-2-686.bak
> -rw-r--r-- 1 root root 1125733 2009-12-03 21:08
System.map-2.6.30-2-686
> -rw-r--r-- 1 root root 2024880 2009-12-03 21:07
vmlinuz-2.6.30-2-686
>
> Does that help? Maybe I was not saying it correctly.
What is the content of your boot directory, you may have old images
that can be deleted.
--
V/R
Thomas E. Maleshafske
From: Nico Kadel-Garcia on
On Feb 25, 8:15 pm, Ant <a...(a)zimage.comANT> wrote:
> On 2/25/2010 3:44 PM PT, GangGreene typed:
>
>
>
> >> My very old Debian/Linux workstation/desktop box (first installed it on
> >> 9/24/2004 and kept it updated daily and only had one reinstall
> >> (accidently ran fsck without unmounting a few years ago) -- still
> >> amazing that it runs today) is unable to install the latest Kernel
> >> (v2.6.32) Debian package due to free limited disk space in / (actually
> >> /boot) partition:
>
> >> $ df
> >> Filesystem           1K-blocks      Used Available Use% Mounted on
> >> /dev/hda1               280003    173227     92320  66% /
> >> tmpfs                  1297724         0   1297724   0% /lib/init/rw
> >> udev                     10240       264      9976   3% /dev
> >> tmpfs                  1297724         0   1297724   0% /dev/shm
> >> /dev/hda5             14421344   2759732  10929052  21% /home
> >> /dev/hda6              4807056   3620424    942448  80% /usr
> >> /dev/hda7               964500    721228    194276  79% /var
> >> /dev/hda8               964500     17676    897828   2% /tmp
> >> /dev/hda9              4807056    206076   4356796   5% /usr/local
> >> /dev/hda11            47383396  19522168  25454292  44% /extra
> >> /dev/hda12              918322     16452    852874   2% /others


> >> How can I resize my /'s /boot to get more free disk space without
> >> getting another bigger HDD to copy over or reinstalling from scratch?
> >> Can I use KNOPPIX v6.2.1 to do it or is it not possible? I used to use
> >> PowerQuest's PartitionMagic for DOS and Windows to resize, but I wasn't
> >> sure if this method works in Linux too.
>
> > Dude....You don't have a boot partition.
>
> Dude, I do:

Dude, you don't. You have a /boot *directory*, not a /boot partition.
This is revealed by your /df command. It looks like your / partition
is overloaded: Do a bit of cleanup on your / partition, and next time,
consider using a simpler partition scheme. I personally find
separating out /usr/local and /extras and whatever to be begging for
one partition, or another, to run out of space at the worst possible
moments. And 300 Meg is way, way, way too small for a modern "/"
filesystem, due to the potential for precisely this kind of "oh, yes,
I needed to put another few files there".

Do you have a few old kernels you could flush? That could help.

You should be able to fix this with a recent Knoppix CD without too
much grief. But do a backup *first*.
From: Ant on
On 2/26/2010 1:33 AM PT, Nico Kadel-Garcia typed:

> Dude, you don't. You have a /boot *directory*, not a /boot partition.

Oh.


> This is revealed by your /df command. It looks like your / partition
> is overloaded: Do a bit of cleanup on your / partition, and next time,

$ ls -all /
total 65
drwxr-xr-x 25 root root 1024 2010-01-22 10:51 .
drwxr-xr-x 25 root root 1024 2010-01-22 10:51 ..
drwxr-xr-x 2 root root 4096 2010-02-22 06:56 bin
drwxr-xr-x 3 root root 1024 2010-02-21 08:27 boot
lrwxrwxrwx 1 root root 11 2007-08-27 22:58 cdrom -> media/cdrom
-rw-r--r-- 1 root root 4 2008-05-08 04:35 debian-binary
drwxr-xr-x 15 root root 3920 2010-02-25 14:44 dev
drwxr-xr-x 172 root root 10240 2010-02-26 01:15 etc
drwxr-xr-x 6 ant ant 4096 2008-10-14 20:53 extra
drwxr-xr-x 7 root root 4096 2008-01-27 11:12 home
drwxr-xr-x 2 root root 1024 2007-08-27 22:59 initrd
lrwxrwxrwx 1 root root 28 2009-12-05 18:24 initrd.img ->
boot/initrd.img-2.6.30-2-686
drwxr-xr-x 13 root root 9216 2010-02-24 06:31 lib
drwxr-xr-x 4 root root 1024 2010-02-24 06:31 media
drwxr-xr-x 3 root root 1024 2009-06-12 13:31 mnt
drwxr-xr-x 3 root root 1024 2008-05-25 03:52 opt
drwxr-xr-x 3 root root 1024 2008-09-15 13:23 others
dr-xr-xr-x 152 root root 0 2010-02-23 00:11 proc
drwxr-xr-x 19 root root 1024 2010-02-25 11:37 root
drwxr-xr-x 2 root root 5120 2010-02-26 00:52 sbin
drwxr-xr-x 2 root root 1024 2008-09-16 00:38 selinux
drwxr-xr-x 3 root root 1024 2009-03-10 07:04 srv
drwxr-xr-x 8 root root 4096 2009-12-20 05:24 storage
drwxr-xr-x 2 root root 1024 2007-08-27 22:58 stuff
drwxr-xr-x 12 root root 0 2010-02-23 00:11 sys
drwxrwxrwt 10 root root 4096 2010-02-26 00:52 tmp
drwxr-xr-x 13 root root 4096 2008-01-27 11:11 usr
drwxr-xr-x 16 root root 4096 2010-01-26 08:25 var
lrwxrwxrwx 1 root root 25 2009-12-05 18:24 vmlinuz ->
boot/vmlinuz-2.6.30-2-686

I don't see anything else to delete in the / root.


> consider using a simpler partition scheme. I personally find
> separating out /usr/local and /extras and whatever to be begging for
> one partition, or another, to run out of space at the worst possible
> moments. And 300 Meg is way, way, way too small for a modern "/"
> filesystem, due to the potential for precisely this kind of "oh, yes,
> I needed to put another few files there".

Well, it is old from 9/24/2004. I will keep that mind when I do a new
install whenever that is. :)


> Do you have a few old kernels you could flush? That could help.

Nope, all purged. Only 2.6.32 installed.


> You should be able to fix this with a recent Knoppix CD without too
> much grief. But do a backup *first*.

So should I use qtparted to resize my ext3 partitions?
--
"We now go live to Ollie Williams in Channel 5 traffic chopper. What's
scene?" --Tom Tucker. "Everyone looks like ants!" "That is probably
because you're up so high." from Family Guy.
/\___/\
/ /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Nuke ANT from e-mail address: philpi(a)earthlink.netANT
( ) or ANTant(a)zimage.com
Ant is currently not listening to any songs on his home computer.
From: GangGreene on
Ant wrote:

> On 2/25/2010 3:44 PM PT, GangGreene typed:
>
>>> My very old Debian/Linux workstation/desktop box (first installed it on
>>> 9/24/2004 and kept it updated daily and only had one reinstall
>>> (accidently ran fsck without unmounting a few years ago) -- still
>>> amazing that it runs today) is unable to install the latest Kernel
>>> (v2.6.32) Debian package due to free limited disk space in / (actually
>>> /boot) partition:
>>>
>>> $ df
>>> Filesystem 1K-blocks Used Available Use% Mounted on
>>> /dev/hda1 280003 173227 92320 66% /
>>> tmpfs 1297724 0 1297724 0% /lib/init/rw
>>> udev 10240 264 9976 3% /dev
>>> tmpfs 1297724 0 1297724 0% /dev/shm
>>> /dev/hda5 14421344 2759732 10929052 21% /home
>>> /dev/hda6 4807056 3620424 942448 80% /usr
>>> /dev/hda7 964500 721228 194276 79% /var
>>> /dev/hda8 964500 17676 897828 2% /tmp
>>> /dev/hda9 4807056 206076 4356796 5% /usr/local
>>> /dev/hda11 47383396 19522168 25454292 44% /extra
>>> /dev/hda12 918322 16452 852874 2% /others
>>>
>>> (parted) p
>>> Model: ST380011A (ide)
>>> Disk /dev/hda: 80.0GB
>>> Sector size (logical/physical): 512B/512B
>>> Partition Table: msdos
>>>
>>> Number Start End Size Type File system Flags
>>> 1 32.3kB 296MB 296MB primary ext3
>>> 2 296MB 80.0GB 79.7GB extended
>>> 5 296MB 15.3GB 15.0GB logical ext3
>>> 6 15.3GB 20.3GB 5001MB logical ext3
>>> 7 20.3GB 21.3GB 1003MB logical ext3
>>> 8 21.3GB 22.3GB 1003MB logical ext3
>>> 9 22.3GB 27.3GB 5001MB logical ext3
>>> 12 27.3GB 28.3GB 1003MB logical ext3
>>> 10 28.3GB 30.7GB 2418MB logical linux-swap(v1)
>>> 11 30.7GB 80.0GB 49.3GB logical ext3
>>>
>>> http://img98.imageshack.us/img98/6544/screenshot1qs.png for a screen
>>> capture of GParted.
>>>
>>> How can I resize my /'s /boot to get more free disk space without
>>> getting another bigger HDD to copy over or reinstalling from scratch?
>>> Can I use KNOPPIX v6.2.1 to do it or is it not possible? I used to use
>>> PowerQuest's PartitionMagic for DOS and Windows to resize, but I wasn't
>>> sure if this method works in Linux too.
>>
>> Dude....You don't have a boot partition.
>
> Dude, I do:
>
> $ ls -all /boot
> total 22028
> drwxr-xr-x 3 root root 1024 2010-02-21 08:27 .
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 ..
> -rw-r--r-- 1 root root 103541 2009-12-03 21:08 config-2.6.30-2-686
> drwxr-xr-x 3 root root 6144 2010-01-26 07:43 grub
> -rw-r--r-- 1 root root 9833276 2010-02-21 08:27 initrd.img-2.6.30-2-686
> -rw-r--r-- 1 root root 9363480 2010-01-22 08:57
> initrd.img-2.6.30-2-686.bak
> -rw-r--r-- 1 root root 1125733 2009-12-03 21:08 System.map-2.6.30-2-686
> -rw-r--r-- 1 root root 2024880 2009-12-03 21:07 vmlinuz-2.6.30-2-686
>
> Everytime I install a new Kernel package, it tells me not enough free
> disk space because of /dev/hda1. :(


Of course you don't.
Just _LOOK_ at your data that you posted.

Look at your /etc/fstab.

/dev/hda1 is the partition that your root fiesystem is mount on...not your
boot partition.

Your boot is just a directory in the root filesystem mounted on
the /dev/hda1 partition.

If your boot was on a partition it you would have a small partition of 128MB
or less ( I use 52MB ), mounted at /boot in /etc/fstab, although the boot
partition really doesn't need to be mounted.


From: GangGreene on
Ant wrote:

> On 2/26/2010 1:33 AM PT, Nico Kadel-Garcia typed:
>
>> Dude, you don't. You have a /boot *directory*, not a /boot partition.
>
> Oh.
>
>
>> This is revealed by your /df command. It looks like your / partition
>> is overloaded: Do a bit of cleanup on your / partition, and next time,
>
> $ ls -all /
> total 65
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 .
> drwxr-xr-x 25 root root 1024 2010-01-22 10:51 ..
> drwxr-xr-x 2 root root 4096 2010-02-22 06:56 bin
> drwxr-xr-x 3 root root 1024 2010-02-21 08:27 boot
> lrwxrwxrwx 1 root root 11 2007-08-27 22:58 cdrom -> media/cdrom
> -rw-r--r-- 1 root root 4 2008-05-08 04:35 debian-binary
> drwxr-xr-x 15 root root 3920 2010-02-25 14:44 dev
> drwxr-xr-x 172 root root 10240 2010-02-26 01:15 etc
> drwxr-xr-x 6 ant ant 4096 2008-10-14 20:53 extra
> drwxr-xr-x 7 root root 4096 2008-01-27 11:12 home
> drwxr-xr-x 2 root root 1024 2007-08-27 22:59 initrd
> lrwxrwxrwx 1 root root 28 2009-12-05 18:24 initrd.img ->
> boot/initrd.img-2.6.30-2-686
> drwxr-xr-x 13 root root 9216 2010-02-24 06:31 lib
> drwxr-xr-x 4 root root 1024 2010-02-24 06:31 media
> drwxr-xr-x 3 root root 1024 2009-06-12 13:31 mnt
> drwxr-xr-x 3 root root 1024 2008-05-25 03:52 opt
> drwxr-xr-x 3 root root 1024 2008-09-15 13:23 others
> dr-xr-xr-x 152 root root 0 2010-02-23 00:11 proc
> drwxr-xr-x 19 root root 1024 2010-02-25 11:37 root
> drwxr-xr-x 2 root root 5120 2010-02-26 00:52 sbin
> drwxr-xr-x 2 root root 1024 2008-09-16 00:38 selinux
> drwxr-xr-x 3 root root 1024 2009-03-10 07:04 srv
> drwxr-xr-x 8 root root 4096 2009-12-20 05:24 storage
> drwxr-xr-x 2 root root 1024 2007-08-27 22:58 stuff
> drwxr-xr-x 12 root root 0 2010-02-23 00:11 sys
> drwxrwxrwt 10 root root 4096 2010-02-26 00:52 tmp
> drwxr-xr-x 13 root root 4096 2008-01-27 11:11 usr
> drwxr-xr-x 16 root root 4096 2010-01-26 08:25 var
> lrwxrwxrwx 1 root root 25 2009-12-05 18:24 vmlinuz ->
> boot/vmlinuz-2.6.30-2-686
>
> I don't see anything else to delete in the / root.
>
>
>> consider using a simpler partition scheme. I personally find
>> separating out /usr/local and /extras and whatever to be begging for
>> one partition, or another, to run out of space at the worst possible
>> moments. And 300 Meg is way, way, way too small for a modern "/"
>> filesystem, due to the potential for precisely this kind of "oh, yes,
>> I needed to put another few files there".
>
> Well, it is old from 9/24/2004. I will keep that mind when I do a new
> install whenever that is. :)
>
>
>> Do you have a few old kernels you could flush? That could help.
>
> Nope, all purged. Only 2.6.32 installed.

What kernel are you running now 2.4 or 2.6?

I hope your not trying to put a 2.6 kernel on a mchine that is currently
running a 2.4 kernel. That's just begging for trouble.