Why does not update-grub detect Fedora 13 installation?

H.S. hs.samix at gmail.com
Mon Jul 12 18:39:14 UTC 2010

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
        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
        linux /boot/vmlinuz- root=/dev/sdc13

Both logical partitions.

Besides, I don't think BIOS is booting from the partitions at all on my
system. It just checks the mbr of sdc, which is set by grub, and the
computer gets pointed to my /boot partition where vmlinuz continues to
boot. Isn't that broadly what happens?


Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.

More information about the users mailing list