On 1/31/2011 12:03 PM, Lennart Sorensen wrote: > If you do software md raid on whole disks, I am not even sure if the > BIOS could boot from that, since there won't be a partition table, no > partition marked bootable (which some BIOSs requrie), sector 0 may not > even contain boot code. Not sure there is anyway whole device software > raid makes sense for a bootable drive at all. It makes sense for data > drives perhaps. I just don't see this as a candidate for booting at all. That is why I asked what the partition table should look like. When grub is installed there will be one ( and boot code ), the question is whether it should be empty, or have a protective partition that claims the entire disk, like EFI does. Normally with format 0.9, the raid array starts on sector 0, so the same MBR appears both at the start of the first physical disk, and at the start of the array. This is not possible with 1.1 or 1.2, so where do they start the array? I must be at some point further away from sector 0, leaving room for a protective MBR on the component disks that would be entirely separate from any MBR inside the array. This leaves room for grub to be installed on each component disk, rather than only the first. It also means that it is incompatible with formats 0.9, 1.1, and possibly 1.0, depending on whether it includes the first sector in the array like 0.9 does. -- 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
