> > keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2 > > /dev/sdb3 /dev/sdc3 > > mdadm: Note: this array has metadata at the start and > > may not be suitable as a boot device. If you plan to > > store '/' or '/boot' on this device please ensure that > > your boot-loader understands md/v1.x metadata, or use > > --metadata=1.0 > > mdadm: Note: this array has metadata at the start and > > may not be suitable as a boot device. If you plan to > > store '/' or '/boot' on this device please ensure that > > your boot-loader understands md/v1.x metadata, or use > > --metadata=1.0 As the utility warns you, anything other than 0.9 or 1.0 may have problems loading as / or /boot, because 1.1 and 1.2 both put the metadata at the start of the device, in your case a partition. > > Continue creating array? n > > mdadm: create aborted. > > keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2 > > --metadata=1.0 /dev/sdb3 /dev/sdc3 > > mdadm: array /dev/md0 started. > > keeper ~ # cat /proc/mdstat > > Personalities : [raid1] > > md0 : active raid1 sdc3[1] sdb3[0] > > 31463228 blocks super 1.0 [2/2] [UU] > > [>....................] resync = 3.9% (1241664/31463228) > > finish=5.2min speed=95512K/sec > > > > unused devices: <none> > > keeper ~ # > > > > Answering self - putting / on RAID1 only seems to work using > --metadata=0.90. Tried it with higher versions and had no luck. One may most certainly run a RAID1 / or /boot (or both) using other than 0.9 metadata. I'm running two servers with / on a 1.02 superblock and /boot on a 1.0 superblock, booting with grub 0.97. That said, if the restrictions of a 0.9 superblock are not an issue for your system, then there is nothing particularly wrong with employing a 0.9 superblock. > Anyway, the system is running well now. Unless the restrictions of a 0.9 superblock will cause problems for you in the future, that's the important thing. -- 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
