Why does not update-grub detect Fedora 13 installation?
tomh0665 at gmail.com
Tue Jul 13 05:31:00 UTC 2010
On Mon, Jul 12, 2010 at 1:49 PM, Suvayu Ali <fatkasuvayu+linux at gmail.com> wrote:
> On Monday 12 July 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
>> (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.
> In that case that should have worked. (even grub 1 would work with that)
> I am not well versed with grub, but have you checked whether you have
> the correct "device.map" file?
device.map is only used at install time.
More information about the users