Why does not update-grub detect Fedora 13 installation?

Tom H tomh0665 at gmail.com
Tue Jul 13 05:35:22 UTC 2010


On Mon, Jul 12, 2010 at 2:39 PM, H.S. <hs.samix at gmail.com> wrote:
> On 12/07/10 01:42 PM, Rick Stevens wrote:
>>
>> /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.
>
> hmm .. then why does it detect OSes on my LVM volumes? I don't think
> BIOS can boot from an LVM volume, can it?
>
> Also, among the other OSes it detected on my system, here are a couple
> of counter examples:
> --------------------------------------------------
> menuentry "Debian, with Linux 2.6.32-100601-1394 (on /dev/sdc6)" {
>        insmod part_msdos
>        insmod ext2
>        set root='(/dev/sdc,msdos5)'
>        search --no-floppy --fs-uuid --set
> 9db23921-b7bc-4f1f-8b31-306f2126af0e
>        linux /vmlinuz-2.6.32-100601-bijli-1394
> root=UUID=0300e89b-ae92-43f5-b1f0-0d53c2b589ca ro vga=792 quiet
>        initrd /initrd.img-2.6.32-100601-bijli-1394
> }
> menuentry "Fedora release 9 (Sulphur) (on /dev/sdc13)" {
>        insmod part_msdos
>        insmod ext2
>        set root='(/dev/sdc,msdos13)'
>        search --no-floppy --fs-uuid --set
> 3cfc63bf-9e84-49a3-90ad-3fa623141200
>        linux /boot/vmlinuz-2.6.26.6-79.fc9.i686 root=/dev/sdc13
> }
> --------------------------------------------------

grub2 can boot from an lvm'd /boot; it needs an "insmod lvm".


More information about the users mailing list