Bug#548156: grub-installer: No grub2 when using gpt partition schema
Am Donnerstag, den 24.09.2009, 10:05 +0200 schrieb Marcel D.A. Koopmans:
> Package: grub-installer
> Severity: important
>
> I use 2 disks with GPT partition schemes
> On those I create 2 RAID-1 partitions
> RAID #1 ( mirror ) contains /boot
> RAID #2 ( mirror ) contains LVM with other partitions
>
> Using these settings no longer gives me the option of selecting GRUB2 <- this is the real bug
If your /boot is on GPT you got never asked that question, because GRUB
Legacy just doestn't support it.
So this isn't at all a bug.
By the way GRUB 2 is now the default for everyone, though that question
should still be asked in expert mode and if GRUB Legacy can
handle /boot.
> And GRUB Legacy fails as it cannot handle /boot on mdadm with gpt partition schemes.
Why do you think GRUB Legacy was choosen by grub-installer? The syslog
would be useful, escpecially the grub-installer part.
>
> I thing this is an important bug as we soon have 2 gibibyte disks and the default msdos partition scheme cannot address those!
You mean 2 TiB, not 2 GiB.
If you use GPT you must create on all disks where your /boot is, a
`Reserved BIOS boot area', then shown as biosgrub.
A few MiBs are enough. They don't need to be all exactly the same size
and they don't need to be at the same sectors on the disks.
And you must create the RAID over a partition not over the whole disk,
even with msdos partition scheme.
I just tried it myself with todays amd64 businesscard.
100 MiB for biosgrub, rest for RAID 1 for an ext4 /
It installed fine, though grub-installer still used `grub-install (hd0)'
instead of (md0)
--
Felix Zielcke
Proud Debian Maintainer
Reply to: