I know you went on vacation over the new year, but it has been about two months now so I figured I would try to revive this conversation. Having collected my thoughts, this is what I propose: I believe that right now, grub recognizes an md device that is built on partitions, and installs to the underlying disks. When the device is built on the whole disks, it needs to divide into two categories: 1) Native md metadata. Grub should ask mdadm for a suitable location to embed the core image on each component disk. This can be satisfied with a 32kb area at the end ( or maybe the beginning ) of the disk that is not used by the array ( or the metadata ). This will work for all native formats except for 1.1, for the obvious reason that it is using the boot block. 2) Other metadata formats. Either assume or explicitly be told by mdadm that these formats are fakeraid and thus understood by the bios int 13. Grub installs to the array as a whole, just like it does today when they are handled by dmraid. If it is known that it is not bios supported, then error out. In the future this could be supported by creating additional grub modules that understand those metadata formats. One question that needs answered for method 1 is what should the partition table look like? Should grub, or maybe mdadm, create a protective mbr when using the whole disk, similar to the one used with GPT? -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
