Bug#567590: Reproducable

[Frans Pop <elendil@planet.nl>]

reassign 567590 partman-partitioning 64
fixed 567590 71
tag 567590 pending
thanks

On Saturday 30 January 2010, Zachary Palmer wrote:
> I witnessed the same confusion myself; in retrospect, I should've
> mentioned it.  I simply assumed that it was a graphical glitch of some
> kind.  I was unable to set the "bootable flag" as well and had been
> setting the BIOS boot area flag (bios_grub) as well.  I'm not clear as
> to the semantic of that flag, but that's what I have set at the moment
> and it seems to be booting my machine correctly.  I'd be glad to provide
> more information at request, but I'm not terribly familiar with GPT, so
> I'm not sure what's relevant.  :)

OK. I'm not a gpt expert myself, but it does seem logical to me that a BIOS 
boot area cannot be used for RAID. AFAIK it's supposed to be a (small) 
separate partition reserved for use for booting the system.

Possibly the bios_grub flag should have been implemented as a "use as" 
option instead of a toggle. This seems to be confirmed as the changelog 
for version 71 of the relevant component has:
  * Convert BIOS GRUB boot area support to a method, thereby making it
    impossible to accidentally put a filesystem on such a partition as
    well, and making it simpler to preseed.
So it looks to be changed already for Squeeze.

So for now I'm going to just fix the display issue and assume that the 
disappearing RAID flag is as it should be.

Thanks for the additional info.

Cheers,
FJP