On 07/12/2010 11:39 AM, H.S. 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
}
--------------------------------------------------
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?
Yes, but even though grub can boot /dev/sdc5, I don't think the update
utility you're using to update grub.conf _checks_ extended partitions
to put appropriate entries in the config file.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, C2 Hosting ricks(a)nerd.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Reality: A crutch for those who can't handle science fiction -
----------------------------------------------------------------------