100% disk space on boot is in use?

[Heikki Pesonen]

My firs attempt to install Linux to my computer failed totally. After
it I had to reinstall all. The first Linux was Fedora core 3 or 4.
After trying other distros I recently installed Fedora Core 5 which I
like very much. It's slick (very fast) and looks nice.
But every time I start Fedora a message appears: "100% disk space on
boot is in use". Does that be a problem in the future?
Recently I have three hard disks on my computer as you can see:

[code]
[root@localhost fossiili]# /sbin/fdisk -l

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           1        8001   8e  Linux LVM
/dev/hda2               2        4358    34997602+   f  W95 Ext'd (LBA)
/dev/hda3   *        4359        9729    43142557+   7  HPFS/NTFS
/dev/hda5               2        4358    34997571    7  HPFS/NTFS

Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *           1          13      104391   83  Linux
/dev/hdb2              14       19457   156183930   8e  Linux LVM

Disk /dev/sda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         255     2048256    b  W95 FAT32
/dev/sda2             256       14946   118005457+   7  HPFS/NTFS

Disk /dev/dm-0: 157.8 GB, 157806493696 bytes
255 heads, 63 sectors/track, 19185 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/dm-1: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table
[/CODE]

hda and sda are used by Windows, except hda1 which is a souvenir from
my last trip to Fedora Core world , what to do with hda1?

hdb is a large disk 160 GB and allocated for Linuxes. There were some
partitions which I had thought for Fedora's use. Unfortunately I was
frighten while installing Fedora because I remember the previous
Fedora installation. I did not find the way to get partition manager
to do what I wanted so I gave all hdb to Fedora. The installation
seemed to proceed well, but after it I could not start neither Fedora
nor Windows. Fortunately I could repair Windows installation and also
the Grub, thanks to good advice from different countries.

I know, that LVM makes me possible to change logical volumes but not
just the one were /boot is residing. I am not very keen on installing
Fedora again, but is there any other possibility?

Is it possible to repartition hdb in Fedora so that I could install an
other distro also to hdb?

[Mikkel]

Heikki Pesonen wrote:
>  My firs attempt to install Linux to my computer failed totally.
> After
>  it I had to reinstall all. The first Linux was Fedora core 3 or 4.
>  After trying other distros I recently installed Fedora Core 5 which I
>  like very much. It's slick (very fast) and looks nice.
>  But every time I start Fedora a message appears: "100% disk space on
>  boot is in use". Does that be a problem in the future?
>  Recently I have three hard disks on my computer as you can see:
>   
What it is telling you is that the /boot partition is full. This may
be a problem when you go to install a new kernel. You can find out
where your /boot partition is by running "mount | grep boot". You
may also want to take a look at the /boot directory on your system
to see what is all in there. If you post the output of "ls /boot"
and "cat /boot/grub/grub.conf" and we can poit out files you may
safely delete.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

[Heikki Pesonen]

On 6/29/06, Mikkel L. Ellertson <mikkel(a)infinity-ltd.com&gt; wrote:
>  Heikki Pesonen wrote:
>  > After trying other distros I recently installed Fedora Core 5 which I
>  > like very much.
>  > But every time I start Fedora a message appears: "100% disk space on
>  > boot is in use". Does that be a problem in the future? 
>  What it is telling you is that the /boot partition is full. This may
>  be a problem when you go to install a new kernel. You can find out
>  where your /boot partition is by running "mount | grep boot". 
[fossiili@localhost ~]$ mount | grep /boot
/dev/hdb1 on /boot type ext3 (rw)

>  take a look at the /boot directory on your system
>  to see what is all in there. 
If you post the output of "ls /boot"
[root@localhost fossiili]# ls /boot
config-2.6.15-1.2054_FC5      pup001
config-2.6.17-1.2139_FC5      pup_save.3fs
dev_save                      System.map-2.6.15-1.2054_FC5
grub                          System.map-2.6.17-1.2139_FC5
initrd-2.6.15-1.2054_FC5.img  vmlinuz-2.6.15-1.2054_FC5
initrd-2.6.17-1.2139_FC5.img  vmlinuz-2.6.17-1.2139_FC5
lost+found
[root@localhost fossiili]#

>  and "cat /boot/grub/grub.conf" and we can poit out files
> you may
>  safely delete. 
[root@localhost grub]# cat grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd1,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.17-1.2139_FC5)
        root (hd1,0)
        kernel /vmlinuz-2.6.17-1.2139_FC5 ro root=/dev/VolGroup00/LogVol00
rhgb quiet
        initrd /initrd-2.6.17-1.2139_FC5.img
title Fedora Core (2.6.15-1.2054_FC5)
        root (hd1,0)
        kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/LogVol00
rhgb quiet
        initrd /initrd-2.6.15-1.2054_FC5.img
title WinXP
        rootnoverify (hd0,2)
        chainloader +1
[root@localhost grub]#

THANK YOU for your clear and simple advice! The problem is related with the
nice and reliable Puppy Linux liveCD.  "pup001" is it's previous versions
save file of the size 75.9 MB safely remowe.

[Ambrogio]

Il giorno gio, 29/06/2006 alle 18.33 +0300, Heikki Pesonen ha scritto:
>  hda and sda are used by Windows, except hda1 which is a souvenir
> from
>  my last trip to Fedora Core world , what to do with hda1? 
Where is your boot
partition?
It's in hda1 (LVM)? Maybe that LVM can be expanded. You can post the
output of vgdisplay -v?

>  hdb is a large disk 160 GB and allocated for Linuxes. There were
> some
>  partitions which I had thought for Fedora's use. Unfortunately I was
>  frighten while installing Fedora because I remember the previous
>  Fedora installation. I did not find the way to get partition manager
>  to do what I wanted so I gave all hdb to Fedora. The installation
>  seemed to proceed well, but after it I could not start neither Fedora
>  nor Windows. Fortunately I could repair Windows installation and also
>  the Grub, thanks to good advice from different countries.
>  
>  I know, that LVM makes me possible to change logical volumes but not
>  just the one were /boot is residing. I am not very keen on installing
>  Fedora again, but is there any other possibility? 
The boot filesystem can be
expanded for example by booting from a live
cd. If you have free space on LV.

>  Is it possible to repartition hdb in Fedora so that I could install
> an
>  other distro also to hdb? 
You want not to loss data?
In this case it's possible, but you have to change filesystem size and
LV to shrink it, if you don't have free space on VG.
With vgdisplay -v we can see if you can or not

Bye
 Ambrogio

[Markku Kolkka]

Ambrogio kirjoitti viestissään (lähetysaika torstai, 29. 
kesäkuuta 2006 18:51):
>  Where is your boot partition?
>  It's in hda1 (LVM)? Maybe that LVM can be expanded. You can
>  post the output of vgdisplay -v? 
/boot can't be on LVM, it must be a normal partition. 

-- 
 Markku Kolkka
 markku.kolkka(a)iki.fi

[Ambrogio]

Il giorno gio, 29/06/2006 alle 20.44 +0300, Markku Kolkka ha scritto:
>  Ambrogio kirjoitti viestissään (lähetysaika torstai, 29. 
>  kesäkuuta 2006 18:51):
>  > Where is your boot partition?
>  > It's in hda1 (LVM)? Maybe that LVM can be expanded. You can
>  > post the output of vgdisplay -v?
>  
>  /boot can't be on LVM, it must be a normal partition.  
You are rigth.
I'm sorry for the mistake.

So in my mail a lot of things are wrong.
But boot filesystem can be expanded only if partition can be expanded.

Bye
 Ambrogio

[Heikki Pesonen]

On 6/29/06, Ambrogio <fn050202(a)flashnet.it&gt; wrote:
>  Il giorno gio, 29/06/2006 alle 18.33 +0300, Heikki Pesonen ha
> scritto:
>  > hda and sda are used by Windows, except hda1 which is a souvenir from
>  > my last trip to Fedora Core world , what to do with hda1?
>  Where is your boot partition?
>  It's in hda1 (LVM)? Maybe that LVM can be expanded. You can post the
>  output of vgdisplay -v? 
Unfortunately
"[root@localhost fossiili]# /sbin/vgdisplay -v
bash: /sbin/vgdisplay: No such file or directory
[root@localhost fossiili]#"

For some reason I can not get vgdisplay to work.

[Ambrogio]

Il giorno ven, 30/06/2006 alle 09.05 +0300, Heikki Pesonen ha scritto:
>  On 6/29/06, Ambrogio <fn050202(a)flashnet.it&gt; wrote:
>  > Il giorno gio, 29/06/2006 alle 18.33 +0300, Heikki Pesonen ha scritto:
>  > > hda and sda are used by Windows, except hda1 which is a souvenir from
>  > > my last trip to Fedora Core world , what to do with hda1?
>  > Where is your boot partition?
>  > It's in hda1 (LVM)? Maybe that LVM can be expanded. You can post the
>  > output of vgdisplay -v?
>  
>  Unfortunately
>  "[root@localhost fossiili]# /sbin/vgdisplay -v
>  bash: /sbin/vgdisplay: No such file or directory
>  [root@localhost fossiili]#"
>  
>  For some reason I can not get vgdisplay to work. 
locate vgdisplay?
in my Fedora is locate on /usr/sbin

Bye
 Ambrogio

[magicus]

Heikki Pesonen wrote:

>  Unfortunately
>  "[root@localhost fossiili]# /sbin/vgdisplay -v
>  bash: /sbin/vgdisplay: No such file or directory
>  [root@localhost fossiili]#"
>  
>  For some reason I can not get vgdisplay to work.
>   
$ locate vgdisplay
/usr/bin/svgdisplay
/usr/sbin/vgdisplay
/usr/share/man/man8/vgdisplay.8.gz


-- 

Music: http://www.myspace.com/acidredux

Links: http://del.icio.us/furlan

Home:  http://flprim.us/index.html

"Play--more than piety, more than charity or vigilance--is what allows 
human beings to transcend evil."
-- Tom Robbins (Jitterbug Perfume)

[Heikki Pesonen]

On 7/1/06, magicus <magicus(a)snet.net&gt; wrote:
>  Heikki Pesonen wrote:>
>  > For some reason I can not get vgdisplay to work.
>  >
>  $ locate vgdisplay 

Thanks for learning  a new  use full command  "locate"! I should have
guessed, that something like that exists. Is there any book or some kind of
index in the Net for all Bash(?) commands? All in Fedora Core?

The output of vgdisplay is long, so I include it at the end. Before that,
please could you give me a relatively simple advice (usufull for a 72 year
old grandpa) how to shrink the Fedora Core partition other than /boot, so
that I will have free space on hdb to install other distros?

[code]
[root@localhost fossiili]# /usr/sbin/vgdisplay -v
    Finding all volume groups
    Finding volume group "VolGroup00"
  --- Volume group ---
  VG Name               VolGroup00
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               148.94 GB
  PE Size               32.00 MB
  Total PE              4766
  Alloc PE / Size       4765 / 148.91 GB
  Free  PE / Size       1 / 32.00 MB
  VG UUID               UURgQ9-DOYj-IzSI-y2tu-H9rn-10hP-hN1dTB

  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol00
  VG Name                VolGroup00
  LV UUID                upL4ui-Ld7j-VUx9-F3In-M5hM-LLhN-Si8Uwd
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                146.97 GB
  Current LE             4703
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol01
  VG Name                VolGroup00
  LV UUID                30prYX-StTl-xR4l-gr8p-4D29-2ngD-9HJdNm
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.94 GB
  Current LE             62
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:1

  --- Physical volumes ---
  PV Name               /dev/hdb2
  PV UUID               OxdBU7-tT5S-ZL4c-goCu-awWP-fWub-r6KIFk
  PV Status             allocatable
  Total PE / Free PE    4766 / 1

[root@localhost fossiili]#

[/CODE]

[Ambrogio]

Il giorno sab, 01/07/2006 alle 09.03 +0300, Heikki Pesonen ha scritto:

>  Thanks for learning  a new  use full command  "locate"! I
> should have
>  guessed, that something like that exists. Is there any book or some
>  kind of index in the Net for all Bash(?) commands? All in Fedora
>  Core?  
Well, locate is not a Bash command.
It's an executable 'command', that you can launch from shell
There are tons of command (ls for example is a command), and also bash
is a command.
I don't know where you can found an exaustive list. But you can use the
man command to know something apropos of an argument.
For example (about locate) you can use the command man -k find.
You obtain a list of man pages in which the description contain the word
file. In this list you can find locate.
Use of man -k (or apropos) with grep is usefull for finding command.

>  [code]
>  [root@localhost fossiili]# /usr/sbin/vgdisplay -v 
>      Finding all volume groups
>      Finding volume group "VolGroup00"
>    --- Volume group ---
>    VG Name               VolGroup00
>    System ID
>    Format                lvm2
>    Metadata Areas        1 
>    Metadata Sequence No  3
>    VG Access             read/write
>    VG Status             resizable
>    MAX LV                0
>    Cur LV                2
>    Open LV               2
>    Max PV                0
>    Cur PV                1
>    Act PV                1
>    VG Size               148.94 GB
>    PE Size               32.00 MB
>    Total PE              4766
>    Alloc PE / Size       4765 / 148.91 GB
>    Free  PE / Size       1 / 32.00 MB
>    VG UUID               UURgQ9-DOYj-IzSI-y2tu-H9rn-10hP-hN1dTB
>  
>    --- Logical volume ---
>    LV Name                /dev/VolGroup00/LogVol00
>    VG Name                VolGroup00
>    LV UUID                upL4ui-Ld7j-VUx9-F3In-M5hM-LLhN-Si8Uwd 
>    LV Write Access        read/write
>    LV Status              available
>    # open                 1
>    LV Size                146.97 GB
>    Current LE             4703
>    Segments               1
>    Allocation             inherit 
>    Read ahead sectors     0
>    Block device           253:0
>  
>    --- Logical volume ---
>    LV Name                /dev/VolGroup00/LogVol01
>    VG Name                VolGroup00
>    LV UUID                30prYX-StTl-xR4l-gr8p-4D29-2ngD-9HJdNm 
>    LV Write Access        read/write
>    LV Status              available
>    # open                 1
>    LV Size                1.94 GB
>    Current LE             62
>    Segments               1
>    Allocation             inherit 
>    Read ahead sectors     0
>    Block device           253:1
>  
>    --- Physical volumes ---
>    PV Name               /dev/hdb2
>    PV UUID               OxdBU7-tT5S-ZL4c-goCu-awWP-fWub-r6KIFk
>    PV Status             allocatable 
>    Total PE / Free PE    4766 / 1
>  
>  [root@localhost fossiili]#
>  
>  [/CODE] 
Ok, 

vgdisplay says that you ave 2 volumes.
One if 1.94 GB and we don't know what filesystem is, and where is
mounted.
The other is 146.97 GB, and we can think is your /
So you can free space in your VG.
Steps are:
1. Reduce File system
2. reduce LV
I suggest you to read well the LVM-howto for first, to know how LVM
works.
After that you have to calc very well the dimension of filesystem and
Volume, because wrong in this calc results in loss of data.
Tell me now if you need help in this step.
Bye
 Ambrogio

[Heikki Pesonen]

On 7/1/06, Ambrogio <fn050202(a)flashnet.it&gt; wrote:
>  Il giorno sab, 01/07/2006 alle 09.03 +0300, Heikki Pesonen ha scritto:
>  how to shrink the Fedora Core partition other than /boot, so that I will
>  have free space on hdb to install other distros?
>
>  vgdisplay says that you ave 2 volumes.
>  One if 1.94 GB and we don't know what filesystem is, and where is
>  mounted.
>  The other is 146.97 GB, and we can think is your /
>  So you can free space in your VG.
>  Steps are:
>  1. Reduce File system
>  2. reduce LV
>  I suggest you to read well the LVM-howto for first, to know how LVM
>  works.
>  After that you have to calc very well the dimension of filesystem and
>  Volume, because wrong in this calc results in loss of data.
>  Tell me now if you need help in this step. 

Yeas I need help ....
I found http://www.tldp.org/HOWTO/LVM-HOWTO/recipesplitvg.html

Reading it  through  I  found the chapter "13.7. Splitting a volume
group"Before
I start reading and applying the advice there, I kindly ask: Is it the right
place for me?

I do want to split the Fedora volume group. I want to free let's say 100 GB
out from the hands of Fedora.

About the data in hdb: that volume is sacrifyed for my Linux experiments. I
could well to reinstall Fedora 5 hoping that in that 3. attempt everything
will work and the result will be let's say 40 GB for Fedora and the rest of
hdb free to be used later. But the partition tool offered by the
installation script has two times been too difficult for me, so perhaps
better to try to learn more by trying to manipulate hdb using recent Fedora
installation. I suppose I already understand a lot about LVM, but perhaps
not enough.

[Markku Kolkka]

Heikki Pesonen kirjoitti viestissään (lähetysaika lauantai, 1. 
heinäkuuta 2006 13:19):
>  I found http://www.tldp.org/HOWTO/LVM-HOWTO/recipesplitvg.html
>
>  Reading it  through  I  found the chapter "13.7. Splitting a
>  volume group"Before
>  I start reading and applying the advice there, I kindly ask:
>  Is it the right place for me? 
No, you can't split a VG that contains only a single physical 
volume.

>  About the data in hdb: that volume is sacrifyed for my Linux
>  experiments. I could well to reinstall Fedora 5 hoping that in
>  that 3. attempt everything will work and the result will be
>  let's say 40 GB for Fedora and the rest of hdb free to be used
>  later. 
I set up my 160GB disk with 4 physical volumes so that I could 
shrink the VG size to create non-partitioned space if necessary.

-- 
 Markku Kolkka
 markku.kolkka(a)iki.fi

[Heikki Pesonen]

On 7/1/06, Markku Kolkka <markkuk(a)tuubi.net&gt; wrote:
>   you can't split a VG that contains only a single physical
>  volume.
>  I set up my 160GB disk with 4 physical volumes so that I could
>  shrink the VG size to create non-partitioned space if necessary. 

I know, that LVM is good for large systems. For home use as in my case,
there is no reason to be involved with it, because nowadays hard disk space
is cheep. Only in the case one collects large set of  sound and video files,
the costs could be reasonable. In the case of Fedora there is some reason
may it be LVM or something else, which makes installing Fedora hazardous.
I'm not the only one who has gotten his computer completely confused in an
attempt to install Fedora.

Any case, after all kind advice I have here received, it seems to me, that
instead of trying to modify my recent Fedora installation I must try again
installing it on a single partition (40 GB). Or to create a  separate 500 MB
partition for /boot and  10 GB for /home and 1 GB for /swap and 30 GB for /.


The problem is, that I hoped to be able to do all that while installing
Fedora, will try that again next time. May be I could create those
partitions with some liveCD-Linux (Puppy, Knoppix ...) so they will be ready
on hdb when I start installing Fedora. Is there any command line tool for
that I will probably find in liveCD-Linux?

[Claude Jones]

On Saturday July 01 2006 9:36 am, Heikki Pesonen wrote:
>  The problem is, that I hoped to be able to do all that while
> installing
>  Fedora, will try that again next time. May be I could create those
>  partitions with some liveCD-Linux (Puppy, Knoppix ...) so they will be
>  ready on hdb when I start installing Fedora. Is there any command line tool
>  for that I will probably find in liveCD-Linux? 
You can do all that while installing. Read the screens carefully - it's not 
completely self-evident, but, it's not hard. 
-- 
Claude Jones
Brunswick, MD, USA

[Anne Wilson]

On Saturday 01 July 2006 15:30, Claude Jones wrote:
>  On Saturday July 01 2006 9:36 am, Heikki Pesonen wrote:
>  > The problem is, that I hoped to be able to do all that while installing
>  > Fedora, will try that again next time. May be I could create those
>  > partitions with some liveCD-Linux (Puppy, Knoppix ...) so they will be
>  > ready on hdb when I start installing Fedora. Is there any command line
>  > tool for that I will probably find in liveCD-Linux?
>
>  You can do all that while installing. Read the screens carefully - it's not
>  completely self-evident, but, it's not hard.
>   
I can't remember the wording, but you'd be looking for something like
'custom 
partitions'.  It easy then, IIRC.

Anne

[Ambrogio]

Il giorno sab, 01/07/2006 alle 13.19 +0300, Heikki Pesonen ha scritto:
>  
>  
>  On 7/1/06, Ambrogio <fn050202(a)flashnet.it&gt; wrote: 
>  
>  Yeas I need help .... 
>  I found http://www.tldp.org/HOWTO/LVM-HOWTO/recipesplitvg.html
>  
>  Reading it  through  I  found the chapter 
>  "13.7. Splitting a volume group"
>  Before I start reading and applying the advice there, I kindly ask: Is
>  it the right place for me? 
No.
It treat about multiple VG, but you have already done it, and you don't
have free space on disks.

I think now is better to start help you in freeing space, but I think
list is not a good place.
Is better to continue by private mail

Bye
 Ambrogio

[Markku Kolkka]

Heikki Pesonen kirjoitti viestissään (lähetysaika lauantai, 1. 
heinäkuuta 2006 09:03):
>  The output of vgdisplay is long, so I include it at the end.
>  Before that, please could you give me a relatively simple
>  advice (usufull for a 72 year old grandpa) how to shrink the
>  Fedora Core partition other than /boot, so that I will have
>  free space on hdb to install other distros? 
LVM doesn't currently support resizing physical volumes, so you 
can only free space inside the LVM volume group without 
destroying the FC5 installation. You can use that space to 
install other distros that support LVM and allow sharing 
the /boot partition.

-- 
 Markku Kolkka
 markku.kolkka(a)iki.fi

[Charles Curley]

On Thu, Jun 29, 2006 at 06:33:02PM +0300, Heikki Pesonen wrote:
>  My firs attempt to install Linux to my computer failed totally.
> After
>  it I had to reinstall all. The first Linux was Fedora core 3 or 4.
>  After trying other distros I recently installed Fedora Core 5 which I
>  like very much. It's slick (very fast) and looks nice.
>  But every time I start Fedora a message appears: "100% disk space on
>  boot is in use". Does that be a problem in the future?
>  Recently I have three hard disks on my computer as you can see: 

>  
>  Disk /dev/hdb: 160.0 GB, 160041885696 bytes
>  255 heads, 63 sectors/track, 19457 cylinders
>  Units = cylinders of 16065 * 512 = 8225280 bytes
>  
>    Device Boot      Start         End      Blocks   Id  System
>  /dev/hdb1   *           1          13      104391   83  Linux
>  /dev/hdb2              14       19457   156183930   8e  Linux LVM
>   
I conclude from your fdisk output that your /boot partition is
hdb1. It looks like it should be big enough. In fact it's the same
size as mine, 114MB.

I have three kernels installed on my desktop and they occupy all of
13MB. Here's a complete list of it:

[root@charlesc images]# ll /boot/ -tr
total 10289
drwx------  2 root root   12288 Dec 21  2005 lost+found
-rw-r--r--  1 root root   94600 Feb  8 08:39 memtest86+-1.65
-rw-r--r--  1 root root 1510257 Mar 14 14:01 vmlinuz-2.6.15-1.2054_FC5
-rw-r--r--  1 root root  811765 Mar 14 14:01 System.map-2.6.15-1.2054_FC5
-rw-r--r--  1 root root   63896 Mar 14 14:01 config-2.6.15-1.2054_FC5
-rw-r--r--  1 root root 1059212 Apr 23 07:28 initrd-2.6.15-1.2054_FC5.img
-rw-r--r--  1 root root 1509474 May 21 13:13 vmlinuz-2.6.16-1.2122_FC5
-rw-r--r--  1 root root  810738 May 21 13:13 System.map-2.6.16-1.2122_FC5
-rw-r--r--  1 root root   64573 May 21 13:13 config-2.6.16-1.2122_FC5
-rw-r--r--  1 root root 1059185 May 30 18:03 initrd-2.6.16-1.2122_FC5.img
-rw-r--r--  1 root root 1519016 Jun  5 23:44 vmlinuz-2.6.16-1.2133_FC5
-rw-r--r--  1 root root  810738 Jun  5 23:44 System.map-2.6.16-1.2133_FC5
-rw-r--r--  1 root root   64562 Jun  5 23:44 config-2.6.16-1.2133_FC5
-rw-r--r--  1 root root 1063866 Jun 13 14:04 initrd-2.6.16-1.2133_FC5.img
drwxr-xr-x  2 root root    1024 Jun 20 11:50 grub
drwxr-xr-x  4 root root    1024 Jun 20 11:50 .
drwxr-xr-x 25 root root    4096 Jun 23 16:52 ..

You should go through your /boot/grub/grub.conf, compare it to your
/boot, and eliminate anything that grub doesn't need (/boot/grub) or
call out in one stanza or another. Do not, however, remove lost+found;
fsck requires it. Grub does not call out the System.map directly, but
I'd leave it in for any kernel you keep. Just in case.

Just to be careful, first make a boot CD. Then see what went onto the
boot CD. Then eliminate by copying elsewhere rather than deleting.

If that doesn't solve your problem, boot to a live CD system (I use
finnix), and fsck all your Linux partitions.


>  
>  
>  Is it possible to repartition hdb in Fedora so that I could install an
>  other distro also to hdb? 
Yes. Use your LVM tools (again, I use finnix for this) to carve up
your LVM stuff. Several different Linuxes can share /boot, as long as
file names don't collide.

You will have to manually merge all the different grub.confs as you
install them. Perhaps someone has a script to do this handy?

You can also share /home if it is on its own logical partition, but
that could be dangerous due to version issues between the different
distributions.

-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

[Charles Curley]

On Thu, Jun 29, 2006 at 12:24:58PM -0600, Charles Curley wrote:
>  
>  > 
>  > Disk /dev/hdb: 160.0 GB, 160041885696 bytes
>  > 255 heads, 63 sectors/track, 19457 cylinders
>  > Units = cylinders of 16065 * 512 = 8225280 bytes
>  > 
>  >   Device Boot      Start         End      Blocks   Id  System
>  > /dev/hdb1   *           1          13      104391   83  Linux
>  > /dev/hdb2              14       19457   156183930   8e  Linux LVM
>  > 
>  
>  I conclude from your fdisk output that your /boot partition is
>  hdb1. It looks like it should be big enough. In fact it's the same
>  size as mine, 114MB. 
Oops, I misread my fdisk output. It's the same size as another
partiton, at 102 MB. Stil plenty for the job at hand.

-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB