Why does not update-grub detect Fedora 13 installation?

Rick Stevens ricks at nerd.com
Mon Jul 12 17:42:01 UTC 2010

On 07/12/2010 10:20 AM, H.S. wrote:
> On 12/07/10 12:50 PM, Suvayu Ali wrote:
>> On Monday 12 July 2010 08:08 AM, H.S. wrote:
>>> I am using LVM. F13 is installed with its / mounted on
>>> /dev/mapper/vg1-lv8 and its boot on /dev/sdc5. Update-grub appears to
>>> miss detecting the kernels in /dev/sdc5 altogether. Any idea why is
>>> that? Is there is a bug in Fedora 13?
>> I think its because grub 1 doesn't have LVM support. If you need LVM
>> support install grub2.
> Yes, that is the one I am using:
> grub-pc   1.98+20100706-1   GRand Unified Bootloader, version 2 (PC/BIOS
> version)
> (sorry I skipped mentioning this earlier).
> Note that boot partitions for both distros (F13 and Debian) are on
> non-LVM partitions precisely because even grub2 may not handle LMV boot
> partitions properly ... not sure about this though so just wanted to be
> cautious. Debian's /boot is on /dev/sdc3 and Fedora 13's /boot is on
> /dev/sdc5. Their other partitions (/, /usr, /home) all are on LVM volumes.

/dev/sdc5 is an extended partition.  IIRC, update-grub only checks
primary partitions--primarily because your BIOS can't boot anything in
an extended partition, either.
- Rick Stevens, Systems Engineer, C2 Hosting          ricks at nerd.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-   Which is worse: ignorance or apathy?  I don't know.  Who cares?  -

More information about the users mailing list