reassign 567590 partman-base 128lenny1 retitle 567590 Strange bootable flag behavior with gpt disk label; RAID fails thanks
On Saturday 30 January 2010, Zachary Palmer wrote: > Here's the interesting bit. I sped through the menus and discovered > that the RAID system was quite happy to create a RAID1 for me. I went > back, deleted the RAID, and started over. The second time, I was able > to reproduce the bug. The only difference between these two runs was > that I remembered to flag both drives as bootable the second time. It > seems that a bootable GPT partition is the problem; the RAID menu system > doesn't seem to see it. It looks as if there's something wrong with the bootable flag code for gpt partitions, even without RAID. When I create a new partition I get: │ Partition settings: │ │ │ │ Name: │ │ Use as: Ext3 journaling file system │ │ │ │ Mount point: / │ │ Mount options: defaults │ │ Label: none │ │ Reserved blocks: 5% │ │ Typical usage: standard │ │ Bootable flag: off │ │ off │ Note the extra line with 'off' below the 'Bootable flag' line. That could be caused by bootable flag, but possibly also a different flag. Toggling Bootable flag does not work (it remains 'off'), but toggling the line below changes it from 'off' to 'on'. I think we should look into this first and see if it also fixes the reported issue with RAID. Reassigning to partman-base for now as this is likely a more general issue than just in partman-md. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org